[Q] Flashing Stock Rom with Heimdall 1.3.2 on a Macbook 10.6.8 - Galaxy S III Q&A, Help & Troubleshooting

I'm trying to change the stock firmware on my unlocked unrooted international S3: I9300 to an official Samsung ROM downloaded from sammobile. The file I downloaded is called I9300XXDLJ4_I9300OXADLJ4_BTU. It's the UK unbranded firmware. The current firmware is on the phone is:
AP: I9300XXBLH3
CP: I9300XXLH1
CSC: I9300OPSBLH3
I have unzipped the file downloaded from Sammobile, which then gave me a tar.md5 file. So I change the file to just .tar, then unzipped that file. Inside that file I have:
boot.img
cache.img
hidden.img
modem.img
recovery.img
system.img
I then tried to use this tutorial on youtube called: How to Use Heimdall on Mac OSX to Install Kernels and ROMs!
When I open Heimdall on my MacBook, I plug my phone in (in download mode) and go to utilities, detect device, which it does. Then I save the PIT file on my desktop. I then go to the flash tab and browse for the PIT file, load that. Then when I go to add the files I don't have any files listed above called zimage or factoryfs etc, but also the Heimdell options doesn't have anything called kernal or the other ones anyway. My options in the partition name drop down box are:
Bootloader
Userdata
OTA
Hidden
System
Cache
Radio
Recovery
Boot
Param
EFS
BOTA1
BOTA0
MD5HDR
TZSW
The video says to match the files, but mine seems to have different names for things.
I have searched and read many forum posts on here and other sites. Can anyone tell me what I am doing wrong with either the unzipping or with Heimdall?
Thanks

Samsung hate apple....thats probably your problem
Sent from my GT-I9300 using xda premium

Thanks, but I only have access to a Mac. I did try my work computer, but it won't let me install any programs like Odin and drivers without Admin privileges.

Related

[Q] Some Questions About Flashing and Firmware

I am sorry if my thread doesn't belong to this section. I have tried to search but I don't get satisfactory information. My questions are:
1. Which one from all files inside the firmware tar that contains the CSC part? Is it cache.img or hidden.img?
2. Do all CSC files reside in the /system/CSC folder?
3. I have the conclusion that the image/bin file inside the firmware will be used to wipe/format the corresponding partition i.e. factoryfs.img for /system partition, etc. Is that true?
4. Is it possible to just flash the PDA/Phone(Modem)/CSC part individually? If I am not mistaken, we can use Odin just to flash the kernel.
5. Is it possible just to create firmware tar file containing just one image to update specific partition? E.g. file containing just factoryfs.img
6. Beside the img file which must be in the compressed ext4 image, can we just use tar command to create the firmware for Odin?
7. Suppose I only have the PDA part of the firmware and use it to flash my SGS2, since the /system partition will be wipe out, does it mean I will loose/corrupt my CSC part?
Thanks in advance.
ynamojn said:
I am sorry if my thread doesn't belong to this section. I have tried to search but I don't get satisfactory information. My questions are:
2. Do all CSC files reside in the /system/CSC folder?
No some are in the root of the system folder namely . CSC files txt CSC Version txt and SW Configuration xml
4. Is it possible to just flash the PDA/Phone(Modem)/CSC part individually? If I am not mistaken, we can use Odin just to flash the kernel.
Yes Modem CSC and Kernel can be individual Odin flashes .
PDA also if its a three part firmware .
jje
Click to expand...
Click to collapse
JJEgan said:
I am sorry if my thread doesn't belong to this section. I have tried to search but I don't get satisfactory information. My questions are:
2. Do all CSC files reside in the /system/CSC folder?
No some are in the root of the system folder namely . CSC files txt CSC Version txt and SW Configuration xml
4. Is it possible to just flash the PDA/Phone(Modem)/CSC part individually? If I am not mistaken, we can use Odin just to flash the kernel.
Yes Modem CSC and Kernel can be individual Odin flashes .
PDA also if its a three part firmware .
jje
Click to expand...
Click to collapse
Thanks for your answer. I have managed to open the cache.img. My conclusion is that if I flash without the CSC part, I will loose some apps and APN seetings. But the system will still be usable. I only need to manually input the APN setting.

[Q] Extract CSC from one part stock firmware [SOLVED]

So...my problem is that my provider (3AT) has the option to roam in another provider-net when the connection is bad.
In Settings I have the option to choose: Roaming on/Roaming off/Only national Roaming...but this option I have only in the branded provider firmware.
My idea was to extract the csc, flash a new rom, flash the extracted csc over it and voila: New firmware with the option "national roaming only"
Now my question: Does it work how I imagine it? :laugh:
2nd question: Who can do it? :angel:
Few infos: Galaxy SII GT-I9100
PDA: I9100XWLPG
PHONE: I9100NELP4
CSC: I9100DRELP4 (This is the one I want to flash on any other rom)
Thx for your help
Push
mhm...nobody?
Push
I guess you can try and see for yourself =)
Here are the steps for extracting CSC from a firmware file.
1. Download the firmware file from Sammobile website or Intratech's thread.
2. Extract cache.img and hidden.img files from the .tar.md5 firmware file using 7zip.
3. Bundle up cache.img and hidden.img to a .tar file using the following linux command (if you are using windows, you can install Cygwin to run the command).
tar -H ustar -cf csc.tar cache.img hidden.img
4. Flash csc.tar via Odin.
Hope that helps
waaahhh...thanks so much!!!! I'll try it and report back! :victory:
So...tried to bundle it with cygwin.
It writes that : No such file or directory
Where do I have to lay the img. files?
Ah...have it by trying it out =) They have to lay in:
...:\cygwin\home\...
So...report back:
I took the latest official stock firmware, extracted it with winzip, changed the hidden.img and cache.img (took the latest from 3AT)
bundled everything as u told me and voila: IT WORKS!!!! :victory::victory::victory::victory::victory:
Great! One tip for using cygwin: you can change your working directory to something other than the default cygwin/home by entering
cd c:
Or
cd d:
Sounds like the good old MS Dos
I did this method and flashed the csc.tar.
After doing this, it prompts an install in CWM. I installed it and nothing changes afterwards. What's am I doing wrong?
Packing the file
adotkdotjh said:
Great! One tip for using cygwin: you can change your working directory to something other than the default cygwin/home by entering
cd c:
Or
cd d:
Click to expand...
Click to collapse
Hi,
can I pack the files into csc.tar using 7zip?
I see it has such a option...
Cygwin is more difficult for me.
Thank you in advance.
Greetings!

[Q] Modifying Samsung factoryfs.img

---------------------------------------------------------------------------------
I posted this in the hacking section by mistake. I hope to get some help by posting this in the correct Q&A section.
I have a Samsung Galaxy Player 70 Plus (YP-GB70D) which is sold in Korea only (got it secondhand from ebay). I cannot find any development of this player (or the Korean development team is not willing to share), particularly on installation of CWM. I would at least like to have this rooted. I did manage to find copies of the OEM firmware in TAR format.
I read about dsixda's Android Kitchen. I installed Virtualbox on my Windows 7 machine to run ubuntu 12. I successfully installed Kitchen and used it to modify my TAR firmware. I know that this player is not on the list supported by Kitchen, but the modification process seemed to complete smoothly.
I notice that the modified firmware is in ZIP format suitable for flashing with CWM (as I said there is no CWM for this player). I renamed this to "update.zip" and tried Samsung's 3e recovery, but it rejected it saying "verification fails".
Further research shows that I can unpack the factoryfs.img in the TAR firmware, and manually add su / superuser into the system folders, then repack it back into factoryfs.img and then the TAR firmware, and use ODIN or Heimdall to flash it to the player. I have also successfully installed EXT4_UTILS on ubuntu and used it to unpack the factoryfs.img into an ext4 image, and mounted the unpacked image using this command:
Code:
sudo mount -o loop output.img tempdir
Unfortunately, the mounted image only allows you to see the content of the image, and you cannot add / delete / change anything inside. I tried modifying the permission of the folder of the mounted image, but no luck.
When I look at the output from Kitchen and the mounted image, I notice they have all the identical system folders and files (except su and superuser added in the Kitchen output). Therefore, I copied the "system" folder from Kitchen output and repacked it into factoryfs.img with EXT4_UTILS, and replaced the original factoryfs.img of the OEM firmware with the modified version (I repacked the TAR using 7zip).
Unfortunately, when I flashed the modified TAR with ODIN (which detected the player without problem), it said "failed" and aborted. When I used Heimdall (which detected the player without problem), it gave me a "usblib error -12" message and aborted. I have tried unsintalling the "Samsung USB driver for mobile phone" and reinstalling the Heimdall driver from zadig.exe, but no luck.
My questions are:
(1) Is there a way to make the mounted ext4 image of the EXT4_UTILS read/writable, so that I can modify the content and add su / superuser to "bin"?
(2) Does ODIN check whether the firmware is original (OEM) or custom, and reject custom firmware? If not, why would my method of replacing the "/system" folder of the original factoryfs.img with that from the Ktichen output fail?
Thanks for helping a noob out.
As I said I used Kitchen to generate a CWM-flashable zip of the rooted version of the original firmware. I repeated the experiment, this time replacing both factoryfs.img (made from repacking the modified /system from Kitchen output using EXT4_UTILS tool) and zImage (instead of just the factoryfs.img) of the original firmware with those from the Kitchen output, then repacking the whole thing into TAR.
This time ODIN worked and completed the flashing of the customized TAR and the player rebooted into recovery for update. Unfortunately, it failed with some red error messages (too fast for me to read through before the player rebooted again).
I notice in Download Mode, the "custom firmware count = yes (1)". I wonder if this is the reason why I cannot flash anything other than official firmware, because the Samsung recovery is blocking unofficial flashing from ODIN and also Heimdall (therefore the "libusb error -12").
I found three versions of the official firmware, one of which is rooted and flashable with ODIN. I wonder how someone can sneak su into the firmware and repackage it to an official Samsung firmware?

[Q] heimdall-frontend flash recovery img?

Hello how do i flash a recovery.img file using heimdall? all i get to choose from is .pit file, and of what i cna't find anywhere for gt-i9205. Since im a linux user this is a big issue. I have read about heimdall and forund out that i should put the recovery.img in the "heimdall" folder but where is it located? i have seen the executable file while browsing through all files in different directories but no heimdall folder anywhere.
Windows is one of the bigest problems for me since my computer seams to not like it, after install on this PC it just gets bluescreen, have tried everything from XP to W10B.
EDIT:
I just found out how to do it xD
i had to create the pit file for my device in heimdall, then select the recovery partition and select my recovery.img file, uncheck repartition, check No Reboot and check Resume (use after "No Reboot")
It all worked great, now running PhilZ Touch 6.48.4. Thanks anyway xD

flash firmware using heimdall for Linux

Heimdall for Linux and mac - this is a program that is used on Linux that's​ similar to Odin for windows. It is capable of flashing extracted tar firmware AP,CP,CSC,and BL using download mode for Samsung devices.
This is not my program.
Also I am limited to Linux for heimdall so testing Mac I can not do but Instructions to install will also be posted using a link
I am testing how to flash the s7 for others limited to Linux or mac.
Linux install of Heimdall on Linux:
Go to the official website here: http://goo.gl/PQC1RN
Scroll down and click on Download(for Linux)
Click to download the Heimdall version for your Linux version (EX. ubuntu13.04-heimdall_1.4.0-0_amd64.deb will work with 14.04 & 13.04 64bit)
Click and download the frontend if you don't like to work inside the terminal
Open your Downloads folder and click to install the files you downloaded
Remember to open Heimdall as Admin(sudo) so it works correctly
Mac install:
http://rootmygalaxy.net/install-odin...3-for-mac-osx/
Steps to flashing frimware on linux:
1. open terminal and type sudo heimdall-frontend
2. look for flash tab
3. extract firmware zip to a folder then create 4 more folders named AP,BL,CP,and CSC
4. Rename AP,BL,CP,CSC by removing the .md5 part of the file name leaving only the .tar at the end
5. Extract each tar to its specific folder
6. Under the flash tab look for pit file and click browse, goto CSC folder and click the pit file
7. Now look for add and from the list under partition details choose which file to add then click browse under it should have the file name you are looking for under partition details if unsure what to put, go through each folder you made and keep adding each file
8. then click start
This is capable of flashing the firmware , as in the pictures it shows it works and fails, i am thinking because i am flashing all at once instead of each folder separate, or in the wrong order
there are forums on xda on how to use heimdall more extensivly but im just doing this for the s7 so productive comments are welcomed
Also this is being tested on a sprint version of the s7 g930p that has been flashed to g930u firmware, in the pictures im flashing a firmware i already have installed just incase i mess up
Worked like a charm for me, this post needs more attention.
XCnathan32 said:
Worked like a charm for me, this post needs more attention.
Click to expand...
Click to collapse
U were able to get all firmware files flashed and able to use phone

Categories

Resources