Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,701,448
  • Replies Replies 9,233
  • Likes Likes 92
I always thought that the Subrepo updates were related to Armosphere-libs

https://github.com/Atmosphere-NX/Atmosphere-libs/tree/82f1553c4c7e68364f7e630b1c68f2aee8681dee
you thought wrong basically, see my master to master comparison from my fork, two commits doing nothing except subrepo update, which is in the direction of atmosphere-libs.

those libraries are inside of /Atmosphere-NX/Atmosphere/ already.

changed by commit 020ed307b1c404eeb5d16949bc3ecd3b2997fa54


https://github.com/borntohonk/Atmosphere/commit/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

diff.jpg
 
  • Like
Reactions: josete2k
you thought wrong basically, see my master to master comparison from my fork, two commits doing nothing except subrepo update, which is in the direction of atmosphere-libs.

those libraries are inside of /Atmosphere-NX/Atmosphere/ already.

changed by commit 020ed307b1c404eeb5d16949bc3ecd3b2997fa54


https://github.com/borntohonk/Atmosphere/commit/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

View attachment 566914
Yes, but you can chack this

https://github.com/ndeadly/MissionControl/tree/master/lib

And see that point to Armosphere-libs, not lib on Atmosphere-NX
 
Yes, but you can chack this

https://github.com/ndeadly/MissionControl/tree/master/lib

And see that point to Armosphere-libs, not lib on Atmosphere-NX
I think you are missing the point of explanation, these commits do nothing for https://github.com/Atmosphere-NX/Atmosphere

already changed by https://github.com/Atmosphere-NX/Atmosphere/commit/020ed307b1c404eeb5d16949bc3ecd3b2997fa54

and as image show ( i know some people understand better with image, but seem not case this time, unfortunate )
 
  • Like
Reactions: josete2k
Posting the same on multiple threads is considerate spam. Read three guide about upgrade Atmosphère
Sorry, I'll delete it. I managed to solve it myself...
Post automatically merged:

Is there nowhere to delete it?
 
  • Like
Reactions: impeeza
I'm getting a black screen when booting emummc after updating to the latest atmosphere, hekate and the sigpatches bth provided in the sigpatches thread. Haven't even updated the official firmware yet.

EDIT: Even going back to the older version of Atmosphere I had before updating doesn't work. Black screen after the Atmosphere logo. Fuck...
 
Last edited by .Darky,
Same black screen, V1 unpatched after updating atmosphere and firmware to 22.1.0. Can't boot hekate.
Hekate doesn't care about the firmware - it can boot with broken firmware. Did you have autoRCM turned on? Hold power button for 10-15 seconds to fully turn off the switch. Then try again. If that still fails you can try booting into recovery mode - just google fu for information on how to do this, there's loads of videos on youtube.
 
Hekate doesn't care about the firmware - it can boot with broken firmware. Did you have autoRCM turned on? Hold power button for 10-15 seconds to fully turn off the switch. Then try again. If that still fails you can try booting into recovery mode - just google fu for information on how to do this, there's loads of videos on youtube.
I can get into Maintenance Mode just fine and my OFW is already up to date. I don't think I want to initialize the console though.
 
I can get into Maintenance Mode just fine and my OFW is already up to date. I don't think I want to initialize the console though.
Well if you can boot into OFW your switch is working, can you see how much free memory the sd card has in OFW. If you can't boot into hekate did you check your sd card is not corrupted and not reading the contents of the bootloader folder, maybe you should redownload hekate and replace the bootloader folder, or try booting using fusee.bin payload instead.
 
Same black screen, V1 unpatched after updating atmosphere and firmware to 22.1.0. Can't boot hekate.
Well, hekate boots fine when turning on the system and I can go into OFW (updated last night), but get the black screen when trying emummc. Also tried fusee.bin and got the same black screen. Would really appreciate some help.
 
Well, hekate boots fine when turning on the system and I can go into OFW (updated last night), but get the black screen when trying emummc. Also tried fusee.bin and got the same black screen. Would really appreciate some help.
Did you try renaming your atmosphere folder to atmosphere.bak and reinstalling a new clean version of atmosphere?
 
Well if you can boot into OFW your switch is working, can you see how much free memory the sd card has in OFW. If you can't boot into hekate did you check your sd card is not corrupted and not reading the contents of the bootloader folder, maybe you should redownload hekate and replace the bootloader folder, or try booting using fusee.bin payload instead.
I have space left on the SD, and it does boot to OFW, yes it's technically 'working'. Hekate Github says it supports 22.1.0, but they must have edited it, as that just came out. I redownloaded the package and tried inserting the hekate bin with tegrarcm and still the black screen. At least I'm not the only one with this issue.
 
Did you try renaming your atmosphere folder to atmosphere.bak and reinstalling a new clean version of atmosphere?
I deleted both the atmosphere and bootloader folder I was using and did a fresh install (added back my contents folder I had backed up) and got the same black screen. I then deleted the contents folder entirely and still didn't work.
 

Site & Scene News

Popular threads in this forum