Homebrew just a theory.

[Joom]

They might be irresponsible, but at least with a9lh you can recover from a brick, which is why it is recommended.

Yeah, and it's not his fault for people not doing so. Again, we all assume the risk when doing any of this. Those of us that do have A9LH took on that risk as well, and those that bricked aren't coming in droves to blame Plailect's guide or anyone else. Honestly, this just seems like bullying, and I hate using that term. People singled him and his guide out, and spread false information through the poll on it just for the sake of discrediting him.

Thats not how this works. When you load luma with safehax, it has no brick protection, so something as simple as a cia download through FBI failing could brick the system.

Again, this is the user's fault, not his, and is irresponsible to claim that. Also, if a CIA fails to install with FBI it won't brick the system unless it's pertinent to the NAND itself. I don't care if what he posted doesn't have brick protection. That's on the end user, not him.

 

[ItsKipz]

Yeah, and it's not his fault for people not doing so. Again, we all assume the risk when doing any of this. Those of us that do have A9LH took on that risk as well, and those that bricked aren't coming in droves to blame Plailect's guide or anyone else. Honestly, this just seems like bullying, and I hate using that term. People singled him and his guide out, and spread false information through the poll on it just for the sake of discrediting him.

But it wasn't false information. His guide had the risk of bricking people's systems with a failed CIA install, and if someone cant get to a9lh using the very simple guide, they probably are bound to mess up FBI. A9LH, on the other hand, allows you to load payloads before home menu, enabling you to boot into hourglass/decrypt9 to load a NAND backup.

 

[FTRBND]

Yeah, and it's not his fault for people not doing so. Again, we all assume the risk when doing any of this. Those of us that do have A9LH took on that risk as well, and those that bricked aren't coming in droves to blame Plailect's guide or anyone else. Honestly, this just seems like bullying, and I hate using that term. People singled him and his guide out, and spread false information through the poll on it just for the sake of discrediting him.

Jesus Christ dude. People faked the pool to make sure no newbies end up using his guide and later on bricking their device due to a mistake of theirs that is unfixable. His thread was putting at risk those who have no experience with 3ds hacking or cfw. Wether short or long term is yours to decide.

 

[xtheman]

Yeah, and it's not his fault for people not doing so. Again, we all assume the risk when doing any of this. Those of us that do have A9LH took on that risk as well, and those that bricked aren't coming in droves to blame Plailect's guide or anyone else. Honestly, this just seems like bullying, and I hate using that term. People singled him and his guide out, and spread false information through the poll on it just for the sake of discrediting him.

His "Guide" was recommending people to boot unprotected sysnand. One fuck up and your done. The "Guide" doesn't have you make a emunand or nand backup so your screwed if you brick
He went as far as to give me editing rights after I explained the problem with the guide.

 

[ItsKipz]

Yeah, and it's not his fault for people not doing so. Again, we all assume the risk when doing any of this. Those of us that do have A9LH took on that risk as well, and those that bricked aren't coming in droves to blame Plailect's guide or anyone else. Honestly, this just seems like bullying, and I hate using that term. People singled him and his guide out, and spread false information through the poll on it just for the sake of discrediting him.


Again, this is the user's fault, not his, and is irresponsible to claim that. Also, if a CIA fails to install with FBI it won't brick the system unless it's pertinent to the NAND itself. I don't care if what he posted doesn't have brick protection. That's on the end user, not him.

Brick protection != just user error. a number of things could happen that would result in a brick. Also, the fact that he NEVER TESTED HIS OWN GUIDE says something about his credibility. What we were doing was not bullying, and if you look at the blog post he made i've actually ended up defending him from people telling him to "leave the community" but the guide was still bad.

 

[Joom]

But it wasn't false information. His guide had the risk of bricking people's systems with a failed CIA install, and if someone cant get to a9lh using the very simple guide, they probably are bound to mess up FBI. A9LH, on the other hand, allows you to load payloads before home menu, enabling you to boot into hourglass/decrypt9 to load a NAND backup.

His guide never covered CIA installation, so no, you're wrong. If a reader decided to install a CIA after following his guide then that's on them for not going through with the A9LH installation anyway.

 

[The Catboy]

Yeah, and it's not his fault for people not doing so. Again, we all assume the risk when doing any of this. Those of us that do have A9LH took on that risk as well, and those that bricked aren't coming in droves to blame Plailect's guide or anyone else. Honestly, this just seems like bullying, and I hate using that term. People singled him and his guide out, and spread false information through the poll on it just for the sake of discrediting him.

The issue is, his thread could have caused bricks with just one update or one bad CIA.
His guide was far more damaging to the end user because of the lack of protect and lack of fallback.
Then he turns around and make another thread after his thread has been removed, but calls it "theory." He's not helping, he's hurting the community by spreading an extremely dangerous method.

His guide never covered CIA installation, so no, you're wrong. If a reader decided to install a CIA after following his guide then that's on them for not going through with the A9LH installation anyway.

You aren't getting the point, his guide was purposed as basically an alternative to A9LH. Meaning people could use it instead of installing A9LH, putting their systems at a greater risk of bricking.

 

[TimX24968B]

this would be entirely unnecessary, as there are currently multiple alternatives, from A9LH to a proper emunand setup with luma.

why is this thread even here, is what I want to know...

 

[xtheman]

His guide never covered CIA installation, so no, you're wrong. If a reader decided to install a CIA after following his guide then that's on them for not going through with the A9LH installation anyway.

Isn't only logic to install .cias after installing cfw?
The a9lh guide barely touches on .cia installing but I see a ton of noobs install games fine.

 

[ItsKipz]

His guide never covered CIA installation, so no, you're wrong. If a reader decided to install a CIA after following his guide then that's on them for not going through with the A9LH installation anyway.

99% of people want luma for piracy/region free. His guide was saying "hey, remember all the cool shit a9lh can do? heres the easy way" but the "easy way" had a HUGE brick risk, used a very unstable loader, and has no backup capabilities, meaning if someone bricks in it they're SoL.

 

[Joom]

His "Guide" was recommending people to boot unprotected sysnand. One fuck up and your done. The "Guide" doesn't have you make a emunand or nand backup so your screwed if you brick
He went as far as to give me editing rights after I explained the problem with the guide.

And? Where were the protests when Pasta was popular which does the exact same thing?

Brick protection != just user error. a number of things could happen that would result in a brick. Also, the fact that he NEVER TESTED HIS OWN GUIDE says something about his credibility. What we were doing was not bullying, and if you look at the blog post he made i've actually ended up defending him from people telling him to "leave the community" but the guide was still bad.

...wut? The system isn't going to brick itself, so yes, it is due to user error. And yes, falsely claiming a guide caused a brick just for the sake of getting it trashed is bullying. Whether or not the guide was bad is irrelevant. The fact is that what he posted does not cause a brick.

Isn't only logic to install .cias after installing cfw?
The a9lh guide barely touches on .cia installing but I see a ton of noobs install games fine.

99% of people want luma for piracy/region free. His guide was saying "hey, remember all the cool shit a9lh can do? heres the easy way" but the "easy way" had a HUGE brick risk, used a very unstable loader, and has no backup capabilities, meaning if someone bricks in it they're SoL.

Irrelevant. Again, that's on the end user, not his guide. Also, I'm defending logic here, not just this random dude.

 

[ItsKipz]

And? Where were the protests when Pasta was popular?


...wut? The system isn't going to brick itself, so yes, it is due to user error. And yes, falsely claiming a guide caused a brick just for the sake of getting it trashed is bullying. Whether or not the guide was bad is irrelevant. The fact is that what he posted does not cause a brick.

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



Irrelevant.

1. We stated before that the system can brick for something in CIA install outside of user control, like an install fail or a disconnect during downloading.
2. We stated in the thread itself that we were voting that it had bricked to warn off noobs from using it, as our end goal was to prevent bricks.
3. Not directly, but it puts the system at risk. That's like saying malware isn't risky because it doesn't immediately break your PC.

 

[FTRBND]

And? Where were the protests when Pasta was popular which does the exact same thing?


...wut? The system isn't going to brick itself, so yes, it is due to user error. And yes, falsely claiming a guide caused a brick just for the sake of getting it trashed is bullying. Whether or not the guide was bad is irrelevant. The fact is that what he posted does not cause a brick.



Irrelevant.

Pasta is more in depth and it is stated that it is not noob friendly. His guide was said to be something for those who don't want to install a9lh.
Of course its user error, but with a9lh you can RECOVER from that. Newbies are much more likely to cause user errors and with his guide they wouldn't be able to do shit with a dual lcd brick.

 

[zoogie]

theoretically could the luma boot.3dsx be updated to detect if on a certain selection of firmwares exploit the arm11 using fasthax then use safefirmhax to get arm 9 access and then boot luma and patch the firmware withount a9lh but still having arm 9 and arm 11 access.


yes i know that it has no brick protection and that you should always install a9lh for brick protection and this could screw up sysnand with one bad file but i propose that if this is created an emunand is forced so you cannot use sysnand so a 0.001% chance of bricking sysnand and this could be used be with the new menuhax 11.1-11.2 for semi auto boot of luma by setting the button to boot menuhax right on the dpad an then setting boot when menuhax when this button is not pressed for semi auto luma boot and being able to boot stock sysnand by pressing right dpad.

and to get fbi you would inject fbi to health and safety on thath emunand then installing fbi, rebooting and launching decrypt 9 and injecting the stock health and safety.

fwiw what this forum did to you for just suggesting light cfw was completely rotten. I though you were distributing corrupted luma bins but I checked and they were the official releases. And people were lying about bricking their 3ds's to slander you. Awful.

The crap about light cfw being more dangerous than a9lh is also nonsense. It doesn't write to nand at all and if you want to tinker with system files and what not, you can just run emunand and do so safely. Just installing game cia's isn't going to hurt anything anyway.

 

[ItsKipz]

fwiw what this forum did to you for just suggesting light cfw was completely rotten. I though you were distributing corrupted luma bins but I checked and they were the official releases. And people were lying about bricking their 3ds's to slander you. Awful.

The crap about light cfw being more dangerous than a9lh is also nonsense. It doesn't write to nand at all and if you want to tinker with system files and what not, you can just run emunand and do so safely. Just installing game cia's isn't going to hurt anything anyway.

There's a reason why loading luma3ds via safehax is not officially supported. Also, how about the part where he didn't test his own guide?

just so you know, im not attacking him personally, im attacking his guide instead. i have no problems with the guy and he made a very nice apology after it was explained what the problem with the guide was.

 

[FTRBND]

The crap about light cfw being more dangerous than a9lh is also nonsense.

It might be just as likely to cause problems as a9lh, but it is 100% more likely to make those problems irreversible.
It's simply bad to suggest to anyone unfamiliar with cfw and homebrew that there is an "easy workaround" to getting cfw without a9lh.

 

[ItsKipz]

It might be just as likely to cause problems as a9lh, but it is 100% more likely to make those problems irreversible.

That's the wording i was looking for, thanks!

 

[The Catboy]

And? Where were the protests when Pasta was popular which does the exact same thing?


...wut? The system isn't going to brick itself, so yes, it is due to user error. And yes, falsely claiming a guide caused a brick just for the sake of getting it trashed is bullying. Whether or not the guide was bad is irrelevant. The fact is that what he posted does not cause a brick.



Irrelevant. Again, that's on the end user, not his guide. Also, I'm defending logic here, not just this random dude.

Pasta was never made to be userfriendly and had warnings all over it.
The guide may not have directly caused bricks, But ran a heavier risk of bricking. The method used in the guide had no fallback and thus anything that could go wrong, would only be able to be repaired through hardmod. Yes, I was wrong for accusing him of causing bricks and I do apologize for that.
The issue with the guide was that it was presented as an alternative to A9LH. Meaning if the user used it like A9LH, they increased their risks of bring bricked or removing their CFW through an update. It's not what the guide directly did, but the indirect side-effects that were the problems.

Look, I am not attacking the user. But I am going to call them out for making another thread based on their removed guide.

 

[Prot8toPot8to_]

*sigh* why did I start this shitstorm

 

[zoogie]

It might be just as likely to cause problems as a9lh, but it is 100% more likely to make those problems irreversible.

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. I really can't wait for sighax to release so we won't even have to argue about this any more.