Hacking Atmosphere-NX - Custom Firmware in development by SciresM

minooch_e

Active Member
Newcomer
Joined
Apr 28, 2017
Messages
35
Trophies
0
XP
1,003
Country
United States
I always updated using choidujournx. I am not an expert, but I think that is due to the nand writting permission that is more protected since several updates. Maybe something is wrong with my settings since the latest update

If you're launching HB loader via a NSP, use applet mode, choi works better
 
  • Like
Reactions: Xyphoseos
D

Deleted User

Guest
SciresM posted details on the boot encryption keys of the "Mariko" Nintendo Switch Motherboards.
Seems like hackers have been able to access early stages of the console’s boot process, and might be able to port the existing selection of hacking tools to the console.

 
  • Like
Reactions: TheCasualties

tivu100

Well-Known Member
Member
Joined
Jun 6, 2015
Messages
2,260
Trophies
0
Age
34
XP
1,136
Country
United States

Worldblender

Well-Known Member
Member
Joined
May 27, 2019
Messages
326
Trophies
0
Age
27
XP
2,244
Country
United States
Explain to me like to an 10 year old. What is potential of this?
There's a possibility that the retrieved encryption keys can be used as part of the hacking process, probably during RCM mode, so that it can be tricked into accepting any payloads, not just official signed ones.
 
  • Like
Reactions: tivu100

Y0sh1

Well-Known Member
Member
Joined
Dec 31, 2017
Messages
137
Trophies
0
XP
1,313
Country
Ireland
There's a possibility that the retrieved encryption keys can be used as part of the hacking process, probably during RCM mode, so that it can be tricked into accepting any payloads, not just official signed ones.

I'd love to believe this but I don't think the hardware limitation can be bypassed that easily
 
  • Like
Reactions: tivu100

alba93

Well-Known Member
Newcomer
Joined
Feb 2, 2019
Messages
77
Trophies
0
Age
45
XP
885
Country
France
good new

exosphere2: completely rewrite the secure monitor
This re-writes exosphere (the very first atmosphere component!) in C++.
The re-write aims to have significantly better code-style, and to result in smaller/faster binaries.
It also lays the groundwork for mariko support going forwards.
This pull request is technically incomplete -- backwards compatibility for older firmwares will be added in the next day or two before merge.
PR is being made now to allow for some time to review, if anyone is so inclined.
I am very, very personally pleased to finally have an idiomatic secure monitor that doesn't have all of the original exosphere's design mistakes.
We're also doing significantly better with regards to our space budget -- exosphere1 has less than 1 KB of space left, but we have plenty of breathing room in exosphere2 despite implementing more functionality.
 
Last edited by alba93,

subcon959

@!#?@!
Member
Joined
Dec 24, 2008
Messages
5,845
Trophies
4
XP
10,109
Country
United Kingdom
Happy June 15th?

:P

Some interesting notes from upcoming 0.13..
Finally, the groundwork for mariko support has been laid -- there are only a few minor changes needed for the new secure monitor implementation to work on both erista and mariko hardware.
Please note: exosphère is only one of many components, and many more need changes to support running on mariko hardware.
Software-side support for executing on mariko hardware is expected some time during Summer 2020, though it should also be noted that this is not a hard deadline.
Please note: The new exosphère binary is not abi-compatible with the old one. Users who boot using hekate should wait for it to update before running 0.13.0 (or boot fusee-primary via hekate).
atmosphère's api for target firmware was changed. All minor/micro system versions are now recognized, instead of only major versions.
This was required in order to support firmware version 5.1.0, which made breaking changes to certain IPC APIs that caused atmosphère 0.12.0 to abort.
Please note: this is (unavoidably) a breaking change. System modules using atmosphere-libs will need to update to understand what firmware version they are running.
emummc was updated to include the new changes.
emummc now uses an updated/improved/faster SDMMC driver.
File-based emummc is now almost as fast as raw partition-based emummc.
 
Last edited by subcon959,

lordelan

Well-Known Member
Member
Joined
Jan 4, 2015
Messages
5,792
Trophies
1
Age
44
XP
6,550
Country
Germany
Edit:
Figured it out. Should not only remove the ; but also the white space before the lines I want to activate.


Hi guys,
I've got a strange bug when applying the system_settings.ini
Currently I'm not using one, in other words, there is no system_settings.ini in sd:\atmosphere\config\ which is fine for a vanilla Atmosphère setup.
However I wanted to use EdiZon and cheats and therefore copied the system_settings.ini from sd:\atmosphere\config_templates\ to sd:\atmosphere\config\ and removed the ; in front of the two lines (enable cheats by default and save cheat toggles). Also I adjusted the values to 0x0 and 0x1 to disable cheats by default and save the toggles with EdiZon.

My file now looks like this:
Code:
; Disable uploading error reports to Nintendo
[eupld]
; upload_enabled = u8!0x0
; Control whether RO should ease its validation of NROs.
; (note: this is normally not necessary, and ips patches can be used.)
[ro]
; ease_nro_restriction = u8!0x0
; Atmosphere custom settings
[atmosphere]
; Reboot from fatal automatically after some number of milliseconds.
; If field is not present or 0, fatal will wait indefinitely for user input.
; fatal_auto_reboot_interval = u64!0x0
; Make the power menu's "reboot" button reboot to payload.
; Set to "normal" for normal reboot, "rcm" for rcm reboot.
; power_menu_reboot_function = str!payload
; Controls whether dmnt cheats should be toggled on or off by
; default. 1 = toggled on by default, 0 = toggled off by default.
 dmnt_cheats_enabled_by_default = u8!0x0
; Controls whether dmnt should always save cheat toggle state
; for restoration on new game launch. 1 = always save toggles,
; 0 = only save toggles if toggle file exists.
 dmnt_always_save_cheat_toggles = u8!0x1
; Enable writing to BIS partitions for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_bis_write = u8!0x0
; Enable reading the CAL0 partition for HBL.
; This is probably undesirable for normal usage.
; enable_hbl_cal_read = u8!0x0
; Controls whether fs.mitm should redirect save files
; to directories on the sd card.
; 0 = Do not redirect, 1 = Redirect.
; NOTE: EXPERIMENTAL
; If you do not know what you are doing, do not touch this yet.
; fsmitm_redirect_saves_to_sd = u8!0x0
; Controls whether to enable the deprecated hid mitm
; to fix compatibility with old homebrew.
; 0 = Do not enable, 1 = Enable.
; Please note this setting may be removed in a
; future release of Atmosphere.
; enable_deprecated_hid_mitm = u8!0x0
[hbloader]
; Controls the size of the homebrew heap when running as applet.
; If set to zero, all available applet memory is used as heap.
; The default is zero.
; applet_heap_size = u64!0x0
; Controls the amount of memory to reserve when running as applet
; for usage by other applets. This setting has no effect if
; applet_heap_size is non-zero. The default is 0x8600000.
; applet_heap_reservation_size = u64!0x8600000

However, if I reboot with this file in the config folder, I'm stuck at the Nintendo Switch logo forever.
If I delete it, I can boot Atmosphère just fine again. What's wrong with the file?
 
Last edited by lordelan,

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,338
Country
United States
A quick reminder that when Atmosphere 0.13.0 is released, current signature patches for 10.0.x will probably not be compatible (I haven't checked if loader was updated). If you care about signature patches, please wait for them to be updated.

Edit: Patches need to be updated for homebrew forwarders. Game backups of any kind work fine.
 
Last edited by Lacius,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Nut on the hill