Homebrew just a theory.

  • Thread starter Thread starter tunip3
  • Start date Start date
  • Views Views 5,377
  • Replies Replies 65
  • Likes Likes 1
Status
Not open for further replies.
Explain to me how mcu rebooting with sig patches and installing pokemon can brick your nand?
Everything is done as live patches in RAM.

Completely overwriting your new 3ds nand with old3ds firm 2.1 derived from someone else's system. What could go wrong.
Maybe you should consult @vb_encryption_vb and maybe he can better testify on the real risk of a9lh. Last I check, business was very good for him. Before you shout, "But, user error!", please note that not everybody has the same amount of computer literacy, and going through the plailect guide and it's dozens of steps is an accident waiting to happen for some people.

I'm not saying a9lh should be avoided - certainly not. I have it on several systems and love it. But for someone with a single system they can't afford to lose, I can see LCFW as a temporary way for a user to "try before they buy" and see if cfw is worth the risk for what they're getting in return.
>try before they buy
>LCFW has no way to recover if something goes wrong
>risk

kek


The fact remains, all CFW, be it a9lh or LCFW, has risks. However, a9lh has a backup plan where you can load a nand backup and/or a CTRTransfer in order to "save" a device, but LCFW has none.
 
  • Like
Reactions: TimX24968B
>try before they buy
>LCFW has no way to recover if something goes wrong
>risk

kek
> something goes wrong
You. Are. Not. Writing. To. Nand. With. Lcfw.

Just fire up freeshop, install your games, and you'll be fine.
 
  • Like
Reactions: BL4Z3D247
> something goes wrong
You. Are. Not. Writing. To. Nand. With. Lcfw.

Just fire up freeshop, install your games, and you'll be fine.
So theres a 0% chance that anything could go wrong? How far are you willing to go with that? no matter what happens, CFW IS RISKY. let me repeat that...

CFW

IS

RISKY!!!

There is always a chance of a device brick! I saw a thread earlier today about a user bricking from using a simple homebrew app, plus user error has to be taken into the equation! Either way, a9lh simply has the tools to save a bricked device, whereas LCFW/MenuHax users have NONE WHATSOEVER.
 
This seems sort of like having a guide on how to climb a mountain without a harness. With everyone saying it's totally on the user if they miss a handhold or slip and fall to their deaths. The guide itself doesn't tell you to slip, so it can't be blamed. Yeah, right.
 
  • Like
Reactions: crazy_p
This seems sort of like having a guide on how to climb a mountain without a harness. With everyone saying it's totally on the user if they miss a handhold or slip and fall to their deaths. The guide itself doesn't tell you to slip, so it can't be blamed. Yeah, right.
thats called failing to know the risk of your activity.
 
I said that some sort of being forced emunand should be put in place though to stop SYSNAND bricking
 
There is always a chance of a device brick! I saw a thread earlier today about a user bricking from using a simple homebrew app, plus user error has to be taken into the equation! Either way, a9lh simply has the tools to save a bricked device, whereas LCFW/MenuHax users have NONE WHATSOEVER.


Would you like to bet on that.. I have $1k that says I can brick a console that a9lh can't recover from and only a hardmod will fix it.
 
Would you like to bet on that.. I have $1k that says I can brick a console that a9lh can't recover from and only a hardmod will fix it.
That is more of an intentional brick. If you don't try to actually brick your device, whatever you do will be recoverable.
 
Blaming the OP is like blaming gun manufacturers for a psycho going on a killing spree. I'll even go old school, if I told someone to jump off a bridge is that my fault? It's not the OP's fault people don't understand the risk of any mod/hack, ESPECIALLY an untested/unofficial one. The users who bricked took a risk without looking at what's at stake. Plain and simple. Stop bashing the OP for another's incompetence. He didn't FORCE anyone to do what he said.
 
  • Like
Reactions: BADDINOROX99
Blaming the OP is like blaming gun manufacturers for a psycho going on a killing spree. I'll even go old school, if I told someone to jump off a bridge is that my fault? It's not the OP's fault people don't understand the risk of any mod/hack, ESPECIALLY an untested/unofficial one. The users who bricked took a risk without looking at what's at stake. Plain and simple. Stop bashing the OP for another's incompetence. He didn't FORCE anyone to do what he said.
He didn't force anyone but he encouraged them to take an unsafe path. If you told someone to jump off a bridge you would be accountable for their death, since you encouraged them to.
 
  • Like
Reactions: Quantumcat
He didn't force anyone but he encouraged them to take an unsafe path. If you told someone to jump off a bridge you would be accountable for their death, since you encouraged them to.
The only way I'd agree with you is if these people who bricked aren't mentally sound. That's the only way anyone would be held accountable for someone jumping off a bridge because they were told to. If you're of sound mind you would know better not to jump and it would fall on the person who jumped.
 
The only way I'd agree with you is if these people who bricked aren't mentally sound. That's the only way anyone would be held accountable for someone jumping off a bridge because they were told to. If you're of sound mind you would know better not to jump and it would fall on the person who jumped.
If you were of sound mind you would also decide to follow the official guide and not a method of someone who hasn't even tested it.
 
If you were of sound mind you would also decide to follow the official guide and not a method of someone who hasn't even tested it.
So what about the people who brick from tested and stable mods/hacks. Who's to blame? Plailect? But the person wasn't sound mind enough to use it, still Plailect's fault? People need to just own up to their stupid decisions and stop pointing fingers. The OP had a theory, I don't care if he gave directions how to do it or not. It was an untested theory that people took upon themselves to be a guniue pig and try. If I told someone to flash a PSP fiwmware to their 3DS and they do it, that's my fault? Please. Everyone here knows that would be a bad idea. The users who bricked should've known better and now they do.
 
So theres a 0% chance that anything could go wrong? How far are you willing to go with that? no matter what happens, CFW IS RISKY. let me repeat that...

CFW

IS

RISKY!!!

There is always a chance of a device brick! I saw a thread earlier today about a user bricking from using a simple homebrew app, plus user error has to be taken into the equation! Either way, a9lh simply has the tools to save a bricked device, whereas LCFW/MenuHax users have NONE WHATSOEVER.
How did someone brick using a homebrew app?!
 
They bricked using a Homebrew app by being a special kind of stupid that's how

but seriously I didn't think that was possible
Some homebrew apps mess with NAND, and have a possibility of bricking if they have an error. a9lh would be able to save those consoles, however, as you could flash a NAND backup.
 
Some homebrew apps mess with NAND, and have a possibility of bricking if they have an error. a9lh would be able to save those consoles, however, as you could flash a NAND backup.
wow I really didn't think it was possible to brick using homebrew apps since I hardly enter the homebrew munu
Link to thread?
I was only kidding because of what someone posted before me
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum