Develop Bugs

[Q] PURE Heimdall Stock GingerBread Upgrade

All the current upgrade methods involve ODIN or don't explain the heimdall version in depth..
I HAVE NOT TRIED THIS YET - waiting for confirmation from someone who knows more than me.
Heimdall 2.3.3 Update v0.9 - UNTESTED
1) Back everything up. Titanium etc..
2) Download the new Stock 2.3.3 file, as found in Overcome 2.0beta http://www.multiupload.com/F6D7U1RUHD
2) Extract GB-stock-safe.zip into a folder.Go into the folder.
3) Now extract the GB_Stock_Safe_v1.tar file into another folder.
3) Copy the gt-p1000_mr.pit and the correct modem.bin into the extracted GB_Stock_Safe_v1.tar folder. So all the required files in one place now.
4) Plug Tab into computer and go to Download mode. (You can do this, by shutting/powering down your Tab. Once shut/powered down, hold down the Volume Down button and the Power button together until Download screen appears) or much easier if you have adb
Code:
adb reboot download
5) (Once in Downlaod mode) From the command line, run this function from the folder where the GB_Stock_Safe_v1.tar file was extracted, and you copied the gt-p1000_mr.pit and modem.bin file.
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
6) basically the movinand.mst and hidden.rfs files are still in the folder but not referenced.
Is this correct !? Can someone confirm or deny please?
I'll update this post with corrections

Just used these instructions to take a stock Froyo Galaxy Tab to Gingerbread stock version (Overcome restock v5) using only Linux.. and then to CM7.
I installed the deb package from the Heimdall web site and installed it into my Ubuntu 10.10 install. Worked like a charm. Thanks a bunch for posting this. Saved me trying to mess around with Windows.

Super Confused About Heimdall

Hi, I'm trying to put stock 2.2 back on my Epic and I'm using Heimdall as I don't have my Windows PC here at college.
So I have 1.31 frontend installed and opened, but I cannot for the life of me, find what needs to go under "Heimdall Firmware Package." Where can I find that file? And also for the PIT, I just downloaded the 2.2 tar for the Epic from the XDA wiki, is that the right thing?
Thank you so much!

I don't have heimdall set up...but i think the tar goes into firmware DO NOT QUOTE ME...and the pit goes into pit obviously. The pit is a .pit file needed for partitioning.

I always use 7zip to open the tar and put them into the correct spots on Heimdall. This was I can use my own choice of recovery and param.ifs.

Yes, you have to open the tar file and put each individual piece into the appropriate section of heimdall

How to make a .tar into a .tar.md5 in Windows?

I am trying to make my own .tar that I can use in Odin. I have the gsm Galaxy Nexus. I already have 4.1.2 and installed it via fastboot from https://developers.google.com/android/nexus/images#takjujzo54k. But just in case I would love to have a .tar to flash with Odin just in case. I downloaded the Takju and extracted all the .img and made a .tar with 7-zip and when I try and flash it through Odin it hangs at nand write start.
So I looked around and found a pre made .tar Yakju here http://forum.xda-developers.com/showthread.php?t=1827685. Since this was for Maguro phones I flashed it through odin with no problems at all.
That Yakju .tar is actually a .tar.md5, so is this the problem with my tar that I made? I've been reading up on md5 and what it actually is but can't find a way to add it to my file name. If someone can point me in the right direction I would really appreciate it. I would like to be able to do this on my Windows 7 rig if possible. Thanks!!

Md5 is just a hash check on the file to make sure it is downloaded correctly. You compare the md5 with the same code that is posted on the download site/location. If it match your download is 100% correct.
Swype'ed on my CM10 Galaxy Nexus

Herman76 said:
Md5 is just a hash check on the file to make sure it is downloaded correctly. You compare the md5 with the same code that is posted on the download site/location. If it match your download is 100% correct.
Swype'ed on my CM10 Galaxy Nexus
Click to expand...
Click to collapse
just install cygwin
Code:
md5sum filename.fileextension > filename.fileextension.md5
to check
Code:
md5sum -c filename.fileextension.md5
example:
valhalla% md5sum -c full_maguro-user-15102012v2-JZO54K-bk201.zip.md5
full_maguro-user-15102012v2-JZO54K-bk201.zip: OK
Click to expand...
Click to collapse

bk201doesntexist said:
just install cygwin
Code:
md5sum filename.fileextension > filename.fileextension.md5
to check
Code:
md5sum -c filename.fileextension.md5
example:
Click to expand...
Click to collapse
can someone make this a bit more noob friendly?
Installed Cygwin..do I need any packages to install?
Where do I put my .tar file
Why when I press Enter at the end of a command in the terminal nothing happens, the cursor just goes to the next line...
for just adding the md5 there is no easier way? something with GUI? maybe something on the android device even...

dataman said:
can someone make this a bit more noob friendly?
Installed Cygwin..do I need any packages to install?
Where do I put my .tar file
Why when I press Enter at the end of a command in the terminal nothing happens, the cursor just goes to the next line...
for just adding the md5 there is no easier way? something with GUI? maybe something on the android device even...
Click to expand...
Click to collapse
install cygwin (install only zip files, no need to install all files)
open cygwin ------>Home------->(user name) and create a folder named "work".
put all images files of stock firmware of your gnex downloaded from google site (radio, bootloader, boot, recovery, system, userdata) in "work" folder.
open cmd by clicking on cygwin .bat file and enter the following commands:
Code:
cd ./work
tar -H ustar -c boot.img bootloader.img radio.img recovery.img system.img userdata.img > name-of-odin-flashable.tar
md5sum -t name-of-odin-flashable.tar >> name-of-odin-flashable.tar
mv name-of-odin-flashable.tar name-of-odin-flashable.tar.md5
(images must be written in command exactly as they are written in "work" folder)
go to "work" folder, and BOOM you have a ready flashable odin .tar.md5 file for your Gnex!

[Q] How to flash baseband modem with Odin without rooting

Can anyone tell me if it's possible to flash/change/update just the baseband modem in my AT&T Samsung Galaxy S3 SGH-I747 without rooting the phone? After installing the latest update via the Samsung KIES software my phone reception has dropped a good bit. I no longer have service where I used to. My phone calls are also very choppy in the fringe reception areas, where before they were significantly better. I live in an area where 4G/3G coverage is fairly spotty, so EDGE is my primary network.
I wish I could remember which baseband version it had before the update so I could roll back to it, but I don't, so it may take a few tries before I can find the correct baseband version. Before the update I know I had ICS v4.0.4......not sure on Baseband version. Now I have Jelly Bean v4.1.1 (which I would like to keep) with Baseband I747UCDLK3.
I've tried using Odin v3.07 and the "AT&T Models Only! (I747U)" files via the link below and inserting the correct file path into the "Phone" section without any luck. Odin detects my phone, starts the process, but fails. http://forum.xda-developers.com/showthread.php?t=1831898
I've read to only use the "PDA" section in Odin to flash, but the files via the link below dont seem to have the proper file to use with the "PDA" seciton in Odin......am I missing something critical here maybe?
I then came across the following link where other people have used Odin to flash the baseband modem and seem to have been successful. http://forum.xda-developers.com/showthread.php?t=927568
Thanks for any help because I've spent hours searching the forum and Internet trying to find an answer!

I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.

I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!

SideWinder4x4 said:
I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!
Click to expand...
Click to collapse
i believe HON-HLOS.bin is your modem

SideWinder4x4 said:
and when I open or extract the files using 7zip,
Click to expand...
Click to collapse
Do not actually extract the files or else you will ruin the MD5 checksum and the flashing process will fail. Simply replace the modem file with the one you want to use by taking a "peek" in the actual TAR file.

Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.

mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
I've tried this method using Ubuntu Terminal to create a new modem.tar.md5 file, but everytime I try to flash with Odin, it fails. What am I doing wrong. Thanks for any further advice, this is driving me crazy!
My steps are as follows:
1.) I'm unzipping the correct modem files (modem_CWM_I747_UCLH9.zip) from this link - http://forum.xda-developers.com/showthread.php?t=1831898
2.) I'm taking the "modem.bin" file and copying it to Ubuntu desktop folder
3.) I'm opening Terminal
4.) I change to the Desktop directory
5.) First command...without the quotes is "tar -H ustar -c modem.bin > modem.tar"
6.) Second command...without the quotes is "md5sum -t modem.tar >> modem.tar"
7.) Third command...without the quotes is "mv modem.tar modem.tar.md5"
8.) I copy that "modem.tar.md5" file back to my Windows 7 based computer
9.) I rename "modem.tar.md5" to "modem.tar"
10.) I press and hold the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted press the "Volume Up" key
11.) On the screen I see the following: ODIN MODE, PRODUCT NAME: SGH-I747, CUSTOM BINARY DOWNLOAD: No, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, QUALCOMM SECUREBOOT: ENABLE
12.) I then open Odin v3.07 using defaults
13.) Odin recognizes my phone on COM8 with a blue teal colored box
14.) I press the "Phone" button and select the "modem.tar" file
15.) I press the "Start" button and it shows "modem.bin" in the first box in white, but about 5 seconds later it turns red and says FAIL!
The Odin message box indicates the following:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> modem.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

Well, try naming it NON-HLOS.bin instead of modem.bin. Also, don't rename it after you make the tar.md5 file.

Solution Found
I finally got this figured out. Thanks for all of the help and ideas along the way!
The key tip was found in this thread - http://forum.xda-developers.com/showthread.php?t=1658809
Just to simplify things for others in the future, the steps I performed were as follows:
1.) Installed Cygwin from http://www.cygwin.com/
2.) Started Cygwin Terminal
3.) Put the SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 firmware file into the following folder I created "c:\baseband"
4.) In Cygwin, typed the following command without the quotes "cd /cygdrive/c/baseband"
5.) In Cygwin, typed the following command without the quotes "tar -xvf SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 NON-HLOS.bin"
6.) In Cygwin, typed the following command without the quotes "tar -H ustar -c NON-HLOS.bin > baseband.tar"
7.) Pressed and held the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted pressed the "Volume Up" key to enter "Download Mode"
8.) I then opened Odin v3.07 using defaults
9.) Connected my phone to my computer using the proper USB cable
10.) Odin recognizes my phone on COM8
11.) I pressed the "Phone" button and selected the "baseband.tar" file I created in step #6
12.) I pressed the "Start" button and about 30 seconds later it finishes and the box turns green and the phone rebooted.

Thanks Sidewinder. Its very informative.. I am facing a strange issue on my Galaxy R ever since I upgraded to ICS and JB (stock/ custom ROMs).
Very often I get my calls disconnected while speaking. This was not the case with Ginger bread..
Today followed your procedure to extract the modem.bin from stock GB rom and flashed to my JB custom ROM (Carbon).. Looks good so far..tried
with test calls - seems to be OK.. Will observe for some more time.

You're Welcome asbalaji. I'm glad what I posted helped you out. My phone reception issues improved a lot after downgrading to an older modem.

Anonymously_Unknown said:
I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.
Click to expand...
Click to collapse
I am in desperate need of a baseband to flash via ODIN for a boostmobile galaxy S3
---------- Post added at 07:00 AM ---------- Previous post was at 06:24 AM ----------
mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
Basebadn boostmobile s3

[Q] Extract Boot.img from Stock ROM

Hi guys, I would like to extract boot.img from a Stock ROM without the need of installing it on my (Galaxy Note 2 T-mobile). All I found on the internet is how to extract it from an installed ROM.
So I would like to:
1. Extract the boot.img
2. Then flash it through ODIN to my custom ROM (Jedi Master 14)
Thanks in advance and please help me :crying:

Why would you do that?
Hastily spouted for your befuddlement

I don't know how you going to use boot.img to fix your problem. But the .md5 rom files are just zipped files. unzip and you will find the boot.img file. Are you sure that this will fix your problem?
Are you trying to change your boot image?

Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.

Thanks a lot. Thats exactly what I am looking for.
Sent from my SGH-T889 using xda app-developers app

Darkshado said:
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Click to expand...
Click to collapse
and how do we do?
i flash the file without pepacking it so i can t bot, kernel error!
I'm really annoyed if you can explained to me how do we do it
thx