Your message dated Tue, 08 Feb 2022 08:59:56 -0700
with message-id
<87wni5uz5v.fsf@navis.i-did-not-set--mail-host-address--so-tickle-me>
and subject line Re: Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot
flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)
has caused the Debian Bug report #880107,
regarding heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005,
hlte)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
880107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880107
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: heimdall-flash
Version: 1.4.1-2+b1
Severity: normal
Tags: fixed-upstream
I get the dreaded “ERROR: Protocol initialisation failed!”
and “libusb error -7” when trying to update TWRP Recovery
on a used Note 3 device.
A self-compiled git snapshot cloned from upstream works,
at commit 9bcc42da350bd2e1766980bcb77d806a82d56a1d, so
updating the package should fix this.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.13.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages heimdall-flash depends on:
ii libc6 2.24-17
ii libgcc1 1:7.2.0-8
ii libstdc++6 7.2.0-8
ii libusb-1.0-0 2:1.0.21-2
heimdall-flash recommends no packages.
heimdall-flash suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
tag 880107 -moreinfo
thanks
On Sat, 29 Aug 2020 21:52:08 +0000 (UTC) Thorsten Glaser <[email protected]>
wrote:
>
> Anyway, back to topic: the TWRP update went problemless,
> so the bug can be closed.
>
Closing now
--- End Message ---
