Homebrew O3DS possible hardbrick?

[CheatJoker008]

I've recently received a bricked old 3DS XL from my friend.
Not much is known about the 3DS except that it was hacked (duh). I don't know by which method it was hacked, or which firmware it was on.
According to my friend, he updated the firmware of the 3DS, and the next thing that he knows is that it's bricked.
Currently, when the power button is pressed, the power LED does light up, but it turns off the next moment.
Since the up + A + L + R button combination doesn't work, I'd imagine that it's not a soft brick, but I can't be sure as I don't really know much about these sorta stuff.
Judging from the current situation, can someone tell me whether the 3DS is hard bricked?
EDIT: Problem solved. The SD card was blank and arm9loaderhax.bin was missing. Should've just googled the symptom at the beginning *facepalm*

 

[Giodude]

I've recently received a bricked old 3DS XL from my friend.
Not much is known about the 3DS except that it was hacked (duh). I don't know by which method it was hacked, or which firmware it was on.
According to my friend, he updated the firmware of the 3DS, and the next thing that he knows is that it's bricked.
Currently, when the power button is pressed, the power LED does light up, but it turns off the next moment.
Since the up + A + L + R button combination doesn't work, I'd imagine that it's not a soft brick, but I can't be sure as I don't really know much about these sorta stuff.
Judging from the current situation, can someone tell me whether the 3DS is hard bricked?
EDIT: Problem solved. The SD card was blank and arm9loaderhax.bin was missing. Should've just googled the symptom at the beginning.

This isn't a brick, they just forgot Googleto put a file on the root. luma3ds and download the latest version (please don't download the source code). Put boot.firm on the console's sd card. What happens is that boot9strap is just a boot.firm launcher. If it can't find it, the console shuts off.

 

[CheatJoker008]

This isn't a brick, they just forgot Googleto put a file on the root. luma3ds and download the latest version (please don't download the source code). Put boot.firm on the console's sd card. What happens is that boot9strap is just a boot.firm launcher. If it can't find it, the console shuts off.

I realized that after I googled the 'blue light turns on and then off' problem. Thanks for replying anyway.

Each day I find myself being more and more stupid lol.

 

[Giodude]

By they way, brick rates are at an all time low at 0%. You can update and play online like normal with no worries what'soever.

 

[CheatJoker008]

By they way, brick rates are at an all time low at 0%. You can update and play online like normal with no worries what'soever.

Since I'm at it I might as well ask about ban cases now. Am I completely safe as long as I don't do crazy stuff such as playing games online or using freeshop etc.?

 

[Giodude]

Since I'm at it I might as well ask about ban cases now. Am I completely safe as long as I don't do crazy stuff such as playing games online or using freeshop etc.?

You can use freeshop. Just make sure you use Homebrew through Rosalina injection. You open up DS download play, open up the Rosalina menu, go to miscellaneous, switch hb title, then exit the app and reenter it. This completely hides what you're doing to Nintendo. You add Homebrew by putting the .3dsx in the 3ds folder. As for playing online, that is 100 percent safe, even if the game was aquired illegitimately. For more info, I suggest reading this post I wrote on exactly what cfw is and how it works:

I'm going to say this now so I can copy and paste this into other threads to explain exactly what a cfw is:
Basically, a cfw (Custom FirmWare), is several patches applied to the 3ds OS launched via some sort of exploit (in most cases b9s). These patches range from signature patches (allowing for the installation of CIA files with invalid tickets) to the Rosalina system module that pops up when L+DOWN+SELECT are held. Otherwise, there is no difference between a regular vanilla 3ds and a 3ds with a cfw launcher installed (as a cfw is never really installed. What is really being installed is something that launches a cfw. That's why godmode9 and other payloads can be loaded too). This means that the 3ds can be updated as normal, with no need to worry about losing games or saves. Updating functions just like normal. The same goes for updating games, which is discussed in detail later. In fact, you could install b9s (boot9strap) and use your 3ds like a completely normal 3ds, and there would be absolutely zero difference between that 3ds and a regular vanilla one. The only way to tell would be to send it in to Nintendo.
Due to a lack of account system on the 3ds at launch (Nintendo network IDs were shoehorned in later, and thus don't function quite right), all 3ds games acquired illegitimately (CIA files) function identically to games that were purchased and installed through legitimate means. This means that pirated games can be updated and played online just like normal games. The only exception to this is if the game is from a different region then the 3ds itself. Those games muse be updated via a dumped update CIA file, which are easy to come by.
Lastly there comes the fear of being banned from Nintendo's online services, which for the most part has been blown out of proportion. As stated earlier, a cfw 3ds is no different then a regular 3ds aside from a few patches here and there. This makes it 100 percent impossible for Nintendo to detect a console running a cfw, and thus impossible to ban. Even running gamesinstalled via a cia file from the internet are guaranteed to work fine online. Now this isn't to say that bans are impossible to come by. Many cfw users have been banned for unknown reasons. Though not much is known about these bans, there are several things that are known. 1: it is not caused by running a cfw or using pirated games. 2: users who do not use CIA Homebrew apps and instead use Rosalina 3dsx loading have been shown to be unbanned. 3: cheating online or playing leaked roms before they have been released will 100 percent result in a ban. From these clues, it can be concluded that people who simply use Rosalina to load 3dsx Homebrew instead of using custom Homebrew CIA files are nearly guaranteed to be safe from any future banwaves.
Again this might be a bit long to read, but I wanted to get this info out there, and so I would never have to bring this up ever again. People are free to quote this in their own posts if they feel this gets a good point across. I might update this post for updated information and/or spelling corrections. This was typed in the middle of the night on mobile so spelling mistakes are bound to be abundant.

You'll be safe as long as you hide your Homebrew with Rosalina injection and don't cheat online.

 

[CheatJoker008]

You can use freeshop. Just make sure you use Homebrew through Rosalina injection. You open up DS download play, open up the Rosalina menu, go to miscellaneous, switch hb title, then exit the app and reenter it. This completely hides what you're doing to Nintendo. You add Homebrew by putting the .3dsx in the 3ds folder. As for playing online, that is 100 percent safe, even if the game was aquired illegitimately. For more info, I suggest reading this post I wrote on exactly what cfw is and how it works:

You'll be safe as long as you hide your Homebrew with Rosalina injection and don't cheat online.

Thanks, that was very informative.