Hi,
I've just installed the latest Heimdall (v1.3) to try to flash my Droid Charge, as I'm running Ubuntu and therefore ODIN is not an option. I was running GummyCharged GBE 2 with CWM Recovery, and wanted to flash the new modem. However, Heimdall seems unable to flash any files to my Droid and now when I turn on the phone I get this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been trying to use Heimdall to fix it, but no matter what I'm trying to flash, I get an error message very similar to this:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Expected file part index: 1761653664 Received: -1
KERNEL upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Re-attaching kernel driver...
I also get red text at the top left corner of the download mode screen that says "RX_TIMEOUT".
The "Expected file part index" is different depending on whether I'm trying flash RECOVERY, KERNEL, LTEMODEM, etc., but it seems to always receive a -1. Can anyone help with this, or simply point me to a resource that will let me get my phone back up and running (that works on Linux)?
Thanks for any assistance,
Dave
Are you flashing with battery in or out?
Battery is out, phone is in Download mode.
tlx45 said:
Battery is out, phone is in Download mode.
Click to expand...
Click to collapse
Put the battery back in after you're in download mode.
Same result unfortunately.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I'm having the exact same issue on a Mac with Loin running heimdall v1.3.1. Following the advice of this thread. I can get the pit to upload but nothing else. But that only bricked my phone worse. I can still get to the download mode but nothing rom related will ever upload. Anyone have ideas?
Part of my output with verbose.
Code:
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Uploading PIT
PIT upload successful
Uploading RECOVERY
0%ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
File Part #0... Response: 0 0 0 0 1 0 0 0
ERROR: Expected file part index: 0 Received: 1
RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: Failed to receive session end confirmation!
The libusb error -7 and RX_TIMEOUT leads be to believe that the charge is not receiving what ever the heck it wants. Tried using --delay but that seems to be for the handshake with Loke
With --verbose and --stdout-errors
Code:
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading RECOVERY
0%ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 1094576 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2104816 whilst receiving packet. Retrying...
Retrying...
File Part #0... Response: 0 0 0 0 2 0 0 0
ERROR: Expected file part index: 0 Received: 2
ERROR: Expected file part index: 26880 Received: 1606416092
RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error 2111712 whilst receiving packet. Retrying...
Retrying...
ERROR: Failed to receive session end confirmation!
ERROR: Failed to receive session end confirmation!
How I saved my Charge:
Odin 1.85
This pit file: http://forum.xda-developers.com/showthread.php?t=1111486
And EE4: http://forum.xda-developers.com/showthread.php?t=1172182
Let it boot
From here you can start from scratch. Hope this helps someone.
incharge said:
How I saved my Charge:
Odin 1.85
This pit file: http://forum.xda-developers.com/showthread.php?t=1111486
And EE4: http://forum.xda-developers.com/showthread.php?t=1172182
Let it boot
From here you can start from scratch. Hope this helps someone.
Click to expand...
Click to collapse
OP was asking about Heimdall specifically because he can't run Odin because he's on Linux.
Get Windows 7 (Microsoft gives away free 30-day trials), and use Odin.
Sent from my SCH-I510 using XDA App
shrike1978 said:
OP was asking about Heimdall specifically because he can't run Odin because he's on Linux.
Click to expand...
Click to collapse
As I was in the same predicament as the OP; after 12 hours of messing with heimdall I just ending up using a friends windows computer and about 10 minutes later my charge was working fine. I even tried emulating Odin with virtualbox and reactos then tryed wine but usb support became the issues for both. I tried everything but the only solution became this and it worked. Debloated EP3HA is amazing from EE4, it was worth the struggle.
Hello,
I recently try to flash my Lenovo TB-8703F under Lineage ROM.
But not my device is completly bricked and I can't power on it anymore.
When I try to flash it again under Download mode with QFLASH I get the following message :
HTML:
01:07:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
01:07:28: ERROR: function: sahara_main:854 Sahara protocol error
01:07:28: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
can you help me? I just want to revive this tablet.
I've join th full log in attchment.
Thank you in advance for your help.
Ptitsnake
Hello. I have been using RemixOs for a some weeks now but one day, when i was trying to boot it up, it showed this error message
error: no such device: RemixOS/kernel
error: file 'RemixOS/kernel' not found
alloc magic is broken at 0x7dfbcdao : 7df097ao.
please i need some help to get the system working again
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
I’ve just flashed the full firmware.
The SW REV check failures were fixed, but my device is still being boot looped
What to do next?
My A12 has MTK chipsets (according to my CPU-Z), hence also their ‘‘secure’’ boot locks, now going to unlock it by their SPFlashTool
speedmetal444 said:
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
Click to expand...
Click to collapse
Heimdall flashes are always by PIT partitions; PIT means partitioning informative tables
Odin flashes, on the other hand, are instead more by tar packages, namely BL, AP, CP, and CSC
* BL = BootLoaders; AP = Android PDA’s i.e. systems with also recoveries; CP = Core PDA’s i.e. modems; CSC = Country support codes or Consumer software customizations
I’m still being boot looped due to sth in unknown errors named PDP
Code:
Android recovery
samsung/a12nsxx/a12
11/RP1A.200720.012/A125FXXU1BUE3
...
Supported API: 3
# MANUAL MODE v1.0.0#
No commands specified
-- Wiping data ...
Formatting /data ...
E: [PDP] lstat /c___/pdp_b__: 0 - No PDP scenario
Formatting /cache ...
Formatting /metadata ...
Formatting /keydata ...
Formatting /keyrefuge ...
Data wipe complete.
hd_scania said:
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Click to expand...
Click to collapse
The error at the last is probably because the firmware you are trying to flash has older bootloader than what it is currently and it looks like you cannot downgrade bootloader.
I
How do i fix this in RSD lite thanks!!
ERROR: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.
i have no clue i'm flashing stock firmware on motorola device