I believe i am using version 1.8 of usb loader gx but here is where i got it from Īnd i have it in the apps folder on my sd card and the usb is in usb port 0 the one that recognizes the usb, i also have tried reinstalling the usb loader too, i am using a usb flash drive and a sd card both of which have 32 gb's of space im not sure whats the cluster size but both are both formatted to fat32, i got the brawl iso from vimms lair and then i got wii back up manager 32 and put in a folder called wbfs in drive 1 and then had it go into another wbfs folder on my sd card where brawl became a wbfs file but then i moved the folder with brawl in it to my usb flash drive, i used base 56 when i reinstalled iso 249 and now here is my sys check report. To know what you currently have in all your "slots", you can follow the syscheck guide linked in my signature and post the result here. yeah, depends what you put in that folder, not its name. "I installed a file in a folder named 249 and it doesn't work". Saying you (re)installed a slot is a useless information if you don't tell what you installed in that slot. Like you can see, it can be a lot of possible cause, and you didn't tell us anything except you tried to reinstall d2x (which, to me, is not causing any dsi error)Īlso, to be sure, which "base IOS" did you put in slot 249 ? Provide almost ALL you can think about if you want to be helped, nobody can predict or use a crystal ball. How did you proceed ? you MUST use wii backup manager THIS WAY. Using a tool ? which tool ? DO NOT USE WBFS MANAGER ! Manually with your file explorer ? which file name, which folder? How did you "put" the game on the device ? Next comes the partition format : FAT32, NTFS, exFAT, WBFS ?Īnd its size and cluster size if you know. Then, which device are you using ? USB Flash drive, or USB External HDD ? Where did you install the loader ? SD or USB ? which USB Port ? top/bottom?
no need to reinstall the cIOS.įirst, tell us which version of USBLoaderGX you are using. If you get dsi errors, it's probably a bug in the loader itself, not the cIOS.
0 kommentar(er)
