Homebrew Question Need help with a potential bug

[blawar]

An issue was reported to our github repo where someone claimed:

Switch bricked when turning on airplane mode on network install of 10+GB nsp.

Don't even ask how I found this. I do have a nand backup, but still.

I was skeptical when I read this, because it feels like a troll. Why would someone turn on airplane mode in the middle of an install? How could installing a NSP even cause a brick? However, all things are possible with hacked consoles, so I left the issue open and told the user I would investigate.

Meanwhile, the github kept getting a slew of trolling "issues" being reported, and a friend of mine who works with me on the project went through and deleted all of the troll messages. Messages that had no community value like "go KYS". He accidentally deleted the brick ticket because he too thought it was someone troling.

So after he deleted this post, the user makes a reddit post:

https://www.reddit.com/r/SwitchHacks/comments/9x3o2r/warning_tinfoil_formerly_dz_has_a_bricking_bug/

At this point, I am still not sure if this guy is a troll, if he is, he is a very effective one. This guy seemed mostly honest (at least to the best of his ability), and he provided steps to reproduce, so i'll give him the benefit of the doubt and not call him a troll. It is quite possible that he did actually brick, but that it was unrelated to Tinfoil, such as he may have installed Brickachu and blamed Tinfoil for the brick by mistake.

Now, I have had several people test, and no one has been able to reproduce this bug. Its possible this bug does exist and is intermittent or only happens in certain conditions. So I would appreciate it if the community could help us test this (make sure you have a NAND backup), to see if someone can find the conditions to reliably cause a brick so we can fix it if it exists.

Here is a video of one of our tests, where we could not reproduce:

 

[masagrator]

Your video shows that You've used 0.97 version which was released after topic in reddit was created, so it's not reliable. You should use version of program which was latest on day of creating issue.

 

[pman152]

Never delete issues like that just because the bug seems unlikely, like that makes 0 fucking sense, test it and ask the user for extra info if you cant replicate.
No one goes to the trouble of signing up, reporting an issue with steps/info just to get you to delete it 5 seconds later.
Absolute rubbish dev if you actually deleted issues just because they sound unlikely.

--------------------- MERGED ---------------------------

And on the issue, chances are they used airplane mode when almost finished installing, possibly somewhere within trimmable byte positions.
Anything could really be the cause, but this does sound like a possible issue.
Does your app handle disconnects properly? Ask the user what version?

My guess is, he almost has it finished, turns on airplane mode, has most of the data "downloaded" but some data missing, it still tries installing as its a network install, probably some missing error handling, and it accidentally continues installation, installs corrupt file -> something fucks up.

Ask what he was installing too, could have been just a brick NSP.

 

[blawar]

Never delete issues like that just because the bug seems unlikely, like that makes 0 fucking sense, test it and ask the user for extra info if you cant replicate.
No one goes to the trouble of signing up, reporting an issue with steps/info just to get you to delete it 5 seconds later.
Absolute rubbish dev if you actually deleted issues just because they sound unlikely.

--------------------- MERGED ---------------------------

And on the issue, chances are they used airplane mode when almost finished installing, possibly somewhere within trimmable byte positions.
Anything could really be the cause, but this does sound like a possible issue.
Does your app handle disconnects properly? Ask the user what version?

My guess is, he almost has it finished, turns on airplane mode, has most of the data "downloaded" but some data missing, it still tries installing as its a network install, probably some missing error handling, and it accidentally continues installation, installs corrupt file -> something fucks up.

Ask what he was installing too, could have been just a brick NSP.

You are preaching to the choir, i wasn’t the one who deleted it. But it was an honest mistake, he is not a developer. we all make mistakes sometimes.

we are trying to rectify it, we resubmitted the issue on our github, and we are asking for help to locate the cause.

 

[pman152]

You are preaching to the choir, i wasn’t the one who deleted it. But it was an honest mistake, he is not a developer. we all make mistakes sometimes.

we are trying to rectify it, we resubmitted the issue on our github, and we are asking for help to locate the cause.

Fair enough but no one should be deleting issues, theres a lock button for a reason.

 

[blawar]

Never delete issues like that just because the bug seems unlikely, like that makes 0 fucking sense, test it and ask the user for extra info if you cant replicate.
No one goes to the trouble of signing up, reporting an issue with steps/info just to get you to delete it 5 seconds later.
Absolute rubbish dev if you actually deleted issues just because they sound unlikely.

--------------------- MERGED ---------------------------

And on the issue, chances are they used airplane mode when almost finished installing, possibly somewhere within trimmable byte positions.
Anything could really be the cause, but this does sound like a possible issue.
Does your app handle disconnects properly? Ask the user what version?

My guess is, he almost has it finished, turns on airplane mode, has most of the data "downloaded" but some data missing, it still tries installing as its a network install, probably some missing error handling, and it accidentally continues installation, installs corrupt file -> something fucks up.

Ask what he was installing too, could have been just a brick NSP.

i’m on mobile, i’ll reply to your other questions when i get home.