hi,
i want to flash my i9001 with heimdall v1.3.1 (ubuntu 11.10) to the latest stock rom xxkpu. there is only a odin one package containing:
adsp.mbn
amss.mbn
boot.img
cach.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
i also have the s1_odin_20100512.pit file, because i cant download pit file from my device.
Can anybody explain to me how to flash with heimdall, cause i dont know what to do with adsp.mbn for example. heimdall doensn't have a parameter for that like heimdall --kernel for the kernel file.
if i have cwm-recovery on my i9001, can i flash stockroms with update.zip?
Thank you very much for your answers and sry for my english
can anybody please help me?
Hi,
I'd like to know something when flashing modem whith Odin.
My GT-I9305 isn't Root so...
I get the <modem.bin> file exctract from my one package carrier's ROM (I9305XXALK5_I9305SFRALK2_I9305AEALK2_HOME.tar.md5)
with 7zip
Can I use this modem (from a 4.1.1 ROM) as if I'm in 4.1.2 (I9305XXBLL5_I9305DBTBLL4_I9305XXBLL5_HOME.tar.md5)
in Odin3 (v3.04), where should I put the <modem.bin> file? Phone,PDA?
The flash counter will be incremented?
What about the OTA or Kies update?
Thx..
Re: [Q]How to Flash <modem.bin> file with Odin?
You need to convert it from a bin file to a. tar file for Odin.
Sent from my GT-I9305 using xda app-developers app
Obagleyfreer said:
You need to convert it from a bin file to a. tar file for Odin.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
I'd read on that post
[Q] How can i extract modem driver from official firmware
we can flash a .bin file with Odin..
...and flash via Odin using the "Phone" entry, not "PDA".
Click to expand...
Click to collapse
Warring of an other thread I'd read (but can't find again ) about Phone and PDA entry..
Hi all,
So any idea?
kanzi83 said:
Hi all,
So any idea?
Click to expand...
Click to collapse
Hello kanzi83, I'm new in the forums but I decided to register so I could help you.
I had the exact same problem and came with a solution, after reading yewsiong's instructions on his post:
http://forum.xda-developers.com/showthread.php?t=1658809
Modifying them so they match your situation, you have to do the following:
1. Install Cygwin and start the Cygwin terminal
2. Put the .tar.md5 firmware into C:\baseband
3. In Cygwin, type the following commands (pressing enter after each line):
Code:
cd /cygdrive/c/baseband
tar -xvf firmware_name.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
Example: If the firmware_name.tar.md5 is I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5
Then the code will be:
Code:
cd /cygdrive/c/baseband
tar -xvf I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
After generating your .tar file, you can use Odin or Odin Mobile (I used Odio Mobile Pro and worked excellent) to flash the Modem.
There you go! Please let me know if you have any questions. Good luck.
kanzi83 said:
Hi all,
So any idea?
Click to expand...
Click to collapse
It's not that hard. Google is your friend.
Please read the following link.
http://forum.xda-developers.com/showthread.php?t=927568
You can just simplely flash modem.bin file via Odin.
Sent from my GT-I9305 using xda app-developers app
Thx for your answers. ..
I'd flash modem.bin file 2 month ago with odin v 3.04 in phone entry and works well
Envoyé depuis mon GT-I9305 avec Tapatalk
Procedure for changing the modem.bin
Hello all,
I am a newbie and want to know to how can I change the modem.bin file of my phone using ODIN...
Kindly help
Try reading this thread answer given in post 6 .
Aldo6 said:
Hello kanzi83, I'm new in the forums but I decided to register so I could help you.
I had the exact same problem and came with a solution, after reading yewsiong's instructions on his post:
http://forum.xda-developers.com/showthread.php?t=1658809
Modifying them so they match your situation, you have to do the following:
1. Install Cygwin and start the Cygwin terminal
2. Put the .tar.md5 firmware into C:\baseband
3. In Cygwin, type the following commands (pressing enter after each line):
Code:
cd /cygdrive/c/baseband
tar -xvf firmware_name.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
Example: If the firmware_name.tar.md5 is I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5
Then the code will be:
Code:
cd /cygdrive/c/baseband
tar -xvf I8150DXLM3_I8150OLBLD1_I8150DXLM2_HOME.tar.md5 modem.bin
tar -H ustar -c modem.bin > baseband.tar
After generating your .tar file, you can use Odin or Odin Mobile (I used Odio Mobile Pro and worked excellent) to flash the Modem.
There you go! Please let me know if you have any questions. Good luck.
Click to expand...
Click to collapse
Thank you!
Is this file checked against md5 when flashing with Odin? (Or when tar-ing?)
How to install modem.bin in my galaxy siii having android 4.3
[QUOTE=kanzi83;40365571Would you please let me know step by step guide to install my modem file (modem.bin) into my GT-I9300 using Odin. Your help in this regard will be highly appreciated.
I am very new to Android world. Need help
when I flash modem.bin via phone with odin 3.07
it fails
yasser86 said:
when I flash modem.bin via phone with odin 3.07
it fails
Click to expand...
Click to collapse
zip the file to .tar
Successful flash with Odin 3.10 & I9305
At first got errors when tried to flash modem.tar which I compressed with 7-zip from modem.bin
Odin just stopped at flashing modem.bin, so unplugged USB and cold restart (everything was still working fine with my phone, even the old modem)
Then successfully flashed modem.BIN via ticking it to CP (Phone?)
So... Somehow Odin couldn't flash my compressed .tar file of the modem..
Maybe I did something wrong with the compression
But now I have a working modem from the latest samsung firmware for my country and signal feels much more reliable now and even got a little bit better speedtest results too
How to flash Modem.bin file with Odin
hi,i had read all posts but i did not get any satisfying result,.....the Solution is
you have to select Odin V3.9 .in 3.9 in CP you can flash modem.bin
Regards
[email protected] said:
hi,i had read all posts but i did not get any satisfying result,.....the Solution is
you have to select Odin V3.9 .in 3.9 in CP you can flash modem.bin
Regards
Click to expand...
Click to collapse
Confirmed with Odin3.10. Don't make it too complicated, folks!
mightysween said:
Confirmed with Odin3.10. Don't make it too complicated, folks!
Click to expand...
Click to collapse
Worked for me also. Thanks OP
hello
raonizal said:
zip the file to .tar
Click to expand...
Click to collapse
This works with newer versions of ODIN.
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
John877 said:
I installed Magisk Manager 5.3.0 and opened it and clicked on Install to download Magisk 14 and to patch the boot.img file that I got from the Samsung Firmware file.
I patched the file and that completed fine with no errors.
I then copied the patched boot.img file to my computer so I could run ODIN on to flash it. Its in the proper format, "magisk.img.tar" is that I called it.
I opened ODIN 3.12 and selected the file under BL and plugged my phone in while in Download Mode.
ODIN detected my phone with the Added! msg in the log window.
ODIN is still running as I type this and all that is in the log is the following:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
Theres no change on the phone screen either.
OEM Unlock is enabled as on the phone screen it says FRP Lock: Off
Phone is a Samsung Galaxy J3 Emerge (J327P) with Boost Mobile
Samsung firmware file from SAMMOBILE is J327PVPU1AQF4_J327PSPT1AQF4_BST
Click to expand...
Click to collapse
It has to be added in AP not BL.
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Hani88 said:
I did the same and I tried to flash it in odin in AP but odin crushes!!
My phone is Galaxy S7 edge
Click to expand...
Click to collapse
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Or do you have the possibility to untar the image (or create just the boot.img) and use a "real" gnu-tar (preferred on linux).
Or give me the exact firmware, so I can try to create the image and tar it with the tar on my Fedora system ?
When doing the (internal) beta-tests I had the same issue, because of incorrect tar-headers (gnu-tar does not care about it). That should be fixed in MagiskManager, but Odin seems to be extremely nitpicking about the tar-header.
It might also be a problem with signed (or better not signed) bot-image, but I guess this would lead to another error.
Click to expand...
Click to collapse
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Hani88 said:
Well for me I only know how to extract the boot.img file from the AP file using winrar and patching it using magisk then renaming to .img.tar
I don't know anything about gnu-tar linux
Click to expand...
Click to collapse
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
jenslody said:
Can you give me the exact version of your rom, so I can download it and send you a patched image for testing ? Or send me the boot.img either patched, stock or patched and tared ?
Click to expand...
Click to collapse
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
白い熊 said:
Well, if that's what you did, no wonder why it's failing and Odin is stuck on analyzing the image—it's not in the proper format, you shouldn't rename it, you need to tar the boot.img file.
Click to expand...
Click to collapse
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Hani88 said:
It is
GF935FXXS1DQHM
I downloaded it from samfirm
I can send you the boot.img tomorrow because my laptop is not with me
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Now I understand because inside it also there is not "meta inf " folder. How to tar it ?
Click to expand...
Click to collapse
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
jenslody said:
In MagiskManager's settings chose the .img.tar output format. The patched image should be named "patched_boot.img.tar", if it's just "patched_boot.img" you can not directly flash it!
Click to expand...
Click to collapse
But in odin in AP I am not able to import img file
Hani88 said:
But in odin in AP I am not able to import img file
Click to expand...
Click to collapse
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
jenslody said:
That's why you have to chose the correct patch-format in MagiskManager's settings before patching the stock boot.img .
In the settings click/touch "Patch Boot Output Format" and chose ".img.tar", then in the main menu click/touch "Install", then again "Install", then "Patch Boot Image File", chose the stock-image and wait until it is patched.
This should create a file named "patched_boot.img.tar" in the MagiskManager-folder of your internal storage.
This should be flashable.
Changing just the ending of any file does not change the format and can not work therefore.
Click to expand...
Click to collapse
Thanks for the explanation.. I will do it tomorrow
Flashing a patched boot image will trip the knox counter right ? Of course mine is tripped but I want to know that
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
John877 said:
@jenslody I have just tried flashing the patched boot.img file in ODIN under the AP/PDA field and depending on ODIN version it either crashes or is stuck at file analysis. I have named the file "magisk" to keep the filename short. Therefore the full filename is magisk.img.tar. It was created using the patcher in magisk manager with the output setting of img.tar. I prefer to flash it in ODIN as I would like to keep the stock recovery for the sake of future updates.
How I obtained the boot.img file is from opening the stock firmware image from SAMMOBILE and extracting the AP file and grabbing the boot.img. I also grabbed the recovery.img this way just to have it. I dont have access to any other way of extracting the files as I dont have or use linux personally so its my windows 10 computer only.
As you offered the other guy above I am including my stock extracted boot.img file as well as my exact firmware version on SAMMOBILE.
The exact firmware filename is: J327PVPU1AQF4_J327PSPT1AQF4_BST
Its the Samsung Galaxy J3 Emerge (2017) from Boost Mobile (J327P) with Baseband version ending in QF4. Its on Android 6.0.1.
I was unable to attach the boot.img file here cause its too big (11.7mb) and the upload failed when I tried to ZIP it instead cause the limit there is 20mb. So here it is on DropBox instead.
https://dl.dropboxusercontent.com/s/azyeqrx7rtvjvik/boot.img
Once again the is extracted directly from the firmware file with winrar with no magisk patching.
Click to expand...
Click to collapse
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
jenslody said:
This should work, unless your ODIN-version stumbles about other things than mine.
Nevertheless, I uploaded a patched version of your boot.img to my server: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar .
It's tared with the tar from my Fedora-system, but the (tar-header related) fixes @topjohnwu made to the java-tar he uses in MagiskManager made the created image flashable on my J5 (latest stock).
I also added a tared image with md5-checksum for you to test: https://rpm.jenslody.de/magisk/J327PVPU1AQF4_patched_boot.img.tar.md5
Click to expand...
Click to collapse
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
白い熊 said:
@jenslody, just for me to understand—you get the patched version via Magisk Manager, then untar it, then tar it again with a custom built tar?
Where are the patches you mention?
Click to expand...
Click to collapse
I used the stock boot for J3, patched it through MagiskManager (one as *.img, one as *.img.tar), renamed the patched_boot.img to boot.img (taht's what Odin expects inside the tar, used Fedora's tar (I'm on Fedora 26) to create a tar archive from it and just for testing added a md5-checksum to one version of it.
MagiskManager is the 5.30 released with/for Magisk 14.4, bot patched. The fixes I mention were made by @topjohnwu in the (internal) beta-testing for 14.4.
To be clear:
the released Magisk with MagiskManager create img.tar-files that work for my J5 with the Odin-version I use (Odin3 v3.10.7) without any tweaking.
My self-tared versions are for testing purposes, to see if other Odin versions are more nitpicking than mine (about tar-headers). The included boot.img is exactly (binary) the same.
John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now.
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Also would this be how to flash the recovery.img file too if I flash TWRP and want to go back to the stock recovery?
Click to expand...
Click to collapse
Same question here.. and you are not the only one who's feeling like an idiot now
---------- Post added at 09:23 AM ---------- Previous post was at 09:02 AM ----------
jenslody said:
Can you by any chance send me the boot-image, stock, patched, tared ?
Click to expand...
Click to collapse
here is it thanks for helping
https://drive.google.com/file/d/0B9_cANW46As_Y2Jwa0xsR1p2UkE
John877 said:
I think I realized my mistake. I extracted the boot.img file from the AP file of the firmware then not realizing it has to be inside a tar archive file I just renamed the boot.img file boot.img.tar instead. I feel like kind of an idiot right now. [emoji14]
Would it be sufficient to just use 7zip to create a tar archive with the boot.img file inside it?
Click to expand...
Click to collapse
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
白い熊 said:
It's unnecessary, you should just select .img.tar as the output format in Magisk Manager's settings. Then you can use the .img file you've extracted from the stock firmware. Magisk Manager will patch the .img file and create a patched .img.tar
This you should be able to flash with Odin.
Click to expand...
Click to collapse
When I extracted the boot.img file from the firmware it was boot.img. When I patched it from magisk manager, it was boot.img still even though I chose output format img.tar.
Unroot Galaxy Note 5 SM-N902i (XSA Australia) with Heimdall - "System UI has stopped"
Hi all,
I am running a linux machine and trying to unroot my Galaxy Note 5. I've downloaded the lastest firmware from sammobile: N920IDVU4CRG1_N920IXSA4CRG1_XSA.zip which extracts to:
boot.img
cache.img
cm.bin
hidden.img
modem.bin
recovery.img
sboot.bin
system.img
Then I've been trying to use heimdall like so:
heimdall flash --verbose --BOOTLOADER sboot.bin --CM cm.bin --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img
The process finishes successfully but then when the phone reboots it hangs with an error: "System UI has stopped"
I've previously executed heimdall print-pit to check the pit list. I noticed that there are more pit entries than the 8 provided in the firmware. I don't know if that's normal.
I also tried using the pit file found on the forum with the same negative result: forum/threads/30106-galaxy-note-5-(-N920-)-pit-files
heimdall flash --pit NOBLELTE_AUS_XSA.pit --verbose --BOOTLOADER sboot.bin --CM cm.bin --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img
Same error.
Is there something that I've been missing or done wrong?
Many thanks
I honestly don't know what Heimdall is, but I would recommend something else. I bet you rooted that phone with Odin, right? If so, try this tutorial.
https://galaxynote5root.com/galaxy-note-5-unroot/how-to-unrootunbrick-galaxy-note-5-2/amp/
If that did not work, try flashing the factory room using your Custom Recovery tool. If you haven't flashed one yet, you should flash TWRP. (Using Odin, go figure)
Hi, thx for your answer. I did not use Odin to root my phone but "adb" since I m on Linux. That said I have now installed Odin on a windows 7 virtual machine on VirtualBox. I followed the Odin procedure. It ended up successfully finishing the procedure but then same thing happened on boot: "System UI has stopped".
But there is something in the video in the page you suggested that gave me a clue: he mentioned clearing all the data on your phone. So I flashed twrp using adb, deleted manually all the data. Then I used heimdall again to flash the firmware and it worked! It would have also worked with Odin. I m happy
I'm writing this because in all my searching I couldn't find a short guide of how to install the Stock firmware using Heimdall. I had a T710 that was failing to boot any ROM I put on it with TWRP. So I decided to put Stock back on it.
obtain stock firmware, mine was named BTU-T710XXU2DRH1-20181005080953.zip
unzip in a new directory, for me this resulted in a single file: T710XXU2DRH1_T710BTU2DRH1_HOME.tar.md5
untar with:
Code:
tar xvf *.tar.*
For me this resulted in the following
boot.img
cache.img
hidden.img
recovery.img
sboot.img
system.img
get the output of print-pit:
Code:
heimdall --print-pit >pit.txt
in the print-pit output, for each entry, look at
Code:
Partition Name
and
Code:
Flash Filename
. This will help you determine which file goes with which partition name.
boot to download mode (Power+VolDown) and use heimdall to flash the parts you want. For me this was:
Code:
heimdall flash --BOOT boot.img --CACHE cache.img --HIDDEN hidden.img --RECOVERY recovery.img --BOOTLOADER sboot.bin --SYSTEM system.img
after the flash the system will automatically reboot. You'll get the throbbing Samsung icon for a while as it does stuff and then it will boot.
Thanks a lot for this. You saved my T810.
I had decided to upgrade my 6-year-old tablet to LineageOS and idiotically missed the first critical step of enabling OEM Unlock. I tried to flash TWRP using Heimdall and softbricked it... It could only boot into download mode and for some reason, Odin could not recognise it, only Heimdall.
I downloaded the latest version of the stock firmware using Frija and followed your method, worked perfectly and I now have stock Nougat.
Still can't figure out why the OEM Unlock button doesn't appear in the Developer settings for me, so can't install Lineage, but at least everything is working again.