Hacking Question Exosphere doesnt boot with CTCaer's Hekate 3.0

[Yamathedestroyer]

Well yes, tried a exosphere.bin from sdfiles and and a version i compiled on my own

EDIT:
Heres my Boot configuration:
[Exosphere]
secmon=modules/atmosphere/exosphere.bin
kip1=modules/atmosphere/loader.kip
kip1=modules/atmosphere/sm.kip
kip1=modules/atmosphere/fs_mitm.kip
logopath=modules/atmosphere/atmosphere.bmp
atmosphere=1

 

[Deleted User]

Well yes, tried a exosphere.bin from sdfiles and and a version i compiled on my own

EDIT:
Heres my Boot configuration:
[Exosphere]
secmon=modules/atmosphere/exosphere.bin
kip1=modules/atmosphere/loader.kip
kip1=modules/atmosphere/sm.kip
kip1=modules/atmosphere/fs_mitm.kip
logopath=modules/atmosphere/atmosphere.bmp
atmosphere=1

it works just fine... for some reason though I have to unplug the switch first in order it to boot, or else it just hangs... also rip sleep mode... oh, not rip, for some reason just tapping the power button shuts the switch entirely, well things are going to break so lol.


edit: I stand corrected, it reboots into rcm mode, the reason I say that is because when it reboots, it causes the hang...

 

[nero99]

And this is why you don’t use a unfinished cfw. SX os is free for homebrew use if that’s all you want to use until atmosphere is actually finished

 

[Deleted User]

And this is why you don’t use a unfinished cfw. SX os is free for homebrew use if that’s all you want to use until atmosphere is actually finished

yes as tx didn't steal any code from atmosphere at all, it's not like we found out a week ago that they stole code, and ignored the gpl license, nope not at all. No sarcasm here. So if you really think about it, sx os is complete in piracy aspects, but everything else is based on incomplete code from another work. So, therefore, sx os is also incomplete.

 

[Yamathedestroyer]

SX OS is stolen shit

 

[rad.i.kal]

And SX OS can brick your console if you mess with stuff.

 

[stephrk398]

And SX OS can brick your console if you mess with stuff.

You've been fear mongered, congrats. The likelihood of an end-user bricking their SX OS Switch is extremely low. That, and there have been no reported bricks.

 

[Deleted User]

You've been fear mongered, congrats. The likelihood of an end-user bricking their SX OS Switch is extremely low. That, and there have been no reported bricks.

Then again, there shouldn't be brick code, period, the end.

 

[rad.i.kal]

You've been fear mongered, congrats. The likelihood of an end-user bricking their SX OS Switch is extremely low. That, and there have been no reported bricks.

NOT fear mongered at all

Then again, there shouldn't be brick code, period, the end.

I agree with this statement.

 

[IPLbug]

I really don't see the point of all this tx stole code bla bla bla if it's open source you can modify and use it as you see fit.
Regardless of that compiling a unfinished build of CFW is pointless as you run the chance of wrecking the console in the case of a error or hook not functioning properly. I see your bitter with TX but the guy that gave you the option to use the free version was just trying to help you out no need to derail this thread with piracy vs no piracy jibber jatter.

The simple answer to your problem is don't use unfinished code simple as that

 

[Deleted User]

I really don't see the point of all this tx stole code bla bla bla if it's open source you can modify and use it as you see fit.

No, false, the thing is, just because it's open does not mean you can just take it. Because the code they stole, was under gpl, which essentially states that they MUST credit the source, and if they made any changes, they have to make it open source. And guess what? they did neither, they tired claiming sx os was entirely their own.

Regardless of that compiling a unfinished build of CFW is pointless as you run the chance of wrecking the console in the case of a error or hook not functioning properly.

Yes because a error that modifies memory is WAAAAAY more likely to brick than intentionally placed brick code, that is checked at every point in the bootloader. And writes to the boot partition of the switch, and locks the nand when and if triggered. Which the boot partitions have key blobs related to that system. So when it bricks it, you better pray to god you have a backup. Because getting one from someone else, isn't going to do you any favors.

The simple answer to your problem is don't use unfinished code simple as that

Wow... hang on let me frame this as a question. If some team decides to steal incomplete code from another developer, and add slight modifications, and then they claim their project is complete, is it actually complete? According to you we shouldn't use tx or Atmosphere. Since if you really think about it, TX is just a incomplete atmosphere with a couple of patches. (And brick code)

On another side note, cfw always has a small chance of bricking a console. But unlike most custom firmware, tx has brick code, and flaws that could accidentally trigger it. And even if a brick happened with atmosphere, it would be far less severe than what tx's brick code. So stop defending it, and do research.

 

[IPLbug]

No, false, the thing is, just because it's open does not mean you can just take it. Because the code they stole, was under gpl, which essentially states that they MUST credit the source, and if they made any changes, they have to make it open source. And guess what? they did neither, they tired claiming sx os was entirely their own.


Yes because a error that modifies memory is WAAAAAY more likely to brick than intentionally placed brick code, that is checked at every point in the bootloader. And writes to the boot partition of the switch, and locks the nand when and if triggered. Which the boot partitions have key blobs related to that system. So when it bricks it, you better pray to god you have a backup. Because getting one from someone else, isn't going to do you any favors.



Wow... hang on let me frame this as a question. If some team decides to steal incomplete code from another developer, and add slight modifications, and then they claim their project is complete, is it actually complete? According to you we shouldn't use tx or Atmosphere. Since if you really think about it, TX is just a incomplete atmosphere with a couple of patches. (And brick code)

On another side note, cfw always has a small chance of bricking a console. But unlike most custom firmware, tx has brick code, and flaws that could accidentally trigger it. And even if a brick happened with atmosphere, it would be far less severe than what tx's brick code. So stop defending it, and do research.

You do realize that using a segment of open source code doesn't breach any licenses at all if that where the case every time a software was made they would have to point to Microsoft or the platform maker for example. The only point you can make is that it's pretty shitty of tx not giving the scene devs a shoutout but that's as far as your point is valid. If it was such a big deal as your trying to make it seems I think the first ones to be outraged and fighting would be the devs to the grade there tx product would be off the market by now

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

You do realize that using a segment of open source code doesn't breach any licenses at all if that where the case every time a software was made they would have to point to Microsoft or the platform maker for example. The only point you can make is that it's pretty shitty of tx not giving the scene devs a shoutout but that's as far as your point is valid. If it was such a big deal as your trying to make it seems I think the first ones to be outraged and fighting would be the devs to the grade there tx product would be off the market by now

To further educate you it been well known that the brickcode your referring to is activated by debugging there os or possible hombrew coding issues that could conflict with there coding style.

There always a chance to brick any console when running any unsigned code in every aspect of the spectrum from tvs to computers the threat is there I couldn't give 2 shit about tx at all but deciding to go ape shit on a user trying to help you out over your outrage over something you dint even code or even add to seem rather stupid as hell he only said that if you wanted to run hombre you could use there free os sense the main point of your thread was you could boot into CFW cause you compiled a unfinished build

 

[Samus20XX]

You do realize that using a segment of open source code doesn't breach any licenses at all if

except it violates GPLv2 soooooooooooooooooooooo

 

[Deleted User]

You do realize that using a segment of open source code doesn't breach any licenses at all if that where the case every time a software was made they would have to point to Microsoft or the platform maker for example. The only point you can make is that it's pretty shitty of tx not giving the scene devs a shoutout but that's as far as your point is valid. If it was such a big deal as your trying to make it seems I think the first ones to be outraged and fighting would be the devs to the grade there tx product would be off the market by now

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



To further educate you it been well known that the brickcode your referring to is activated by debugging there os or possible hombrew coding issues that could conflict with there coding style.

There always a chance to brick any console when running any unsigned code in every aspect of the spectrum from tvs to computers the threat is there I couldn't give 2 shit about tx at all but deciding to go ape shit on a user trying to help you out over your outrage over something you dint even code or even add to seem rather stupid as hell he only said that if you wanted to run hombre you could use there free os sense the main point of your thread was you could boot into CFW cause you compiled a unfinished build

https://twitter.com/hexkyz/status/1012363017957380096
first off easier to trigger than expected, implying users could run into it. And what is worse? code that is unfinished, or code that is unfinished with brick code. Because let's face it, it's based off atmosphere, which is incomplete, again, thefore, SX os is incomplete. Even if they said it's finished.
https://twitter.com/hexkyz/status/1012362983572492291
https://twitter.com/hexkyz/status/1012363013389774848
more than just snippets, as it's using atmosphere's loader code.

 

[IPLbug]

except it violates GPLv2 soooooooooooooooooooooo

GPLv2 applies in the case of the entire code being used or modified. It doesn't apply to just segments of it being used in anothers code string or if compiled with another persons code. It's still shitty for some one to use part of your code without reference to you in the readme.txt atlest

https://tldrlegal.com/license/gnu-general-public-license-v2

 

[hippy dave]

Another thread ruined, great work guys.

 

[IPLbug]

I

Another thread ruined, great work guys.

I tried to stop it

 

[Proto-Propski]

I like watching a thread delude into complete chaos over loosely related topics, it's why I buy Popcorn, after-all who needs to watch a Movie anymore, am I right.


That aside OP, according to the Github I don't think exosphere is really even complete yet, unless there has been improvements since Mar 27th that hasn't been commited in direct relation to that Sub-Projects 2/3 ongoing goals, on their Atmosphere-NX Github.

 

[GizmoTheGreen]

https://twitter.com/hexkyz/status/1012363017957380096
first off easier to trigger than expected, implying users could run into it. And what is worse? code that is unfinished, or code that is unfinished with brick code. Because let's face it, it's based off atmosphere, which is incomplete, again, thefore, SX os is incomplete. Even if they said it's finished.
https://twitter.com/hexkyz/status/1012362983572492291
https://twitter.com/hexkyz/status/1012363013389774848
more than just snippets, as it's using atmosphere's loader code.

TX OS is basically a very old buggy build of atmosphere with a TX skin on it. it's 45% atmosphere + hbloader, 5% their XCI "iso mount" style piracy, and 50% 27 layers of encryption and decryption + SEVERAL "anti crack" checks that intentionally brick your device.

and people pay for this. I'm not even mad. enjoy your slim chance of brick on every payload boot and heavily crippled system cause Nintendo actually did good in preventing piracy this time around and TX's method is stupid in general because of it.

 

[DKB]

TX OS is basically a very old buggy build of atmosphere with a TX skin on it. it's 45% atmosphere + hbloader, 5% their XCI "iso mount" style piracy, and 50% 27 layers of encryption and decryption + SEVERAL "anti crack" checks that intentionally brick your device.

and people pay for this. I'm not even mad. enjoy your slim chance of brick on every payload boot and heavily crippled system cause Nintendo actually did good in preventing piracy this time around and TX's method is stupid in general because of it.

fearmongered lol