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 would like to enlarge the data partition of my Samsung S2 I9100, and there is a good thread about it here.
It has the command to flash the PIT as
Code:
$ heimdall flash --repartition --pit newpit.pit
But heimdall is refusing to flash, I guess because I have to specify all partitions with the same command:
Code:
$ heimdall flash --repartition --pit I9100_16GB_6GBdata.pit
Action: flash
Arguments:
--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.
It's heimdall 1.4.0. Is it not possible anymore to flash just the PIT?
P.s.: Of course it is dangerous, I know, I diffed old and new PIT file and only the data and ums partitions seem to change.
I am trying to compile an Orange Fox custom recovery for poco x2 device. Source sync was 100% and I generated device tree using SebaUbuntu's Script. When I try to compile, I get this error. What is it and how can I fix it...
Code:
[ 99% 13183/13195] Target boot image: /home/koken/Desktop/orangefox/out/target/product/phoenix/boot.img
FAILED: /home/koken/Desktop/orangefox/out/target/product/phoenix/boot.img
/bin/bash -c "(/home/koken/Desktop/orangefox/out/host/linux-x86/bin/mkbootimg --kernel /home/koken/Desktop/orangefox/out/target/product/phoenix/kernel --ramdisk /home/koken/Desktop/orangefox/out/target/product/phoenix/ramdisk.img --base 0x00000000 --pagesize 4096 --cmdline \"console=ttyMSM0,115200n8 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 androidboot.usbcontroller=a600000.dwc3 swiotlb=2048 loop.max_part=7 cgroup.memory=nokmem,nosocket androidboot.selinux=permissive androidboot.init_fatal_reboot_target=recovery buildvariant=eng buildvariant=eng\" --os_version 16.1.0 --os_patch_level 2099-12-31 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --header_version 2 --dt device/xiaomi/phoenix/prebuilt/dtb.img --output /home/koken/Desktop/orangefox/out/target/product/phoenix/boot.img ) && (true )"
Traceback (most recent call last):
File "/home/koken/Desktop/orangefox/out/host/linux-x86/bin/mkbootimg", line 216, in <module>
main()
File "/home/koken/Desktop/orangefox/out/host/linux-x86/bin/mkbootimg", line 206, in main
args = parse_cmdline()
File "/home/koken/Desktop/orangefox/out/host/linux-x86/bin/mkbootimg", line 191, in parse_cmdline
raise ValueError('header_version and dt cannot be set at the same time')
ValueError: header_version and dt cannot be set at the same time
[ 99% 13185/13195] build /home/koken/Desktop/orangefox/out/target/pro...ct/phoenix/obj_arm/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin
ninja: build stopped: subcommand failed.
04:38:54 ninja failed with: exit status 1
Disabling this line fixed it for me:
> cat BoardConfig.mk | grep header_version
#BOARD_MKBOOTIMG_ARGS += --header_version $(BOARD_BOOTIMG_HEADER_VERSION)
I performed a factory reset on my Redmi Note 6 Pro and it seems things went wrong as it now won't boot. When I turn it on, I get the Mi.com screen for a few seconds then nothing. I did some googling and decided to try a fastboot flash. This did not work with an error "Flash xbl error"
Here is the log:
MiFlash 2020.3.14.0
vboytest index:1
idproduct: 53261 idvendor: 6353
Thread id:10 Thread name:95c0959
image path:C:\Users\User\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global
env android path:"C:\Users\User\Desktop\MIUI_Flash\Source\ThirdParty\Google\Android"
script :C:\Users\User\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\flash_all_lock.bat
Physical Memory Usage:1044480 Byte
start process id 2968 name cmd
info1:$fastboot -s devicename getvar product 2&1 | findstr /r /c:"^product: *tulip" || echo Missmatching image and device
info1roduct: tulip
info1:$fastboot -s devicename getvar product 2&1 | findstr /r /c:"^product: *tulip" || exit /B 1
info1roduct: tulip
info1:$set CURRENT_ANTI_VER=4
info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s devicename getvar anti 2&1 | findstr /r /c:"anti:"') do (set version=%i )
info1:$(set version=4 )
info1:$if [4] EQU [] set version=0
info1:$if 4 GTR 4 (
info1:echo current device antirollback version is greater than this package
info1: exit /B 1
info1
info1:$fastboot -s devicename flash xbl C:\Users\User\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images\xbl.elf ||
info2:Sending 'xbl' (2504 KB) OKAY [ 0.078s]
info1:"Flash xbl error"
info2:Writing 'xbl' FAILED (remote: 'Flashing is not allowed in Lock State')
info2:fastboot: error: Command failed
begin FlashDone
error:"Flash xbl error"
process exit.
flashSuccess False
isFactory False CheckCPUID False
before:flashSuccess is False set IsUpdate:True set IsDone True
after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
Can anyone assist? I see the "flashing is not allowed in lock state" message but my various googlings seem to suggest I shouldn't need to unlock? Perhaps I do (I did start down that path but got a bit stuck - will persevere if that is the issue).
Managed to get into Recovery mode on the device and that fixed it. No need to flash after all.
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.