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.
Related
How it started:
Okay, so I had some troubles getting botbrew (experimental) to install it's subcomponents so I had the bright idea to start fresh by:
Code:
# rm -rf /data/botbrew*
...without thoroughly checking the contents of the folder.
I later figured there were some symlinks to critical system files (or vise versa) within that directory because almost immediately multiple programs force closed such as the Android panel and there were FC windows on top of each other. *facepalm*
I tried to connect via adb and got this:
Code:
$ ./adblinux shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Rebooting leads to a persistent Samsung logo with adb response same as above. I can get into recovery mode though I'm not sure what, if anything, can be done in it to fix /system/.
I read elsewhere that the sh path is hardcoded:
http://forum.xda-developers.com/showthread.php?t=1877618
Luckily I have a "somewhat working" fallback device. However, is there any way to restore these files manually? There should still be a couple different copies of busybox on the device so... hopefully they could be leveraged to get it going again.
The first thing I did after seeing the failed adb connection was attempt to flash with several different stock roms using Odin, and then Heimdall for good measure, but they all failed with a junk message just prior to starting the flash (see attached example screenshot) while phone is in download mode.
[See next]
Update - Some Success.
I tried heimdall through the command line instead of the java GUI while specifying a PIT file and got a step further (yes!):
Code:
$ sudo heimdall flash --pit infuse.pit --factoryfs factoryfs.rfs
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
[webpage omitted]
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:
[webpage omitted]
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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 FACTORYFS
100%
FACTORYFS upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
After it rebooted, I was able to shell in with adb! I notice that /system/bin/sh does exist now, /sdcard is not mounted and the device now reboots systematically in a short period of time.
Running su gets:
Code:
$ ./adblinux shell
$ su
[1] Segmentation fault su
Any suggestions going forward?
Thank you in advance,
Mark
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'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
I've managed to accidentally brick my MI4C while flashing recovery. There is no way to boot now, no fastboot either.
Phone doesn't respond to charging cable, but I'm able to connect it to the PC in the EDL mode (shows up as Qualcomm HS-USB QDLoader 9008).
I've downloaded the QPST package and used the QFIL emergency flashing utility following a guide from xiaomifirmware.com.
QFIL always finishes without any error (tried waiting for >45 mins), however the ROM doesn't seem to be installed - and the phone is still completely dead.
Is there any hope left? Here is the output log from QFIL:
Code:
Validating Application Configuration
Load APP Configuration
COM:5
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\
RAWPROGRAM file path: C:\rawprogram0.xml
PATCH file path:C:\patch0.xml
Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
Process Index:0
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
***** Working Folder:C:\Users\______\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\______\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn
15:57:02: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8992_ddr.mbn"
15:57:02: 404664 bytes transferred in 0.094000 seconds (4.1055MBps)
15:57:02: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
15:57:02: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\______\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
The phones gets recognized by MiFlash, however any action results in ERROR 0x8000ffff: Receiving hello packet...
Any insight appreciated!
feek.404 said:
I've downloaded the QPST package and used the QFIL emergency flashing utility following a guide from xiaomifirmware.com. QFIL always finishes without any error (tried waiting for >45 mins), however the ROM doesn't seem to be installed - and the phone is still completely dead.
The phones gets recognized by MiFlash, however any action results in ERROR 0x8000ffff: Receiving hello packet...
Any insight appreciated!
Click to expand...
Click to collapse
With Xiaomi we generally use MiFlash rather than QPST/QFIL. I suppose you had tried the latest version of MiFlash but this device is old and an old version of MiFlash/MiPhone has to be used. Please get this 2015 version, it works for sure. Also for soft-brick recovery we use this old ROM "libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz" and then flash new stuff.
So, enter the EDL/9008 mode again and flash the old ROM with the old MiFlash.
Relax, it will be fixed :highfive:
k23m said:
With Xiaomi we generally use MiFlash rather than QPST/QFIL. I suppose you had tried the latest version of MiFlash but this device is old and an old version of MiFlash/MiPhone has to be used. Please get ..., it works for sure. Also for soft-brick recovery we use this old ROM "libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz" and then flash new stuff.
So, enter the EDL/9008 mode again and flash the old ROM with the old MiFlash.
Relax, it will be fixed :highfive:
Click to expand...
Click to collapse
Thank you, this version of MiFlash worked! :good:
I flashed the old 5.1 ROM with MiFlash, then the older TWRP version, then flashed the official 7.0 ROM, then unlocked bootloader, then the new TWRP, then my desired ROM and now I'm good to go again.
QFIL is such a finicky tool, I don't want to ever see that again haha
I got into a similar situation.
The device is bootlooping and does not have recovery or atleast it is not accessible. I can boot in fastboot mode. The bootloader is locked and it does not let me flash recovery or rom.
I have requested and got permision to unlock the phone but the unlocking fails at the second step (don't remember the mesaage right now, I'll try to update this response later).
I have tried flashing what is stated in this post but it did not work. If anyone could list the specific details required for each step I could give it a second try.
Anyone willing to help? Thanks
Nekronik said:
I got into a similar situation.
The device is bootlooping and does not have recovery or atleast it is not accessible. I can boot in fastboot mode. The bootloader is locked and it does not let me flash recovery or rom.
I have requested and got permision to unlock the phone but the unlocking fails at the second step (don't remember the mesaage right now, I'll try to update this response later).
I have tried flashing what is stated in this post but it did not work. If anyone could list the specific details required for each step I could give it a second try.
Anyone willing to help? Thanks
Click to expand...
Click to collapse
This is the output for the following commands:
$ fastboot getvar product:
product: MSM8992
finished. total time: 0.016s
$ fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: -0.000s
$ fastboot oem edl
< waiting for any device >
...
OKAY [ 0.000s]
finished. total time: 0.000s
The last command took some time to return even though it says 0.000.
I do see a 9008 in the devices admin.
Nekronik said:
This is the output for the following commands:
$ fastboot getvar product:
product: MSM8992
finished. total time: 0.016s
$ fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: -0.000s
$ fastboot oem edl
< waiting for any device >
...
OKAY [ 0.000s]
finished. total time: 0.000s
The last command took some time to return even though it says 0.000.
I do see a 9008 in the devices admin.
Click to expand...
Click to collapse
My problem was that MiFlash2015 did not let me communicate with the phone under edl mode. It simply refused to connect.
I have managed to recover it by attempting the recover method described above after disabling "Driver Signature Verification".
To disable it under windows 10, the easiest way I have found is to restart with driver signature verification turned off.
To do so: Configuration > Updates and Security > Recover > Reset now
Once the blue menu appears: Solve problems > Advanced options > Configure start > Reset
Then you will be prompted to select an option. It is probably to "F7" to disable signature verification.
Big thanks to @k23m for helping me recover the phone.
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.