Homebrew Question HBG shop new update and no full ram access

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
You never had prodinfo brick protection, even scires admits its a near worthless meme. It was a false sense of security. It didn't stop bricks, it caused some bricks, and generally annoyed most users. The BIS "protection" code in atmosphere is pretty much just a disaster.
Please explain how it was a disaster or where SciresM said it was "worthless."

The protections are not 100% effective, but they're better than nothing. The fact that Incognito is incompatible is irrelevant, since you only need to run Incognito once to install it, and it's easy to do.
 

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
Please explain how it was a disaster or where SciresM said it was "worthless."

The protections are not 100% effective, but they're better than nothing. The fact that Incognito is incompatible is irrelevant, since you only need to run Incognito once to install it, and it's easy to do.

They arent even 1% effective. To bypass the protection, a homebrew app just needs to write the flag file to the sd card. Think about it, if nand writes were blocked by atmosphere, how would choi install system updates? Choi writes the flag itself to the SD card, to give itself write access to your nand, and then writes to it. This is why atmosphere's bis protection is a meme and completely worthless.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
They arent even 1% effective. To bypass the protection, a homebrew app just needs to write the flag file to the sd card. Think about it, if nand writes were blocked by atmosphere, how would choi install system updates? Choi writes the flag itself to the SD card, to give itself write access to your nand, and then writes to it. This is why atmosphere's bis protection is a meme and completely worthless.
  1. All of the prodinfo brickers that preceded this (and caused the protection to be implemented in the first place) are defeated by this protection.
  2. You can't argue that the protection is pointless while simultaneously arguing that it gets in the way of Incognito. If it's so easy to bypass the protections, do it. If it's more trouble than it's worth, then the protections aren't worthless.
  3. You haven't shown me where SciresM said the protections are "worthless."
  4. You haven't shown me where the protections have actually caused bricks.
  5. CAL0 isn't writeable with flags, only readable, and you know that is why Incognito doesn't work and why the protection isn't worthless.
  6. This doesn't address any of the other problems with your malicious additions to Tinfoil.
  7. This doesn't address the the pretense for the malware being nonsense.
 
  • Like
Reactions: Ashura66

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
Im confused, are you challenging me to write an atmosphere bricker? because that is trivial. Brickachu came out like 4 months before atmosphere implemented its bis write, and the latest XCI bricker did affect atmosphere.

As for the protection causing bricks, search the incognito thread. It is not recommend to run incognito on vanilla atmosphere because sometimes atmosphere lets some of the writes through, bricking the user.

You can sit there and cry about it, call it malware, whatever you want. The fork stays, and no amount of whining is going to change that. So you can either cry about it some more in this thread, accuse it of touching you whatever, or you can get over it or use a different installer? I'm sorry you dont like the changes I made to atmosphere, you are free to file a complaint to our customer service department.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
Im confused, are you challenging me to write an atmosphere bricker?
No. If you are going to argue the protections are easily bypassed, do so with Incognito. You can't whine that the protections suck because they interfere with Incognito while simultaneously arguing the protections are trivial. Which is it?

Brickachu came out like 4 months before atmosphere implemented its bis write,
Yes, and?

and the latest XCI bricker did affect atmosphere.
Yes, and?

As for the protection causing bricks, search the incognito thread. It is not recommend to run incognito on vanilla atmosphere because sometimes atmosphere lets some of the writes through, bricking the user.
You seem to be confusing "Atmosphere caused bricks" with "Incognito caused bricks."

You can sit there and cry about it, call it malware, whatever you want.
Telling me I'm "crying about it" doesn't mean it's not malware. I'm going to call out malware when I see it. At the very least, you can acknowledge the changes in the changelog instead of being deceptive about imaginary bugs or whatever.

The fork stays, and no amount of whining is going to change that.
Well, I'm using it without the malware, so no.

So you can either cry about it some more in this thread, accuse it of touching you whatever, or you can get over it or use a different installer?
Arguing against a crying strawman instead of actually refuting my points above doesn't help the case that it's not malware.

So you can either cry about it some more in this thread, accuse it of touching you whatever, or you can get over it or use a different installer?
As I already said near the beginning, I can't recommend using Tinfoil with the malware attached. Thanks though for giving me permission to do what I already said I'd be doing.

I'm sorry you dont like the changes I made to atmosphere, you are free to file a complaint to our customer service department.
If your goal isn't to make useful tools or to desire feedback to make your tools better, what are you even doing here? The malware is bad and disliked. If that doesn't bother you, great, but that doesn't really make sense if your goal is to make good tools that people like. I could be wrong, but my guess is that's not your goal.
 
  • Like
Reactions: Herald and Ashura66

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
According to his words, he already did that with Incognito.

No, atmosphere bricked the user. Had atmosphere allowed all of the writes through, it would not have bricked. Byt blocking some of the writes and not others, atmosphere caused the brick.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
No, atmosphere bricked the user. Had atmosphere allowed all of the writes through, it would not have bricked. Byt blocking some of the writes and not others, atmosphere caused the brick.
If your app is incompatible with Atmosphere and caused a brick, Incognito caused the brick.

If I published an app that bricked my PC because it was incompatible with the latest version of Windows 10, particularly if the app was designed to modify crucial system files, the app is what bricked the computer, not Windows 10. In fact, to make this analogy work, my app is published months after the new version of Windows 10 is released.

Sorry, buddy.
 

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
If your app is incompatible with Atmosphere and caused a brick, Incognito caused the brick.

If I published an app that bricked my PC because it was incompatible with the latest version of Windows 10, particularly if the app was designed to modify crucial system files, the app is what bricked the computer, not Windows 10. In fact, to make this analogy work, my app is published months after the new version of Windows 10 is released.

Sorry, buddy.

Negative, there is a bug in atmosphere that caused the brick by not reliably blocking all nand writes, directly causing corruption of the nand. Incognito states it is not compatible with atmosphere, feel free to open a github issue with atmosphere about its brick bug, or run my fork

it’s actually really ironic that the atmosphere feature that is supposed to prevent bricks, causes bricks.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
Negative, there is a bug in atmosphere that caused the brick by not reliably blocking all nand writes, directly causing corruption of the nand. Incognito states it is not compatible with atmosphere, feel free to open a github issue with atmosphere about its brick bug, or run my fork

it’s actually really ironic that the atmosphere feature that is supposed to prevent bricks, causes bricks.
If Incognito has to be labeled as not compatible with Atmosphere because it allegedly causes bricks on Atmosphere, then Incognito is what causes bricks on Atmosphere. Atmosphere isn't bricking systems by itself. Please re-read my analogy. Even if we agree the brick happens because of what you describe as a "bug" with Atmosphere, it's still Incognito causing the brick. However, we're arguing semantics at this point.

I am not calling Incognito a bad piece of software. I like Incognito. However, it's blatantly incorrect to say "Atmosphere bricks the user." It's "using Incognito with Atmosphere" that allegedly bricks the user. I use the word "allegedly" because I just scoured the Incognito thread, and although I could have missed it, I didn't find a single case of a brick on Atmosphere caused by Incognito.

Also, we are way off-topic, and you haven't addressed most of my points about your unnecessary malware in Tinfoil.
 
  • Like
Reactions: Ashura66

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
If Incognito has to be labeled as not compatible with Atmosphere because it allegedly causes bricks on Atmosphere, then Incognito is what causes bricks on Atmosphere. Atmosphere isn't bricking systems by itself. Please re-read my analogy. Even if we agree the brick happens because of what you describe as a "bug" with Atmosphere, it's still Incognito causing the brick. However, we're arguing semantics at this point.

I am not calling Incognito a bad piece of software. I like Incognito. However, it's blatantly incorrect to say "Atmosphere bricks the user." It's "using Incognito with Atmosphere" that allegedly bricks the user. I use the word "allegedly" because I just scoured the Incognito thread, and although I could have missed it, I didn't find a single case of a brick on Atmosphere caused by Incognito.

Also, we are way off-topic, and you haven't addressed most of my points about your unnecessary malware in Tinfoil.


You are correct, your ranting have made me see the error in my ways, i’ll just block all atmosphere next patch problem solved right?
 

HtheB

Well-Known Member
Member
Joined
May 15, 2006
Messages
877
Trophies
1
Age
36
Location
Bize Her Yer Trabzon
Website
www.HtheB.com
XP
3,058
Country
Netherlands
You are correct, your ranting have made me see the error in my ways, i’ll just block all atmosphere next patch problem solved right?
I would say: Do it!
I always wonder why Atmosphere users whine about everything and trying to start a flame war....
I've never saw SX OS users doing that (:
blawar ftw
 
  • Like
Reactions: Verin and gizmomelb

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
your ranting
Have you heard the phrase "the pot calling the kettle black"? I wouldn't call it "ranting," but if that's what we're going to call it, you've done just as much "ranting" as I have.

i’ll just block all atmosphere next patch problem solved right?
If we ignore that, like with the malware, there's no actual reason to block Atmosphere aside from your own emotional hang-ups and pettiness, then I support this decision.

If it were me, I'd either work to make sure Tinfoil was compatible with Atmosphere (it already is, without the malware), or I'd just ignore the existence of Atmosphere during Tinfoil development while saying Atmosphere isn't officially supported. If it worked with Atmosphere, great, but if it didn't, it wouldn't be my problem.

Checkpoint is a good example of what to do (and what not to do). Checkpoint blocked applet mode, and people (who were mostly confused) thought it was a bug spoke up. In response, Checkpoint unblocked applet mode but included a disclaimer about applet mode not being supported if it detected the use of applet mode. Doing something similar with Tinfoil is probably the best option for someone who doesn't want to dirty his hands with Atmosphere.

Forcing malware and/or intentionally sabotaging the use of Tinfoil on Atmosphere seem to come from a place of pettiness, particularly when neither solves any sort of problem. The patched version of Tinfoil works just fine with vanilla Atmosphere. Vanilla Tinfoil also worked just fine on vanilla Atmosphere before the malware was added.

I would say: Do it!
I always wonder why Atmosphere users whine about everything and trying to start a flame war....
I've never saw SX OS users doing that (:
blawar ftw
There's a difference between "whining" and acknowledging the use of malware that intentionally disrupts one's CFW-usage.
 
  • Like
Reactions: Ashura66

HtheB

Well-Known Member
Member
Joined
May 15, 2006
Messages
877
Trophies
1
Age
36
Location
Bize Her Yer Trabzon
Website
www.HtheB.com
XP
3,058
Country
Netherlands
There's a difference between "whining" and acknowledging the use of malware that intentionally disrupts one's CFW-usage.
There's a difference between "acknowledging the use of malware that intentionally disrupts one's CFW-usage" and admitting that the CFW itself being the problem, as it works perfectly fine on other CFW's ;)
 
  • Like
Reactions: gizmomelb

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
There's a difference between "acknowledging the use of malware that intentionally disrupts one's CFW-usage" and admitting that the CFW itself being the problem, as it works perfectly fine on other CFW's ;)
  1. It works fine on other custom firmwares because the malware doesn't target other custom firmwares.
  2. Without the malware, Tinfoil works fine with Atmosphere.
 

HtheB

Well-Known Member
Member
Joined
May 15, 2006
Messages
877
Trophies
1
Age
36
Location
Bize Her Yer Trabzon
Website
www.HtheB.com
XP
3,058
Country
Netherlands
  1. It works fine on other custom firmwares because the malware doesn't target other custom firmwares.
  2. Without the malware, Tinfoil works fine with Atmosphere.
1. If it was malware, it would target everything.
2. Just get over with it, don't use it if you think it's malware or change your CFW. No one stops you for using other CFW's.
3. No one stops you either for developing or forking your own version.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
1. If it was malware, it would target everything.
That's not how malware works.

2. Just get over with it, don't use it if you think it's malware or change your CFW. No one stops you for using other CFW's.
  1. It's fine to acknowledge the malware. I'm going to call out malware where I see it. "Sit down, shut up, and get over it" isn't much of a counterargument against the malware.
  2. I am using a patched version of Tinfoil without the malware on vanilla Atmosphere.
  3. If #2 weren't an option, I wouldn't use Tinfoil.
  4. Atmosphere is, in my opinion, the best CFW, and I'm unlikely to use anything else.

3. No one stops you either for developing or forking your own version.
I don't have to. A patched version already exists.
 
  • Like
Reactions: Ashura66

Engezerstorung

Well-Known Member
Member
Joined
Nov 9, 2011
Messages
208
Trophies
1
XP
1,733
Country
France
about incognito bricking :
so basically he can write his homebrew so it doesnt launch if things arent installed like he want them to be, to force user to install the full package or nothing, and with all the shit it does, but he cant write incognito to refuse to be used if not full write access is detected to avoid his own software he made to brick people? (because YES incognito is a program that launch into an environnement, if it use brick the environment, the software is at cause, not the environment; if a disease kill you its the disease fault, not the host one)

...i didn't say anything until know, but wow boi, how amazed i am to see how that guy manage to be an dick every.single.time

damn, if the applet mode change were such a problem for him he could have forket only this, or madea sysmodule, or i dont know what, to have the applet mode act like he want, without touching the title redirection... but nooo...

and "brickers still exist so bis protection doesnt protect against bricking", it protect against the bricks that happened before it was implemented, it protect against erasing those infos... its like saying "nintendo stability update arent update to block hack at all because hack still happen", if it wasnt there there would be even more way to brick people switch... for fck sake...
 
Last edited by Engezerstorung,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Sicklyboy @ Sicklyboy: *teleports behind you* "Nothing personnel, kiddo" +1