Switch was working with latest Atmosphere 1.3.2 and OFW. Today when I try to boot using TegraRcmSmash with fusee.bin and my dongle/jig it flashes the Atmosphere screen for about a half second then the screen goes blank. A few seconds later the Atmosphere logo screen flashes again, then goes black. Never boots back up. Any known fix? TegraRcmSmash (32 bit) provides the following:
No RCM device detected
RCM Device detected
Invoking TegraRcmSmash.exe with args : "C:\Program Files (x86)\TegraRcmGUI\favorites\fusee.bin"
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#7&2ee6241&0&1#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id C080031700000010C2A2406401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 109088, total size: 175304, total padded size: 176128)...
Smashing the stack!
Smashed the stack with a 0x001f byte SETUP request!
Payload successfully injected
RCM device disconnected
RCM Device detected
Invoking TegraRcmSmash.exe with args : "C:\Program Files (x86)\TegraRcmGUI\favorites\fusee.bin"
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#7&2ee6241&0&1#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id C080031700000010C2A2406401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 109088, total size: 175304, total padded size: 176128)...
Smashing the stack!
Smashed the stack with a 0x001f byte SETUP request!
Payload successfully injected
RCM device disconnected
RCM Device detected
Invoking TegraRcmSmash.exe with args : "C:\Program Files (x86)\TegraRcmGUI\favorites\fusee.bin"
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#7&2ee6241&0&1#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id C080031700000010C2A2406401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 109088, total size: 175304, total padded size: 176128)...
Smashing the stack!
Smashed the stack with a 0x001f byte SETUP request!
Payload successfully injected
RCM device disconnected
RCM Device detected
Invoking TegraRcmSmash.exe with args : "C:\Program Files (x86)\TegraRcmGUI\favorites\fusee.bin"
TegraRcmSmash (32bit) 1.2.1-3 by rajkosto
Opened USB device path \\?\usb#vid_0955&pid_7321#7&2ee6241&0&1#{aa0dbd45-3117-f331-5c49-76bf65225042}
RCM Device with id C080031700000010C2A2406401101062 initialized successfully!
Uploading payload (mezzo size: 92, user size: 109088, total size: 175304, total padded size: 176128)...
Smashing the stack!
Smashed the stack with a 0x001f byte SETUP request!
Payload successfully injected
RCM device disconnected
You can just use an android phone.Hello, I accidantaly destroyed my ns-atmosphere payload injector, is there one that is good enough with an included jig you would recommand?
If possible not from china/aliexpress, I don't really want to wait weeks/months for it to come.
I use an old android phone as an injector.Hello, I accidantaly destroyed my ns-atmosphere payload injector, is there one that is good enough with an included jig you would recommand?
If possible not from china/aliexpress, I don't really want to wait weeks/months for it to come.
Rekado for the win!I use an old android phone as an injector.
Hello, I accidantaly destroyed my ns-atmosphere payload injector, is there one that is good enough with an included jig you would recommand?
If possible not from china/aliexpress, I don't really want to wait weeks/months for it to come.
Under Atmoshopere directory there is no /contents directory.Have you added anything new sys modules?
Try this:
temporarily move/rename your /atmosphere/contents directory to /atmosphere/contents.bk and reboot.
I was able to get Atmosphere running again by injecting hekate and then that was able to boot into atmosphere. However now I get The microSD card data is corrupted. I thought for sure that when updated the OFW I chose fat32. Hekate disc info report fat32. However, it seems the card may be corrupt. It won't run games. Is there anything to try before I reformat the SD card?inject another payload, like hekate and enter on NYX (pressing VOL- while injecting) or tegraexplorer and let us to know how that go.
Then create it.Under Atmoshopere directory there is no /contents directory.
Been busy with work but tried this again and now it's worse. Before at least I was booting into the atmosphere but now it just shows a black screen with "A fatal error occurred when running Fusee. Incorrect fusee version! ...Press POWER to reboot."This is just to move the old deployments out of the way for both atmosphere and bootloader.
When you unzip the files at the top of your SDCard you will have new atmosphere and bootloader directories with nothing left over from the original deployment (but you have a .bk for backup if you want to roll back).
In the odd case you don’t have a new /atmosphere and /bootloader then we know there’s an issue with the transport method.
Make sense?
Been busy with work but tried this again and now it's worse. Before at least I was booting into the atmosphere but now it just shows a black screen with "A fatal error occurred when running Fusee. Incorrect fusee version! ...Press POWER to reboot."
I even tried deleting the Atmosphere folder and copying over everything again. Didn't help at all. What went wrong or what is preventing it from even booting past that incorrect fusee screen?!
Yes, same page you have in the screenshot here. Same atmosphere. Note: I am booting payloads using the SX OS dongle (on erista switch w original SX license from years ago)Did you download fusee.bin from the same place you downloaded Atmosphere?
You will need to place it in /bootloader/payloads/fusee.bin AGAIN (because we moved the /bootloader out of the way.)
View attachment 317228
Yes, same page you have in the screenshot here. Same atmosphere. Note: I am booting payloads using the SX OS dongle (on erista switch w original SX license from years ago)
Everything has been fine for years until this latest attempt at updating atmosphere. (I have updated atmos/OFW since converting to atmosphere before. Not sure why this time it all went south) :-(