Related
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.
Hello,
I'm just wondering how I can make the .tar file with the recovery.img file in it and flash with Odin? Does anyone have a guide to how to do this? I recently downloaded the latest recovery from Clockworkmod website, but don't know what to do from there. I know how to flash with Odin of course, but don't know how to make the .tar file with the recovery.img file in it. I tried to (NOOB) rename the recovery file I got from cwm website to "recovery.img" and put it as a .tar file using 7Zip, thinking it would work, but didn't work. So I'm guessing there's another way, I'm sure I can figure it out with a good guide. Thanks!
P.S: Only reason why I want to know how to do this is because there's no actual place to my knowledge where I can update my cwm recovery automatically, but if anyone knows an automatic way of updating cwm that would be a big plus. Thanks.
you could use rom manager. As long as your device is rooted, Rom Manager will download and flash your recovery for you.
or...
You can also put your recovery file on your sdcard so that the path would be /sdcard/recovery.img Then using either adb shell or terminal emulator, the command would be
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
lordmorphous said:
you could use rom manager. As long as your device is rooted, Rom Manager will download and flash your recovery for you.
or...
You can also put your recovery file on your sdcard so that the path would be /sdcard/recovery.img Then using either adb shell or terminal emulator, the command would be
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
Oh yeah I know about rom manager, I just want to know how to make the file so I can, in the future update my cwm recovery version. I use Rom Manager to flash the recovery and do what I want in the recovery, that's not an issue, just updating it to a later version if one comes out is why I want to know how to make the file. I tried to download the latest cwm from Rom Manager, but when it gives me the devices list to download, the Galaxy S3 is not there.
A day or two ago I opened rom manager and it prompted me that there was an update for my recovery downloaded it and flashed it no problem
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
DeathKoil said:
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
Click to expand...
Click to collapse
Ah thanks! I downloaded that tar file and updated successfully! I will try that command guide out and see if it works. Thanks again! :fingers-crossed:
lordmorphous said:
A day or two ago I opened rom manager and it prompted me that there was an update for my recovery downloaded it and flashed it no problem
Click to expand...
Click to collapse
Hmm...that's really weird..I never got such a message.
EDIT: Tried the command guide, and it didn't work unfortunately, but it does show the recovery.tar file, won't let me open saying it is damaged. On the cmd it tells me: 'tar' is not recognized as an internal or external command operable program or batch file.
The recovery.tar file is made though, but can't be opened. Any tips?
Thr toolkit posted lets you do that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
is 6.0.1.2 much better than the version from the toolkit?
No I'm saying that the toolkit Lets you make img files into Odin flashable tar files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
drakeymcmb said:
No I'm saying that the toolkit Lets you make img files into Odin flashable tar files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes you're right! Thanks a lot. Made one using a recovery image downloaded from cwm website, makes tar file and everything, worked when flashing with Odin. Thanks again.
DeathKoil said:
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
Click to expand...
Click to collapse
To do the same thing in windows, you need to use Cygwin.
what is the toolkit u guys are talking about? Is there a link?:silly:
http://forum.xda-developers.com/showthread.php?t=1746665
I think this is the one they are referring to.
mrhaley30705 said:
To do the same thing in windows, you need to use Cygwin.
Click to expand...
Click to collapse
I happened to have Cygwin installed so I used it to tar the image, but you could probably use 7-z
DeathKoil said:
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
Click to expand...
Click to collapse
I'm also running Linux, but my computer seems to have problems communicating with my S GS3 (T999V). It doesn't help that I'm new to linux, but where do you get a driver for the gs3 for linux? Also, if I were to package a ROM into a .tar or .tar.gz to be flashed with Heimdall, what do? just unzip my rom, repackage as .tar.gz and try with heimdall?
I stall out on flashing recovery image. Here's what I get. I'm using a tar where I manually swapped in the recovery image on my own.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
Click to expand...
Click to collapse
And it just stalls. The screen of the phone appears as if nothing happened. I don't see the progress bar or anything.
Odin shows the first blue bar of the progress bar but it never goes beyond that.
Any help?
EDIT - it worked fine using one of the tars from this thread. - http://forum.xda-developers.com/showthread.php?t=2015369 - So what am I doing wrong when substituting a recovery image on my own?
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
Hi
Where is Sboot.bin partition located in T800? I want to dump it.
Thanks
Just pull it from a stock Rom.
ashyx said:
Just pull it from a stock Rom.
Click to expand...
Click to collapse
Yes, i know, thanks. I have pulled a stock copy already. I wonder if it's possible to dump a copy from my tab and compare with stock (for research). I could not locate it in: /dev/block/platform/dw_mmc.0/by-name. Is there a copy in T800?
Thanks
Sorted. Pit file dumped with PIT Magic, and analysed with Jenkins online Pit anaysis tool.
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Yes!! I have asked countless people and put a thread up but nobody answered. Thank you very much for this tool! I used to use EXT2EXPLORE on KitKat with my S4 Mini, now I can use it on my S6. Thank you!!
citytrader said:
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Click to expand...
Click to collapse
I'm FRP boot loop locked on my G928W8 and I can't fix it because stock firmware isn't available on sammobile yet. Can this tool be used by someone with the stock firmware to pull it off and fix my problem? Does it require root to make the image?
I need a stock firmware image before the battery runs down even while off. So if someone can extract their stock firmware then it could really save my phone. Is this something the tool could be used for, or would the md5 not be the same as the actual stock firmware so the FRP lock would stay?
thismonk said:
I'm FRP boot loop locked on my G928W8 and I can't fix it because stock firmware isn't available on sammobile yet. Can this tool be used by someone with the stock firmware to pull it off and fix my problem? Does it require root to make the image?
I need a stock firmware image before the battery runs down even while off. So if someone can extract their stock firmware then it could really save my phone. Is this something the tool could be used for, or would the md5 not be the same as the actual stock firmware so the FRP lock would stay?
Click to expand...
Click to collapse
You need someone that can dump the partitions of their phone and flash that partitions to your phone, you need to understand a bit the procedure before flashing with ODIN
citytrader said:
Here are the tools needed for file extraction of system.img and
TAR MD5 packing for ODIN flash, it means you could do your package with only the files to want to flash in ODIN, for me this tools are very useful.
ALL IS WORKING FLAWLESS WITH LOLLIPOP
http://www23.zippyshare.com/v/4v1wFBtL/file.html
Explanation:
------
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
NOTE: newimg2ext2 is renamed from the original file name SVAImgUnpack, credits to @svadev
-------
For packing files for ODIN, I made an example file that is named modem2tarmd5.bat, this pack modem.bin into modem.tar.md5 ready to be flashed with ODIN,
edit the .bat and use with the files you like.
Click to expand...
Click to collapse
How can we use it;;it gives wrong parameter if executed.needs editing;;the newimgext2 ??
citytrader said:
For unpacking the system.img
NEWIMG2EXT2 system.img systemext2.img <- It converts ODIN images to EXT2 filesystem
Read the file systemext2.img with ext2explore and extract any file you want
Click to expand...
Click to collapse
Works fine ! I tried a lot of methods to do the same thing, of firmware Lollipop Samsung Galaxy S6 and S5 neo. This method is the only one which works. Thanks !
Very good love it, works even on Nougat (S7).