muzz

Anyone else getting this at the moment?

" - Reason: The underlying connection was closed: The connection was closed unexpectedly."

N has done me well. Sent a brick in that did not have a vulnerable boot1. They sent back an older console LU5X and it had sysmenu 3.4 installed. I would've thought it would have a higher version but guess not. And only 4 bad blocks on NAND. I wanted to post this in case anyone has been hesitant to send in, you may get lucky as I did. Also the turnaround time was less than 5 days. I would've paid for the repair had they determined foul play but I'll take things the way they are.

I tried asking in another dead thread so I'll try one more time with a new one. I aquired a semi-brick....wrong region sysmenu installed. I had a bad sysmenu wad for the correct region that failed. Instead of NUSing a fresh wad like I should have and installing that I thought I'd delete the sysmenu and try to reinstall thinking for one reason or another it was having trouble overwriting. Since it began installing and failed mid way I lost preloader in the processs. Yes, foolish to do this with an imperative file to the system operation. So, after this idiot move, I get a good sysmenu wad while sitting idle in HBC.....I notice wiimotes don't sync in HBC now, I plug in a GC controller and can navigate again. After I think I saved my ass I copied a new NUSed sysmenu to the card and reload HBC.....I go into wadmanager.....no GC controller support. I knew I was screwed then. I had no way to navigate select the wad and press A to install or gracefully exit the app. I sat shaking my head realizing my stupidity even more then I I hit reset knowing well; game over......

Without vunerable boot1 I am guessing an infectus is not going to help me. Without a nand flasher can anyone advise a different way to work with this? I do not have a nand backup and wonder if a preprogrammed autobooting chip would allow me to run wadmanager autoboot disc or would I still have the same problem and still be unable to navigate assuming the autoboot chip would start the disc. Savemii does not work since there is no sysmenu, I've tried. Thanks in advance

Last night I was setting up a new USB HDD and was running homebrew from HBC on it. It seems that two of the loaders I tried USB Loader GX and CoverFloader dump when they are invoked via HBC on USB drive when attempting to mount WBFS. I've not tried others yet. To see if this was a universal scenario I tried Wad Manager and was able to select USB HDD as the source of my Wads and install without dump so I know it's possible for an app launched via USB to again access USB. Is this being looked into as a solution? Even though it's slower I'm looking forward more to using USB as my primary homebrew source. If not I can provide the stack info later and maybe this can become a viable way to use USB loaders when run from FAT partition on USB? Again, sorry if this has already been brought up. Cheers!