I rooted my phone via SuperOneClick and installed red CWM. I used the generic ginger rom and then touchMIUIwiz. I accidently flashed CWM through rom manager and booted it into recovery only to find it giving me some kind of E: /cache error, and it was the yellow/goldenrod regular CWM with no option to flash zips or update. I went to a CWM thread and put the recovery.bin file in the system/bin folder I beleive and overwrote the existing one. I rebooted it again and it let me go into red cwm, so I flashed touchMIUIwiz again without wiping for fear of not being able to get cwm back again. It installed successfully but then got stuck on samsung start screen. ODIN wouldnt recognize it, and my first attempt got me from the yellow download mode to the "phone ! computer" screen and any attempts to boot or get me into download mode did the same. So I downloaded Heimdell and tried it, and this was my log:
[email protected][email protected]@[email protected]o.Buffer[email protected] to write C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\firmware.xmlAttempting to write C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\firmware.xmlAttempting to write C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32.zipAttempting to write C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32.zipSearching for heimdall in folder:C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\Searching C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32Searching for heimdall in folder:C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\DriversHeimdall Binary:C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe
###executing: C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe###Response from command "C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe":
v1.3.1Verifying C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\ . Result=trueResult=trueSet Temporary Folder:C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\Statics.setSystemInfo(): Windows Operating System: Windows
###executing: C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe###Response from command "C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe":
Usage: heimdall <action> <action arguments> <common arguments>
Common Arguments:
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
Action: flash
Arguments:
--repartition --pit <filename> [--factoryfs <filename>]
[--cache <filename>] [--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--param <filename>] [--kernel <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
or:
[--factoryfs <filename>] [--cache <filename>] [--dbdata <filename>]
[--primary-boot <filename>] [--secondary-boot <filename>]
[--secondary-boot-backup <filename>] [--param <filename>]
[--kernel <filename>] [--recovery <filename>] [--efs <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
Description: Flashes firmware files to your phone.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal, including bootloaders.
Action: close-pc-screen
Description: Attempts to get rid off the "connect phone to PC" screen.
Action: download-pit
Arguments: --output <filename>
Description: Downloads the connected device's PIT file to the specified
output file.
Action: detect
Description: Indicates whether or not a download mode device can be detected.
Action: dump
Arguments: --chip-type <NAND | RAM> --chip-id <integer> --output <filename>
Description: Attempts to dump data from the phone corresponding to the
specified chip type and chip ID.
NOTE: Galaxy S phones don't appear to properly support this functionality.
Action: print-pit
Description: Dumps the PIT file from the connected device and prints it in
a human readable format.
Action: version
Description: Displays the version number of this binary.
Action: help
Description: Displays this dialogue.
###executing: C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe###Response from command "C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe":
v1.3.1Found Heimdall Version: v1.3.1Connect your device in Download Mode to procede.Device not [email protected][email protected][email protected]@[email protected][email protected][email protected] Stock UVKG2 is ready for your device.
Ready for flash.FLASH ROUTINE INITIATED!!!![C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\heimdall-win32\heimdall.exe, flash, --pit, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\sk4g.pit, --6, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\zImage, --7, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\zImage, --22, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\factoryfs.rfs, --23, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\data.rfs, --24, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\cache.rfs, --11, C:\Users\Lance\AppData\Local\Temp\LanceHeimdallOneClick36F13297\modem.bin]nullnullHeimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading MODEM
MODEM upload failed!
Ending session...
Rebooting device...
ERROR: Failed to confirm end of file transfer sequence!
Device not connected.
Now its hung on the samsung boot screen again.
I searched and tried all the usual methods, nothings worked.
What are my next options?
This isn't to bump the thread, but I figured I should give everyone an update because I cant count how many times I've found someone with an exact same problem as me and they never update it and I stay completly lost.
So what I did was disconnect my phone and redo heimdall like 3 times, and I finally saw it ask for drivers. I clicked "options" on the pop up screens menu bar and clicked "show all devices" then selected something serial I think. It ran and failed on modem again, then I retryed it and it went from the "phone ! computer" (which is essentially a forced download mode) thing to the regular download mode. Then I relaoded hiemdall and clicked the "install bootloaders" thing and let it run. It took a bit, but I finally got it to stock.
I hope this helps somebody in the future.
I'm attemptimg to root my Galaxy S4 on Mac OSX using JODIN 3 and it cannot obtain a PIT file regardless of what I do. Here is the script mumbo jumbo I don't understand, but it might help you. I'm on an AT&T SGH-I537, btw.
Device Removed Device Connected /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/ElevateScript.sh: line 2: export: download-pit': not a valid identifier /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/ElevateScript.sh: line 2: export:--output': not a valid identifier /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/ElevateScript.sh: line 2: export: /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/part.pit': not a valid identifier Usage: heimdall <action> <action arguments>Action: close-pc-screenArguments: [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Attempts to get rid off the "connect phone to PC" screen.Action: detectArguments: [--verbose] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Indicates whether or not a download mode device can be detected.Action: download-pitArguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Downloads the connected device's PIT file to the specified output file.Action: flashArguments: --repartition --pit <filename> --<partition name>|--<partition identifier> <filename> [...] [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>] or: --<partition name>|--<partition identifier> <filename> [...] [--pit <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Flashes one or more firmware files to your phone. Partition names (or identifiers) can be obtained by executing the print-pit action.WARNING: If you're repartitioning it's strongly recommended you specify all files at your disposal.Action: helpDescription: Displays this dialogue.Action: infoDescription: Displays information about Heimdall.Action: print-pitArguments: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.Action: versionDescription: Displays the version number of this binary. /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/ElevateScript.sh: line 5: export:download-pit': not a valid identifier /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/ElevateScript.sh: line 5: export: --output': not a valid identifier /var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/ElevateScript.sh: line 5: export:/var/folders/b6/q60p7jfd0hxg0t4l9xgk13qc0000gn/T/CASUALbrannen04-signup1-2014-06-08-11.42.55/part.pit': not a valid identifier Usage: heimdall <action> <action arguments>Action: close-pc-screenArguments: [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Attempts to get rid off the "connect phone to PC" screen.Action: detectArguments: [--verbose] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Indicates whether or not a download mode device can be detected.Action: download-pitArguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Downloads the connected device's PIT file to the specified output file.Action: flashArguments: --repartition --pit <filename> --<partition name>|--<partition identifier> <filename> [...] [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>] or: --<partition name>|--<partition identifier> <filename> [...] [--pit <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Flashes one or more firmware files to your phone. Partition names (or identifiers) can be obtained by executing the print-pit action.WARNING: If you're repartitioning it's strongly recommended you specify all files at your disposal.Action: helpDescription: Displays this dialogue.Action: infoDescription: Displays information about Heimdall.Action: print-pitArguments: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>] [--usb-log-level <none/error/warning/debug>]Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.Action: versionDescription: Displays the version number of this binary.
Mac also keeps telling me to type in my password to allow osascript to make changes. Does that have something to do with it?
Sorry but we are not here for resolve troubleshootings but help navigate
But I can give you a link => [Release] JOdin3 CASUAL Cross Platform and Web-Based Flashing For Samsung Phones
Hello,
I'm not able to build (repackage) correctly system.img for SM-G361F, output is always rejected by both Odin (10.3.7) and Heimdall
I'm trying to repackage (pre-root) system.img taken from "G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5" (taken from ETL factory image named ETL-G361FXXU1APA2-20160202095551.zip )
Step-by-step:
1) tar xvf G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5 system.img
2) simg2img system.img system.img.raw
3) mount system.img.raw /mnt
4) made changes
5a) make_ext4fs -s -g 32768 -b 4096 -T -1 -S file_contexts -f -l 1843M system.repack.img /mnt/
5b) mkuserimg.sh -s /mnt system.repack.img ext4 system 1843M file_contexts
6) tar --owner 0 --group 0 --numeric-owner -H ustar -c system.img > G361F_SYSTEM.tar
7a) Load either system.img through Heimdall (PIT file downloaded through Heimdall is here: http://forum.xda-developers.com/showpost.php?p=65779994&postcount=146 )
7b) Load G361F_SYSTEM.tar in Odin v3.10.7 in AP tab and flash it
On ODIN/Download screen I can see that
1) FRP LOCK: OFF
2) KNOX: 0x0
3) System status: official
4) RP SWREV: S1, L1, M1
Notes
1) I have checked the box "OEM Unlock" in Developers settings to enabled
2) "file_contexts" is taken from booted up device through ADB (adb pull /file_contexts)
3) I've tried repackage the image without making any changes
4) When I compare original and repackaged images ("ls -lsaR" outputs), it seems like owner:group permissions are not persisted
5) I've tried both simg2img/make_ext4fs/mkuserimg.sh from CM12.1 repository (up to date today) and from https://github.com/ASdev/android_img_repack_tools (branch android-5.1.1)
6) I'm not sure about size 1843M, however flashing fails in the same manner when I go with 1536M and 2048M and anything between those two
7) Heimdall fails at about 6% of flashing single (sparse system.img) file with error "Failed to unpack received packet"
OSS Kernel for SM-G361F is here: https://github.com/smarek/G361F-Kernel
OSS Platform for SM-G361F is here: https://github.com/smarek/G361F-Platform
Questions are:
1) Is there anything special to be aware of when building for Samsung devices?
2) Did I miss or misunderstood any step in system.img repackaging process?
Hello,
I own a samsung xcover 3 (sm-g388f, android lollitop) and out of curiosity I start to be interested in the android system. I downloaded the ROM and get back the file boot.img, i try to get the file Image.gz (kernel) with Android Image Kitchen.
Code:
./unpackimg.sh boot.img
I get:
Code:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: boot.img
Setting up work folders...
Image type: AOSP-PXA
Footer with "SEAndroid" type detected.
Splitting image to "split_img/"...
BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE 0x10000000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 0x00008000
BOARD_RAMDISK_OFFSET 0x01000000
BOARD_SECOND_OFFSET 0x00f00000
BOARD_TAGS_OFFSET 0x00000100
BOARD_DT_SIZE 475136
BOARD_UNKNOWN 0x03000000
Unpacking ramdisk (as root) to "ramdisk/"...
Compression used: gzip
4739 blocs
Done!
I get the file boot.img-kernel, i use dumpimage:
Code:
./dumpimage -i boot.img-kernel -p 0 Image.gz
The return is:
Code:
./dumpimage: invalid option -- 'i'
Usage: ./dumpimage -l image
-l ==> list image header information
./dumpimage [-T type] [-p position] [-o outfile] image
-T ==> declare image type as 'type'
-p ==> 'position' (starting at 0) of the component to extract from image
-o ==> extract component to file 'outfile'
./dumpimage -h ==> print usage information and exit
./dumpimage -V ==> print version information and exit
I try the command:
Code:
./dumpimage -T boot.img-kernel -p 0 Image.gz
i get:
Code:
./dumpimage: Invalid type
I no longer see what to do, here is the boot.img
If anyone has an idea I’m interested
Thanks
I own a Samsung Galaxy A50s, I don't own a Windows (and can't get access to any Windows machine) so I guess Heimdall is my only way to go with my Ubuntu 20.04 (I tried Jodin, but didn't work and always stuck at "running"). Everyone who has been suggesting Heimdall didn't even even reply when I ask how to correctly use it. I've been looking for a decent tutorial for weeks, most tutorial, like this one mentioned vague statements, for instance :
"select all components you want to flash"
Click to expand...
Click to collapse
No, please tell me what I need to flash. I'm literally looking for tutorials for this information because I wouldn't know what to flash. Other tutorials I found are from a decade ago (2010, 2011, 2012, 2016), this one is quite recent from this year "How To Download Heimdall Flash Tool For Galaxy Devices" and was specifically directed for Samsung Galaxy too, however some components the OP mentioned don't event exist (anymore) in the latest Galaxy stock rom (both Android 10 and Android 11).
Here's the sample command arguments that are mentioned :
Code:
heimdall --repartition --pit <filename> [--factoryfs <filename>]
[--cache <filename>] [--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--param <filename>] [--kernel <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
These I can't find on my stock rom :
Code:
[–factoryfs]
[--dbdata]
[--hidden <filename>]
[--movinand <filename>]
[--data <filename>]
[--ums <filename>]
[--emmc <filename>]
[--partition identifier> <filename>]
[--kernel <filename>]
I wouldn't know which arguments are required or if it's ok if I just skip arguments that don't have corresponding files to my stock rom, but I have tried. I tried to flash with only arguments that match any file that I own from my stock rom, like this :
Code:
heimdall --repartition --pit A50S_SEA_OPEN.pit
--cache cache.img --primary-boot boot.img
--param param.bin --modem modem.bin
--system system.img --user-data userdata.img --fota fota.zip
But it just exists the command, I'm not sure what's going on (another reason why I need a clear tutorial) because there's no error information or anything, here the Heimdall output I have pasted on Gist. And also, there are some other components that I don't understand :
[–fota <filename>] : There are 2 fota zip files, in the AP folder (300-ish mb) and in CSC folder (2.5kb), which one I need to flash ?
Some tutorial suggestion would be helpful, or any correction to my command to make it work ? Thank you in advance.
[UPDATE]
Actually, I managed to use Heimdall using its GUI version (Frontend), it flashed everything by correctly putting file to its respective component in Heimdall. Unfortunately, it sent me into bootloop, I couldn't boot into system no matter how many times I tried to flash it with Heimdall.
Did you figure it out. Don't worry about the missing files.
pixie_laluna said:
I own a Samsung Galaxy A50s, I don't own a Windows (and can't get access to any Windows machine) so I guess Heimdall is my only way to go with my Ubuntu 20.04 (I tried Jodin, but didn't work and always stuck at "running"). Everyone who has been suggesting Heimdall didn't even even reply when I ask how to correctly use it. I've been looking for a decent tutorial for weeks, most tutorial, like this one mentioned vague statements, for instance :
No, please tell me what I need to flash. I'm literally looking for tutorials for this information because I wouldn't know what to flash. Other tutorials I found are from a decade ago (2010, 2011, 2012, 2016), this one is quite recent from this year "How To Download Heimdall Flash Tool For Galaxy Devices" and was specifically directed for Samsung Galaxy too, however some components the OP mentioned don't event exist (anymore) in the latest Galaxy stock rom (both Android 10 and Android 11).
Here's the sample command arguments that are mentioned :
Code:
heimdall --repartition --pit <filename> [--factoryfs <filename>]
[--cache <filename>] [--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--param <filename>] [--kernel <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
These I can't find on my stock rom :
Code:
[–factoryfs]
[--dbdata]
[--hidden <filename>]
[--movinand <filename>]
[--data <filename>]
[--ums <filename>]
[--emmc <filename>]
[--partition identifier> <filename>]
[--kernel <filename>]
I wouldn't know which arguments are required or if it's ok if I just skip arguments that don't have corresponding files to my stock rom, but I have tried. I tried to flash with only arguments that match any file that I own from my stock rom, like this :
Code:
heimdall --repartition --pit A50S_SEA_OPEN.pit
--cache cache.img --primary-boot boot.img
--param param.bin --modem modem.bin
--system system.img --user-data userdata.img --fota fota.zip
But it just exists the command, I'm not sure what's going on (another reason why I need a clear tutorial) because there's no error information or anything, here the Heimdall output I have pasted on Gist. And also, there are some other components that I don't understand :
[–fota <filename>] : There are 2 fota zip files, in the AP folder (300-ish mb) and in CSC folder (2.5kb), which one I need to flash ?
Some tutorial suggestion would be helpful, or any correction to my command to make it work ? Thank you in advance.
[UPDATE]
Actually, I managed to use Heimdall using its GUI version (Frontend), it flashed everything by correctly putting file to its respective component in Heimdall. Unfortunately, it sent me into bootloop, I couldn't boot into system no matter how many times I tried to flash it with Heimdall.
Click to expand...
Click to collapse
do you notice this: https://wiki.ubuntuusers.de/Heimdall/ ? I found it helpful - hope meanwhile you enjoy your device!
pixie_laluna said:
I own a Samsung Galaxy A50s, I don't own a Windows (and can't get access to any Windows machine) so I guess Heimdall is my only way to go with my Ubuntu 20.04 (I tried Jodin, but didn't work and always stuck at "running"). Everyone who has been suggesting Heimdall didn't even even reply when I ask how to correctly use it. I've been looking for a decent tutorial for weeks, most tutorial, like this one mentioned vague statements, for instance :
No, please tell me what I need to flash. I'm literally looking for tutorials for this information because I wouldn't know what to flash. Other tutorials I found are from a decade ago (2010, 2011, 2012, 2016), this one is quite recent from this year "How To Download Heimdall Flash Tool For Galaxy Devices" and was specifically directed for Samsung Galaxy too, however some components the OP mentioned don't event exist (anymore) in the latest Galaxy stock rom (both Android 10 and Android 11).
Here's the sample command arguments that are mentioned :
Code:
heimdall --repartition --pit <filename> [--factoryfs <filename>]
[--cache <filename>] [--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--param <filename>] [--kernel <filename>]
[--modem <filename>] [--normal-boot <filename>] [--system <filename>]
[--user-data <filename>] [--fota <filename>] [--hidden <filename>]
[--movinand <filename>] [--data <filename>] [--ums <filename>]
[--emmc <filename>] [--<partition identifier> <filename>]
These I can't find on my stock rom :
Code:
[–factoryfs]
[--dbdata]
[--hidden <filename>]
[--movinand <filename>]
[--data <filename>]
[--ums <filename>]
[--emmc <filename>]
[--partition identifier> <filename>]
[--kernel <filename>]
I wouldn't know which arguments are required or if it's ok if I just skip arguments that don't have corresponding files to my stock rom, but I have tried. I tried to flash with only arguments that match any file that I own from my stock rom, like this :
Code:
heimdall --repartition --pit A50S_SEA_OPEN.pit
--cache cache.img --primary-boot boot.img
--param param.bin --modem modem.bin
--system system.img --user-data userdata.img --fota fota.zip
But it just exists the command, I'm not sure what's going on (another reason why I need a clear tutorial) because there's no error information or anything, here the Heimdall output I have pasted on Gist. And also, there are some other components that I don't understand :
[–fota <filename>] : There are 2 fota zip files, in the AP folder (300-ish mb) and in CSC folder (2.5kb), which one I need to flash ?
Some tutorial suggestion would be helpful, or any correction to my command to make it work ? Thank you in advance.
[UPDATE]
Actually, I managed to use Heimdall using its GUI version (Frontend), it flashed everything by correctly putting file to its respective component in Heimdall. Unfortunately, it sent me into bootloop, I couldn't boot into system no matter how many times I tried to flash it with Heimdall.
Click to expand...
Click to collapse
Heimdall can be finicky, especially with new devices. I also don't have a Windows machine, but I've posted a way to use Odin on Linux here.