Recent content by Gingerz

  1. G

    Hacking Question Panic occured while running Atmosphere. Title ID : 0100000000000002b

    Hey there, I've been having the same issue. I installed NxNandManager, used Hekate to link to eMMc RAW GPP, but the button to mount SYSTEM was greyed out. It did say Keyset Needed at the top. Any ideas for a relative noob?
  2. G

    Hacking R4s Dongle issue

    I worked it out! My hekate ini had been edited in Mac, which totally buggered it up. Fixed it in PC and the hekate payload renamed as palyload.bin works just fine!
  3. G

    Hacking R4s Dongle issue

    Was about to send the R4S dongle back as I can't install argon on it (file is too big). When I make the argon package smaller by removing the large bmp image it disconnects and all the new files are gone. I tried what you said re: moving the three zipped files and the dongle disconnects when I...
  4. G

    Hacking R4s Dongle issue

    I did this (Switch is in Auto RCM) but I'm just getting the black ArgonNX v0.3 screen with the three options at the bottom for Screenshot, Power Off and Reboot RCM
  5. G

    Hacking [HELP] AppToUSB 'Cannot Start the Application' ERROR

    I've been trying to do the same, but cannot seem to delete that hidden partition... HELP!
  6. G

    Hacking Problem using app2USB : "The defined MOUNT_POINT is incorrect"

    I was sincerely hoping that it was something as simple as the USB port, but alas it's not. Does Hen 2.1.1 allow you to use fake PKG files? And how would I do that? Please excuse my ignorance here.
  7. G

    Hacking Problem using app2USB : "The defined MOUNT_POINT is incorrect"

    Just to clarify, I wanted to use the HDD to run fake PKG files I had downloaded, and had my INI file set up accordingly.
  8. G

    Hacking Problem using app2USB : "The defined MOUNT_POINT is incorrect"

    I formatted a 4TB usb drive on Mac but when running app2USB I keep getting this error: "The defined MOUNT_POINT is incorrect. MOUNT_POINT=0 is defined but the drive is mounted to USB1" I now get the same error when formatting the same drive on my PC. Any solutions?