Hacking Fail to rip Xenoblade fully. Please help!

  • Thread starter Thread starter oimori
  • Start date Start date
  • Views Views 10,556
  • Replies Replies 35
Status
Not open for further replies.

oimori

Member
Newcomer
Joined
Oct 25, 2014
Messages
13
Reaction score
0
Trophies
0
Age
37
XP
71
Country
I tried to rip Xenoblade(Japanese ver.) with cfg usb loader 70, but it only made an iso whose amount is 4.3GB.
I've heard that full size of Xenoblade(Chronicles) is 6.51GB. I think the reason is its dual-layer disk, but I don't know what to do.
I've tried clean rip and it said ''logical block address out of range" while it produced 4.3GB file, so clean rip is useless for me.
At present, wbfs file produced by cfg usb loader is working in both cfg usb loader and Dolphin, but it will cause problems.
Please tell me how to rip the disk fully!
.
 
If you're ripping directly to an HDD, make sure you're not ripping to a FAT32 drive - the file size limit of that file system is a little over 4GB and I don't think loaders split the dump automatically. You'll want to use an NTFS partition, even if only temporarily.
 
Try Usb Loader GX, it worked on mine

I tried it, but it said" Xenoblade : 4.10GB".
I'm trying ripping now with GX, but there will be more things to solve.

If you're ripping directly to an HDD, make sure you're not ripping to a FAT32 drive - the file size limit of that file system is a little over 4GB and I don't think loaders split the dump automatically. You'll want to use an NTFS partition, even if only temporarily.

I use a WBFS 8gb USB Flash Drive.
 
If you're ripping directly to an HDD, make sure you're not ripping to a FAT32 drive - the file size limit of that file system is a little over 4GB and I don't think loaders split the dump automatically. You'll want to use an NTFS partition, even if only temporarily.


Odd, I ripped it to FAT32, but USB Loader GX did indeed split the file into two WBFS files, worked fine when I ripped it, NTFS won't work on most USB loaders or other apps. Also dumped Super Mario Galaxy 2, Brawl and MK Wii, all of which use dual layered DVDs on FAT32. but again, it does split.
 
You're using WBFS files or the WBFS filesystem? Because they're two different things.
Odd, I ripped it to FAT32, but USB Loader GX did indeed split the file into two WBFS files, worked fine when I ripped it, NTFS won't work on most USB loaders or other apps. Also dumped Super Mario Galaxy 2, Brawl and MK Wii, all of which use dual layered DVDs on FAT32. but again, it does split.
I'm well-aware of that, what I said was that I don't know if the loader will split the file while dumping, which is why I suggested using a file system that works with 4GB+ files.
 
Care to explain how I ripped those to my FAT32 HDD? Once again, USB Loader splits anything > 4 GB. I'd be more than glad to show screenshots of the split WBFS files.
I was not sure if loaders split files while dumping, see above. If they do then good for him, he should use FAT32 instead of the obsolete WBFS.
 
I was not sure if loaders split files while dumping, see above. If they do then good for him, he should use FAT32 instead of the obsolete WBFS.


Well, I know for a fact that that 8.7 GB ISOs I ripped were indeed split by USB Loader GX.

Edit: Found this

http://wiki.robotz.com/index.php/Configurable_USB_Loader

Q: Isn't FAT limited to 4GB file size but a game iso is larger than 4GB?
A: Yes, that's why the .wbfs files are scrubbed to save space and if it is still larger than 4GB it is split to 4GB chunks. Split files are named gameid.wbfs, gameid.wbf1, gameid.wbf2,... similar to how the a .rar archive can be split to multiple files (.rar, .r01, .r02,...)
 
Welp, in that case I will go down my usual line of thought and blame WBFS as the party responsible for all the evils of the world (because it's usually the responsible party) and I'll suggest switching to a file system that works, for instance FAT32 or, if that fails, NTFS (only for the sake of the dump, not actual everyday use - that would be even worse than WBFS).
 
Welp, in that case I will go down my usual line of thought and blame WBFS as the party responsible for all the evils of the world (because it's usually the responsible party) and I'll suggest switching to a file system that works, for instance FAT32 or, if that fails, NTFS (only for the sake of the dump, not actual everyday use).


The files themselves are WBFS, the file system is FAT32


Source: http://wiki.robotz.com/index.php/Configurable_USB_Loader
Q: Isn't FAT limited to 4GB file size but a game iso is larger than 4GB?
A: Yes, that's why the .wbfs files are scrubbed to save space and if it is still larger than 4GB it is split to 4GB chunks. Split files are named gameid.wbfs, gameid.wbf1, gameid.wbf2,... similar to how the a .rar archive can be split to multiple files (.rar, .r01, .r02,...)

FAT32 with WBFS files.
 
The files themselves are WBFS, the file system is FAT32


Source: http://wiki.robotz.com/index.php/Configurable_USB_Loader
Q: Isn't FAT limited to 4GB file size but a game iso is larger than 4GB?
A: Yes, that's why the .wbfs files are scrubbed to save space and if it is still larger than 4GB it is split to 4GB chunks. Split files are named gameid.wbfs, gameid.wbf1, gameid.wbf2,... similar to how the a .rar archive can be split to multiple files (.rar, .r01, .r02,...)

FAT32 with WBFS files.
Thank you, I know that files on FAT32 drives have the WBFS extension, I was talking about WBFS the file system.
Maybe mine is wbfs file system formatted by wii backup manager.
Both are obsolete. Use Wii Backup Manager and FAT32 instead.
 
OK, I formatted the drive as you showed(FAT32 by WBM), and I retried, but USB Loader still says" Xenoblade: 4.10GB".
It should be 6.51GB.
 
OK, I formatted the drive as you showed(FAT32 by WBM), and I retried, but USB Loader still says" Xenoblade: 4.10GB".
It should be 6.51GB.
Does it show that size in the loader or is that the file size on the drive (Disconnect it and check on your PC)? Perhaps the loader only "sees" the first chunk. Also, are you scrubbing anything from the image? I have seen Xenoblade rips that are around that size.
 
In the loader. And after ripping, it literally produces 4.1GB file.
 
Does it show that size in the loader or is that the file size on the drive (Disconnect it and check on your PC)? Perhaps the loader only "sees" the first chunk. Also, are you scrubbing anything from the image? I have seen Xenoblade rips that are around that size.

No, I just tried to install it.

That's odd. Does CleanRip produce the same result when using a FAT32 drive?

Yes.
 
Do you have any other drive you could rip to instead of that stick? Can you post a sysCheck of your system?
 
Do you have any other drive you could rip to instead of that stick? Can you post a sysCheck of your system?

I have used SDHC card(both FAT32 and NTFS were tried) in clean rip, but it also said" logical block address out of range" when ripping reached 4.3GB. Maybe Clean rip recognizes the data is 6.5GB, but ripping itself fails.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum