Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)

2020-08-29 Thread Thorsten Glaser
Dixi quod… >Anyway, back to topic: the TWRP update went problemless, Ah, forgot: the manpage is completely, utterly shot and probably causes multiple lintian warnings as well ;-) it doesn’t honour the manpage format and doesn’t help the user much either. The description of the options is also

Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)

2020-08-29 Thread Thorsten Glaser
Nicholas D Steeves dixit: >So it looks to me like this bug fell through the cracks during the >process of changing submitter of your bugs from the former to the I didn’t, because I have my From set to the mirbsd.de address for historical reasons and mailing lists that check the Header-From :/

Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)

2020-08-14 Thread Nicholas D Steeves
Hi Thorsten! On Tue, Aug 04, 2020 at 02:34:01PM +, Thorsten Glaser wrote: > Hi Nicholas, > > >Re-sending this bug update to your debian.org address, because > >t...@mirbsd.de emitted the following during the last attempt > > yes, this is an issue with Googlemail not honouring internet >

Bug#880107: [RSVP] Re: Bug#880107: heimdall-flash: cannot flash RECOVERY on Samsung Note 3 (SM-N9005, hlte)

2020-08-04 Thread Nicholas D Steeves
Control: tag -1 moreinfo Dear Thorsten, On Sun, Oct 29, 2017 at 02:52:34PM +, Thorsten Glaser wrote: > 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