Hacking cIOSX rev21d2x: Yet Another Hot Fix!!!!

davebaol · Mar 30, 2011

@lenny_kano
That's exactly what I wanted to hear.

Thanks for the feedback

kukupo · Mar 30, 2011

davebaol said:
freestile said:

Good work on everything guys. Thanks for all the updates.
Do I have to change rev21004 to rev21 in showmiiwads? It was giving me the ret error cant find titles
or one of the sort, so I went back into showmiiwads and changed 21004 to 21 and now its working fine.
Just thought I'd ask. Wasnt sure if thats how it was. Seems like config usb can read 21004 though.
Wasn't to sure if mighty channels could read it or not. I'm using mighty channels beta 6
with cIOSX246[56] d2x v4beta1.

Click to expand...

Yes, you're right.
Migthy Channels beta6 doesn't recognize cios d2x with version number 21xxx.
As XFlak said you can use the option "Advanced Custom Downloads" in ModMii to change the version number to 21.

Everything on my 2TB works now as it did on my previous HDD (500gb one)
Thank you for all the help and suggestions.

actar · Mar 30, 2011

davebaol said:
Download d2x v4beta1
....cut....

Error downloading file. Retrying...

I'll try tomorrow

davebaol · Mar 30, 2011

@actar
Parliamo in italiano che ce la sbrighiamo prima.
Che problema hai? Non l'ho mica capito.

XFlak · Mar 30, 2011

davebaol said:
@actar
Parliamo in italiano che ce la sbrighiamo prima.
Che problema hai? Non l'ho mica capito.

I think he means he can't download the beta from mediafire. I'm also having issues downloading the latest JoyFlow beta from mediafire. I suspect the issue will resolve itself once mediafire gets its act together.

PS. The mods will be all over you if you post in another language without a translation
QUOTE(davebaol | Google Translate @ Mar 30 2011, 09:08 PM) @actar
We speak in Italian and hurry there the first.
What's your problem? I did not understand mica.

edit: seconds after posting this, I was finally able to download the JoyFlow beta from mediafire, so the issue may be fixed now

davebaol · Mar 30, 2011

Mirror: d2x v4beta1

PS:
That google translation is hilarious.

Kryptical · Mar 31, 2011

davebaol said:
Mirror: d2x v4beta1

PS:
That google translation is hilarious.

LOL it is XD.

Anyways, it's working fine with my 1TB HDD.

actar · Mar 31, 2011

davebaol said:
Mirror: d2x v4beta1

Now it's ok. =)

dhwz · Mar 31, 2011

Thx davebaol great work, NAND Emulation is now working again with my 1,5TB Seagate Expansion Portable.

Also Mighty Channels rev11 beta 6 is working as it should be, it recognizes cIOS 249 rev21004 without any problem.

But I've still another problem but maybe this isn't cIOS related, maybe its just a problem of the WAD-Manager.
If I try to install a WAD file with WAD-Manager 1.7 i can't mount the Harddisk, it doesn't matter if I select USB or USB2.0 Mass Storage.
I always get Err -1 or Err -2.

XFlak · Mar 31, 2011

try using yawmm or mmm instead of wad manager 1.7, works for me (also make sure a "WAD" folder is saved on the USB\SD otherwise it wont work). Or u can always just load IOS236 instead using w/e wad manager u want (obviously u gotta make sure u have IOS236 installed first).

davebaol · Mar 31, 2011

dhwz said:
Thx davebaol great work, NAND Emulation is now working again with my 1,5TB Seagate Expansion Portable.

Glad to hear it.

dhwz said:

Also Mighty Channels rev11 beta 6 is working as it should be, it recognizes cIOS 249 rev21004 without any problem.
Yeha but it works just like with rev17 meaning that full mode is disabled.
So nand emulation is actually reading/writing something in your real nand.

QUOTE(dhwz @ Mar 31 2011, 06:55 PM)

Click to expand...

But I've still another problem but maybe this isn't cIOS related, maybe its just a problem of the WAD-Manager.
If I try to install a WAD file with WAD-Manager 1.7 i can't mount the Harddisk, it doesn't matter if I select USB or USB2.0 Mass Storage.
I always get Err -1 or Err -2.

I believe the issue is inside wadmanager's code.

threeend · Mar 31, 2011

davebaol -

Having a problem with multiple games freezing up within 20 minutes running cIOSX rev21d2x4 beta 1. Had issues with many other cIOSs as well. Using 58 as a base because it is the only base that can see USB hard drive.

Full thread here. Any help appreciated.

davebaol · Mar 31, 2011

Usually it happens for not fully supported drives.
Try using another hdd or pen drive.

dhwz · Mar 31, 2011

davebaol said:
dhwz said:

Also Mighty Channels rev11 beta 6 is working as it should be, it recognizes cIOS 249 rev21004 without any problem.

Click to expand...

Yeha but it works just like with rev17 meaning that full mode is disabled.
So nand emulation is actually reading/writing something in your real nand.

At least the last channel that I've installed today wrote its saves to the emulated NAND and not to the real NAND.
So what do you mean with something is written to the real NAND?

davebaol · Mar 31, 2011

Well, it's not easy to explain.

Anyways, in full mode everything but /dev is accessed on the emulated nand in FAT.
Notice that inside the /dev path there are resources representing devices, but these are not actually present in the real nand; they're "virtual" paths.

On the other hand, in non full mode only some paths are actually accessed in FAT, namely those starting with:
/ticket/00010001
/ticket/00010005
/title/00010000
/title/00010001
/title/00010004
/title/00010005
/tmp
/sys/disc.sys
/sys/uid.sys

Everything else is accessed in the real nand.
The saves and the channels are inside the /title tree and they're always taken from the emulated nand regardless of the full mode.

threeend · Apr 1, 2011

davebaol said:
Usually it happens for not fully supported drives.
Try using another hdd or pen drive.

Thx for the response davebaol. I tried putting the backup on a FAT32 formatted USB Thumbdrive and a FAT32 formatted SDHC card. Both have the same result of locking up withing 15-20 minutes.

I've also tried cIOS 249 v21 d2x4 b1 [56] and 250 [57]. These don't even see the hard drive/thumb drive. They do however recognize the thumb drive in FTPii v0.21 and they see apps on the drive in HBC. They do NOT recognize the USB thumb drive in Configurable v66, in Neo Gamma R9 v47, in USB Loader GX 2.1 r1080 , or in MPlayerCE USBTest (though I haven't seen that last one work with any setting).

Only when I run cIOS 249/250 v21 d2x4 b1 [58] then Configurable can detect and start the game (from either USB hard drive or thumb drive) but the game locks up within 20 minutes. Again I have tried 3 different backup games.

Base 58 was also the only version I had any success with in Waninkoko's v21 though it also had the same lockup problem. Thanks for any help you can offer.

icw35 · Apr 1, 2011

threeend said:
Base 58 was also the only version I had any success with in Waninkoko's v21 though it also had the same lockup problem. Thanks for any help you can offer.

Then there is something wrong with your setup. All the bases should work. I got base 37, 38, 56, 57, 58 installed and all of them work (not with all games). Do you have something like cioscorp installed?

papermanzero · Apr 2, 2011

Great Release.
Max and the Magic Marker is working now. =D

Unfortunately S&S not.
But here the Log:

QUOTE said:
FS returned: 0
FS_Close(): 537172388
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57535750/content, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Readdir(): (path: /title/00010001/57535750/content, iolen: 2)
FS_Readdir(): Calling FAT_ReadDir(, 0x123A580, 5)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0x123A580, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
1: title.tmd
2: 00000000.app
3: 00000001.app
4: 00000002.app
5: 00000007.app
FS_Readdir(): Calling os_sync_after_write(0x123A580,65) ----> outlen: 5
FS_Readdir(): Returning 0
FS returned: 0
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57535750/data, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Calling os_sync_after_write(0x138F0080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/fs, mode: 0)
FS_SetAttributes(): /title/00010001/57535750/data
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/es, mode: 0)
FS_Close(): 537172388
FS_Open(): (path: /dev/stm/immediate, mode: 0)
FS_Open(): (path: /dev/stm/eventhook, mode: 0)
FS_Open(): (path: /dev/fs, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/net/kd/request, mode: 1)
FS_Open(): (path: /dev/net/kd/request, mode: 0)
FS_Open(): (path: /dev/net/kd/time, mode: 0)
FS_Open(): (path: /dev/di, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/usb/oh1/57e/305, mode: 0)
FS_Readdir(): (path: /shared2/sys/SYSCONF, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Returning -106
FS returned: -106
FS_Delete(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=3
FS_Readdir(): Calling os_sync_after_write(0x135E1080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_CreateFile(): /shared2/sys/SYSCONF
FS returned: 0
FS returned: -6

QUOTE said:
Bonsai Barber has also issues (which didn't occur in d2x v2)
I will get a red screen which tells that an issue occurred with the memory.

QUOTEFS returned: 0
FS_Close(): 537172388
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57424e50/content, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Readdir(): (path: /title/00010001/57424e50/content, iolen: 2)
FS_Readdir(): Calling FAT_ReadDir(, 0x123A580, 5)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0x123A580, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
1: title.tmd
2: 00000000.app
3: 00000001.app
4: 00000006.app
5: 00000007.app
FS_Readdir(): Calling os_sync_after_write(0x123A580,65) ----> outlen: 5
FS_Readdir(): Returning 0
FS returned: 0
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57424e50/data, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=5
FS_Readdir(): Calling os_sync_after_write(0x138F0080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/fs, mode: 0)
FS_SetAttributes(): /title/00010001/57424e50/data
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/es, mode: 0)
FS_Close(): 537172388
FS_Open(): (path: /dev/stm/immediate, mode: 0)
FS_Open(): (path: /dev/stm/eventhook, mode: 0)
FS_Open(): (path: /dev/fs, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/net/kd/request, mode: 1)
FS_Open(): (path: /dev/net/kd/time, mode: 0)
FS_Open(): (path: /dev/di, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/usb/oh1/57e/305, mode: 0)
FS_Readdir(): (path: /shared2/sys/SYSCONF, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Returning -106
FS returned: -106
FS_Delete(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=3
FS_Readdir(): Calling os_sync_after_write(0x135E1080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_CreateFile(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys/SYSCONF, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Returning -106
FS returned: -106
FS_Delete(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=3
FS_Readdir(): Calling os_sync_after_write(0x135E1080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_CreateFile(): /shared2/sys/SYSCONF
FS returned: 0

Nevertheless. Good Release!
Btw. Now I know why the Beta3 didn't work. Because I didn't change the version to 21.

Etheboss · Apr 2, 2011

papermanzero said:
Great Release.
Max and the Magic Marker is working now. =D

Unfortunately S&S not.

But here the Log:

QUOTE said:

FS returned: 0
FS_Close(): 537172388
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57535750/content, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Readdir(): (path: /title/00010001/57535750/content, iolen: 2)
FS_Readdir(): Calling FAT_ReadDir(, 0x123A580, 5)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0x123A580, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
1: title.tmd
2: 00000000.app
3: 00000001.app
4: 00000002.app
5: 00000007.app
FS_Readdir(): Calling os_sync_after_write(0x123A580,65) ----> outlen: 5
FS_Readdir(): Returning 0
FS returned: 0
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57535750/data, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Calling os_sync_after_write(0x138F0080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/fs, mode: 0)
FS_SetAttributes(): /title/00010001/57535750/data
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/es, mode: 0)
FS_Close(): 537172388
FS_Open(): (path: /dev/stm/immediate, mode: 0)
FS_Open(): (path: /dev/stm/eventhook, mode: 0)
FS_Open(): (path: /dev/fs, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/net/kd/request, mode: 1)
FS_Open(): (path: /dev/net/kd/request, mode: 0)
FS_Open(): (path: /dev/net/kd/time, mode: 0)
FS_Open(): (path: /dev/di, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/usb/oh1/57e/305, mode: 0)
FS_Readdir(): (path: /shared2/sys/SYSCONF, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Returning -106
FS returned: -106
FS_Delete(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=3
FS_Readdir(): Calling os_sync_after_write(0x135E1080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_CreateFile(): /shared2/sys/SYSCONF
FS returned: 0
FS returned: -6

Bonsai Barber has also issues (which didn't occur in d2x v2)
I will get a red screen which tells that an issue occurred with the memory.

QUOTEFS returned: 0
FS_Close(): 537172388
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57424e50/content, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Readdir(): (path: /title/00010001/57424e50/content, iolen: 2)
FS_Readdir(): Calling FAT_ReadDir(, 0x123A580, 5)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0x123A580, entries=5
FS_Readdir(): Calling os_sync_after_write(0x133E84C0,4)
1: title.tmd
2: 00000000.app
3: 00000001.app
4: 00000006.app
5: 00000007.app
FS_Readdir(): Calling os_sync_after_write(0x123A580,65) ----> outlen: 5
FS_Readdir(): Returning 0
FS returned: 0
FS_Open(): (path: /dev/fs, mode: 0)
FS_Readdir(): (path: /title/00010001/57424e50/data, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=5
FS_Readdir(): Calling os_sync_after_write(0x138F0080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/fs, mode: 0)
FS_SetAttributes(): /title/00010001/57424e50/data
FS returned: 0
FS_Close(): 537172424
FS_Open(): (path: /dev/es, mode: 0)
FS_Close(): 537172388
FS_Open(): (path: /dev/stm/immediate, mode: 0)
FS_Open(): (path: /dev/stm/eventhook, mode: 0)
FS_Open(): (path: /dev/fs, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/net/kd/request, mode: 1)
FS_Open(): (path: /dev/net/kd/time, mode: 0)
FS_Open(): (path: /dev/di, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/es, mode: 0)
FS_Open(): (path: /dev/usb/oh1/57e/305, mode: 0)
FS_Readdir(): (path: /shared2/sys/SYSCONF, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Returning -106
FS returned: -106
FS_Delete(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=3
FS_Readdir(): Calling os_sync_after_write(0x135E1080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_CreateFile(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys/SYSCONF, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=0
FS_Readdir(): Returning -106
FS returned: -106
FS_Delete(): /shared2/sys/SYSCONF
FS returned: 0
FS_Readdir(): (path: /shared2/sys, iolen: 1)
FS_Readdir(): Calling FAT_ReadDir(, 0, 0)
FS_Readdir(): Return from FAT_ReadDir: outbuf=0, entries=3
FS_Readdir(): Calling os_sync_after_write(0x135E1080,4)
FS_Readdir(): Returning 0
FS returned: 0
FS_CreateFile(): /shared2/sys/SYSCONF
FS returned: 0

Click to expand...

Nevertheless. Good Release!
Btw. Now I know why the Beta3 didn't work. Because I didn't change the version to 21.

Hee papermanzero, you could have used a spoiler, like this....

fubka · Apr 3, 2011

I don't know if this is cIOS related, I run Rock Band 3 with retail disk, I had a USB 2.0 hub which no longer powers up attached devices. They do work if plugged directly into the Wii. Did one of these cIOS I install change the voltage or comparability? The hub works just fine in a PC.

Hacking cIOSX rev21d2x: Yet Another Hot Fix!!!!

Did d2x work for you?

Yes, I had an issue with the official cios and d2x fixed it

Yes, but everything was already working for me with the official cios

No, and I posted what goes wrong

No, and I won't report what goes wrong because I am a troll

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Wiitired but still kicking

Well-Known Member

Well-Known Member

Well-Known Member

Active Member

Wiitired but still kicking

Well-Known Member

Member

Well-Known Member

Active Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Official LULWUT supporter

Well-Known Member

Similar threads

Popular threads in this forum