Error after migrating emuMMC to a new SD card

neko_koneko

Well-Known Member
OP
Member
Joined
Mar 16, 2011
Messages
199
Trophies
1
XP
900
Country
United States
Hello,

I recently finished this tutorial on how to migrate your emummc to a new card.
https://rentry.org/EmuNANDNewSDcard

I needed more storage, and made sure that I partitioned the new SD card correctly and everything.

When I try to boot into Atmosphere in the Hekate 6.0.7 home screen under "Launch" and Atmosphere, and another booting method, under "payloads" fusee.bin, I get the error message, " A fatal error occurred when running Fusee. Failed to find INI1! " I have tried a few things, including editting my hekate_ipl.ini file. (I attached a before and after picture of my editted file). I was wondering how, or if I need to, regenerate a new BOOT0 and BOOT1? I am very lost at this point. I've considered partitioning the card again and moving over the folders from my backup on my PC to the new sd card as mentioned in the tutorial.

Any help would be greatly appreciated!
 

Attachments

  • Sb9NzCl.jpeg
    Sb9NzCl.jpeg
    971.9 KB · Views: 8
  • 20240117_170030.jpg
    20240117_170030.jpg
    1.3 MB · Views: 16
  • 20240117_092605.jpg
    20240117_092605.jpg
    336.5 KB · Views: 14

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • K3Nv2 @ K3Nv2:
    Luckily I get to whore myself to insurance which billing departments have no idea on how to handle
  • K3Nv2 @ K3Nv2:
    What he's covered? Make his life stressful anyway
  • Sicklyboy @ Sicklyboy:
    I love how insurance companies can deny procedures because they deem it not medically necessary despite the procedure being ordered by a doctor
  • K3Nv2 @ K3Nv2:
    Going with that right now with a dental claim morons put the wrong company name and rejected claims been on hold an hour for the claims department
  • K3Nv2 @ K3Nv2:
    @Sicklyboy, BTW is it better to go usb or bt for these mini Pcs figure you may know since you play with rack systems so much
  • Sicklyboy @ Sicklyboy:
    Counting my blessings that my insurance hasn't caused me really any headache (yet, at least) despite the fact that I've been getting way more appointments and what not recently due
  • Sicklyboy @ Sicklyboy:
    @K3Nv2, what do you mean, what are you trying to do?
  • K3Nv2 @ K3Nv2:
    Just looking at a built in mouse pad keyboard combo
  • K3Nv2 @ K3Nv2:
    I loose the dongle constantly but they may have better connection with usb frequency
  • Sicklyboy @ Sicklyboy:
    Imo Bluetooth is always a option of last resort for me
  • Sicklyboy @ Sicklyboy:
    Except for phones because it tends to be pretty reliable there
  • K3Nv2 @ K3Nv2:
    I got a bad habit of taking out usb transmitter and loosing it because they can't you know print names on the damn things
  • Sicklyboy @ Sicklyboy:
    But any desktop OS, I've never had anything but frustration trying to get Bluetooth devices to work reliably and stable. It might pair and connect once, and then next time I go to use it I have to delete and re-pair it again
  • K3Nv2 @ K3Nv2:
    5.3 has been so good I think 6 is really going to make it stable
  • K3Nv2 @ K3Nv2:
    I remember how shit 3 was
  • Sicklyboy @ Sicklyboy:
    Ptouch labeler aren't terribly expensive, label shit yourself fam. This is the one I own and there are cheaper ones too https://www.amazon.com/Brother-P-Touch-PTH110BP-Portable-included/dp/B09QXYND6S
  • Sicklyboy @ Sicklyboy:
    Solves part of the problem, mixing up which dongle is which. Then you just have to not lose them lol
  • K3Nv2 @ K3Nv2:
    Double D would be proud
    +1
  • Sicklyboy @ Sicklyboy:
    Even my Xbox One controller I have it paired to my desktop over Bluetooth, it USUALLY works but sometimes it refuses to connect and I have to delete and re-pair it. Maddening
  • K3Nv2 @ K3Nv2:
    Gigabytes built in mobo bt/wifi pairs pretty decent
  • Sicklyboy @ Sicklyboy:
    That's what I'm using :(
  • K3Nv2 @ K3Nv2:
    Ran a driver update in device manager?
  • Sicklyboy @ Sicklyboy:
    Not recently but I think it's less a driver issue and more just Windows having a garbage Bluetooth stack
  • K3Nv2 @ K3Nv2:
    Could be I was having issues when I first upgraded it and didn't realiser gigabyte has specific driver revisions which is stupid
  • K3Nv2 @ K3Nv2:
    Which is married to the boards revision
    K3Nv2 @ K3Nv2: Which is married to the boards revision