Hacking RELEASE Argon NX - Payload chainloader

  • Thread starter Thread starter FR0ZN
  • Start date Start date
  • Views Views 67,465
  • Replies Replies 139
  • Likes Likes 10
Is anyone else having problems with this?

Previously I’d been using 0.3 with no problems, but with this new release the selection screen background is just black and only three of my payloads appear, all on the right side of the screen.
Same here. I tried the newest version and get a blackscreen. But the Console is not in the rcm anymore after injecting.
 
Is anyone else having problems with this?

Previously I’d been using 0.3 with no problems, but with this new release the selection screen background is just black and only three of my payloads appear, all on the right side of the screen.
I didn't try it yet, but did you update your images for the new version? The background image now needs to be landscape (1280x720) as opposed to portrait (720x1280), and the logos want to be 280x280 rather than 200x200.
e: also there's a new resources.argon file to go in the sys directory.
 
Last edited by hippy dave,
I didn't try it yet, but did you update your images for the new version? The background image now needs to be landscape (1280x720) as opposed to portrait (720x1280), and the logos want to be 280x280 rather than 200x200.
e: also there's a new resources.argon file to go in the sys directory.

I just copied everything from the zip file, so I have to assume the background is the right size.
 
the problem with the new version 1.0 alpha is that the allowable data size for payloads has been exceeded. That's why a coldboot is not possible, but a warmboot is.

the current solution looks like this:
Copy the argon-nx payload from v1.0 alpha release into the argon folder and send the attached payload with your payload sender.
 

Attachments

Last edited by Muxi,
the problem with the new version 1.0 alpha is that the allowable data size for payloads has been exceeded. That's why a coldboot is not possible, but a warmboot is.

the current solution looks like this:
Copy the argon-nx payload from v1.0 alpha release into the argon folder and send the attached payload with your payload sender.
Huh, good spot. The joys of alpha software, hopefully will get an official fix soon.
 
  • Like
Reactions: Muxi
Is anyone else having problems with this?

Previously I’d been using 0.3 with no problems, but with this new release the selection screen background is just black and only three of my payloads appear, all on the right side of the screen.
Me, i have a black screen :(
 
If I only want this payload as an autoboot to have within RCMLoader, does the 1.0 release offer me anything better than the 0.3?
 
With SX OS, freez on Bootlogo Aragonnx :(
This is not the case for me. ArgonNX runs smoothly. The only thing that I think would be faulted is the bug in the Tools menu "Power of" instead of "Power off"
 
Last edited by Muxi,
This is not the case for me. ArgonNX runs smoothly. The only thing that I think would be faulted is the bug in the Tools menu "Power of" instead of "Power off"

Here you go, I fixed the typo for you. I didn't test, just fixed the spelling mistake and built it.
 

Attachments

  • Like
Reactions: chronoss
Does ArgonNX require an update for the Mariko hardware, or would this chainloader be applicable without a customization underneath?
 
anyone converter argonnx.bin 1.1 to current.uf2 used on R4S, I'm used argon 0.3 with R4S and would to update to 1.1 but no support from r4i-sdhc, I tried to flash with argon.bin 1.1 alpha (current.uf2) trinket m0 but it red light and not send payload, anyone help me
 

Site & Scene News

Popular threads in this forum