|
DVD Drives for Wii & Gamecube Backups
|
|
|
IrishTR
Newbie
|
10. December 2007 @ 22:46 |
Link to this message
|
Originally posted by uou: Originally posted by IrishTR: I bought one of the H10Ns off Ebay and it does not work, my 8162 and 8163 both work.
All the users reporting to work had the 0B10 firmware. No other firmware version has been reported to work.
Mine is a 0D04 and like others who reported non working we all had the same firmware...
Ah, so it's only the H10N with 0B10 firmware that work. Thanks for that info! I'll update the OP.
Probably one of the best places to get help with backing up the firmware is at http://club.cdfreaks.com
Do you have a link to the discussion about the firmware?
One discussion
http://psx-scene.com/forums/wii-general-...ta-dvd-rom.html
And another relevant to the subject
http://psx-scene.com/forums/wii-disc-dum...html#post445911
|
|
Advertisement
|
  |
|
|
Member
|
10. December 2007 @ 23:53 |
Link to this message
|
|
|
|
isimig23
Junior Member
|
11. December 2007 @ 00:47 |
Link to this message
|
Originally posted by uou: Originally posted by Pelzie: I have an HL-DT-ST GDR-8160B and I believe that it is able to read the Wii discs...
Great! What is your firmware version? Usually if the drive does not work, then you will get the following error right at the start: Error!! You might have a faulty Drive!!
I experienced the exact same unhandled exception error due to arithmetic on a known working 8164B after I used Windows Update to update to .net Framework 3.0. I recommend sticking with 2.0 ONLY. I believe this error also occurs when a disc is scratched and cannot be read.
How far into the dump do you get before getting this error?
Also, all four of my drives, 8161, 8162, 8163, and 8164 work just fine with Ultra DMA - never had to use PIO on any of them. I'm using XP PRO SP2 fully updated.
When using all three of my 8160b drives with rawdump, the software acted as if it could detect that a wii disc was inserted, however, it was never able to provide a title for the disc and ultimately you would get an unhandled exception error. It NEVER gave me a "you may have a faulty drive" error. However, I was never able to get a successful rip. I had no trouble at all with my 8161b. I wish you people would listen to me instead of trying to do things the hard way. Uou seems to be obsessed with claiming that the 8160 works even though the folks who developed rawdump do not list it as a compatible drive and the ONLY person who ever claimed to get a full successful rip with the 8160 is completely MIA while we all go around in circles. Meanwhile, he keeps going on about firmware revisions that simply do not exist: There are no firmware updates available for this drive. They are not out there. Trust me, I know. I spent way too much time trying to make these drives work. I am trying to save you the headache.
This message has been edited since posting. Last time this message was edited on 11. December 2007 @ 00:48
|
Member
|
11. December 2007 @ 01:44 |
Link to this message
|
|
Once again I'll ask for your help.
What are the brand names, exact models, and firmware versions of your three 8160s?
There may have not been an official released firmware update for the 8160, but that does not mean that there are not different versions of the firmware. We already know there are different firmwares for the drive. So far two different firmware versions have been posted in this very thread. It may still be a matter of simply flashing the correct firmware to your drive.
|
|
IrishTR
Newbie
|
11. December 2007 @ 07:26 |
Link to this message
|
Originally posted by uou: So, did you try flashing this H10N 0B10 firmware that is reported to work?
Cant there is no way to flash it at this point with any firmware (LG doesnt have any tool for just flashing unless its a released updated one) Which they dont make for the H10Ns. And others stated to get a hack to work some flashing programs would need to be rewritten to work with the 0B10 to the other versions. Wish I could do it but thats waaay over my head lol.
|
|
isimig23
Junior Member
|
11. December 2007 @ 12:53 |
Link to this message
|
Originally posted by uou: Once again I'll ask for your help.
What are the brand names, exact models, and firmware versions of your three 8160s?
There may have not been an official released firmware update for the 8160, but that does not mean that there are not different versions of the firmware. We already know there are different firmwares for the drive. So far two different firmware versions have been posted in this very thread. It may still be a matter of simply flashing the correct firmware to your drive.
Well you find me a flash utility that will work with this drive, and I will use it. I could not find one anywhere on the web. And by the way, wiible said it recognizes discs, he NEVER said that he got a successful rip. In fact, so far, no one has claimed that they got a successful rip with an 8160. Once again, I ask where wiible is. Maybe he can explain just how far he got with an 8160b. Once again, they all recognize that the disc is a wii disc, but they are never able to give you the title and then they get a protection error. Can everyone else who ever tried an 8160b please sound off and describe your exact symptoms? I can just about guarantee that you are wasting your time with an 8160. It will not work.
|
Member
|
11. December 2007 @ 14:29 |
Link to this message
|
If I get some time I'll help search for a flash utility. I know the guys at cdfreaks.com have been writing flash utilities for years, many of them can flash multiple models of drives and cross flash with firmware from other models.
One of the first things to try should be 360 firmware toolbox, I believe the latest version is 4.5. Especially for the H10N since that is what the H10N firmware was dumped with. Also there are several DOS flash utilities, like mktflash.
Again, please list your drive details - brand, manufacture date, ROM version, full model number, and firmware versions. This is the only way to find out all the different versions and is something you can easily do in a minute or two.
Start>Control Panel>System>Hardware>Device Manager>DVD/CD-ROM drives>[double click a drive]>Details
The number after the model number is the firmware version.

This message has been edited since posting. Last time this message was edited on 11. December 2007 @ 14:34
|
|
isimig23
Junior Member
|
11. December 2007 @ 14:53 |
Link to this message
|
Originally posted by uou: If I get some time I'll help search for a flash utility. I know the guys at cdfreaks.com have been writing flash utilities for years, many of them can flash multiple models of drives and cross flash with firmware from other models.
One of the first things to try should be 360 firmware toolbox, I believe the latest version is 4.5. Especially for the H10N since that is what the H10N firmware was dumped with. Also there are several DOS flash utilities, like mktflash.
Again, please list your drive details - brand, manufacture date, ROM version, full model number, and firmware versions. This is the only way to find out all the different versions and is something you can easily do in a minute or two.
Start>Control Panel>System>Hardware>Device Manager>DVD/CD-ROM drives>[double click a drive]>Details
The number after the model number is the firmware version.

Ok, fine I will reinstall all three drives and look up those numbers. However, are you SURE that is a firmware revision? There is an area for firmware. See that drop-down box? Pull that down and select firmware. When I checked that, it was blank.
By the way, I still am waiting for someone to say these words: "I got a SUCCESSFUL RIP using the 8160b." NO ONE has said this on ANY forum. Wiible has not said anything in any of these dialogs for the last two weeks. Being that he is completely MIA, I am willing to believe that he very quickly glanced at the screen, saw that raw dump said "Wii disc detected" and decided that it works. If he had sat there for another couple of minutes, he would have noticed that rawdump never reported the title of the disc, and in actuality, never started the process (no elapsed time or time remaining will ever be displayed). Ultimately Raw dump will report a general protection error. I tired version 2.0, 1.4, 1.3, 1.2, 0.4, and 0.3 (I think. I basically tried every one I could find.) I also tried friidump and got a similar result.
What I really want, is someone who had a successful rip with the drive to speak up. The lack of any of these people, leads me to believe that it is a myth.
|
|
IrishTR
Newbie
|
11. December 2007 @ 20:38 |
Link to this message
|
Originally posted by uou: If I get some time I'll help search for a flash utility. I know the guys at cdfreaks.com have been writing flash utilities for years, many of them can flash multiple models of drives and cross flash with firmware from other models.
One of the first things to try should be 360 firmware toolbox, I believe the latest version is 4.5. Especially for the H10N since that is what the H10N firmware was dumped with. Also there are several DOS flash utilities, like mktflash.
Again, please list your drive details - brand, manufacture date, ROM version, full model number, and firmware versions. This is the only way to find out all the different versions and is something you can easily do in a minute or two.
Start>Control Panel>System>Hardware>Device Manager>DVD/CD-ROM drives>[double click a drive]>Details
The number after the model number is the firmware version.

To save you some trouble the 360 Firmware Toolbox is coded to only flash the 360's 3120L model drives based on that firmware. As stated on other sites it would take some hacking and slashing to how the firmware identifies and writes to our H10Ns.
Like I said I can only follow no way am I a leader on this type of stuff as it is way outta my league. No programming skills here just using skills LOL. Perhaps the CDFreaks might whip something up, I know the RPC1 Firmware site that usually has every dang brand/model available gets something going but they had nada for these drives.
The 360 community is actually trying to get these H10Ns to replace the Kreon drives used to read/rip Xbox360 games so its kinda a waiting game to see who gets it to take flashes and for what system I guess LOL.
|
|
AJRogers
Newbie
|
12. December 2007 @ 15:02 |
Link to this message
|
All done by me.
-Unmodded 360 - I enjoy my warranty on this sketchy machine :)
-WiiKey Wii
-DMS4 Ps2
Gamertag: AJRogers
This message has been edited since posting. Last time this message was edited on 12. December 2007 @ 15:04
|
Member
|
12. December 2007 @ 18:48 |
Link to this message
|
|
Thanks for the nice images! I just noticed something that will make looking up your firmware version so much easier for everyone - it's displayed right in Rawdump. :D
The firmware version in Rawdump is the last four digits in the "Select Drive" box.
So in the images above his firmware is 0043.
The firmware on my 8161B is 0100.
Next time you rip a disc all the way through, post what kind of speed in MB/hour you get with the 0043 firmware. I see it started out at 2422, not bad.
This message has been edited since posting. Last time this message was edited on 12. December 2007 @ 18:50
|
|
AJRogers
Newbie
|
12. December 2007 @ 19:10 |
Link to this message
|
Originally posted by uou: Thanks for the nice images! I just noticed something that will make looking up your firmware version so much easier for everyone - it's displayed right in Rawdump. :D
The firmware version in Rawdump is the last four digits in the "Select Drive" box.
So in the images above his firmware is 0043.
The firmware on my 8161B is 0100.
Next time you rip a disc all the way through, post what kind of speed in MB/hour you get with the 0043 firmware. I see it started out at 2422, not bad.
Actually it stayed right in that area the whole time. I was away from the pc for about an hour and when I came back it was still around that speed. So I don't know if it spiked any higher, but I doubt it.
All done by me.
-Unmodded 360 - I enjoy my warranty on this sketchy machine :)
-WiiKey Wii
-DMS4 Ps2
Gamertag: AJRogers
|
Member
|
12. December 2007 @ 19:37 |
Link to this message
|
|
So the final speed result was about 2422?
|
|
AJRogers
Newbie
|
12. December 2007 @ 20:22 |
Link to this message
|
Originally posted by uou: So the final speed result was about 2422?
Yes sir.
Is it typical for a backup to be unreadable by the pc when you are finished with it? I decided to go ahead and burn the iso that rawdump created (it was 4.37gb) and the pc won't read it. I'm waiting on a new Wiikey so I can test it out with my Wii.
All done by me.
-Unmodded 360 - I enjoy my warranty on this sketchy machine :)
-WiiKey Wii
-DMS4 Ps2
Gamertag: AJRogers
|
Member
|
12. December 2007 @ 20:26 |
Link to this message
|
|
Yes, the PC won't read it. Congrats on getting the second fastest drive, 8161B. :)
Now, your's is a GRD-8161b on the label? I see it says GDR in Rawdump. So was the "GRD" just a typo or does it say that on the label?
This message has been edited since posting. Last time this message was edited on 12. December 2007 @ 20:32
|
|
AJRogers
Newbie
|
12. December 2007 @ 21:44 |
Link to this message
|
Originally posted by uou: Yes, the PC won't read it. Congrats on getting the second fastest drive, 8161B. :)
Now, your's is a GRD-8161b on the label? I see it says GDR in Rawdump. So was the "GRD" just a typo or does it say that on the label?
That is good to hear, sounds like this backup may work. It was weird though, I couldn't burn the iso with dvd decrypter, I used Nero *shrug*. Whatever.
Oh and GRD was a typo on the seller's website. It's GDR on the label. :)
That's what I was praying for when I ordered it, haha.
All done by me.
-Unmodded 360 - I enjoy my warranty on this sketchy machine :)
-WiiKey Wii
-DMS4 Ps2
Gamertag: AJRogers
|
Member
|
12. December 2007 @ 21:48 |
Link to this message
|
Originally posted by AJRogers: BTW, This is a refurbished unit. $29.00 and free shipping.
That's a decent price then. They still have two left:
http://www.cheeverind.com/parts/GRD-8161B.aspx
Since we saw a lot of google results for GRD, I wonder if you could not find more deals on these "typo" drives.
lol
|
Member
|
12. December 2007 @ 22:33 |
Link to this message
|
A little about the model numbers here:
http://club.cdfreaks.com/1289258-post2.html
B for internal desktop units (e.g. 4160B)
D for external units (e.g. 2166D)
N for ultra slim notebook units (4082N)
In other words, models ending in B, D or N, should all be the same type of drive, i.e. and 8161D would just be an external version.
Same for the newer units:
E for external units
H for internal desktop units
T for slim laptop units
So, an H10E should be the same as an H10N, just the external version.
Looks like I can modify the search for many more drives!
|
Member
|
12. December 2007 @ 23:16 |
Link to this message
|
|
H10 firmwares that DO NOT work: 0D04, D70D
|
Member
|
13. December 2007 @ 00:25 |
Link to this message
|
For those of you that have a GDR-H10N, what happens when you run the flash utility for the GDR-H20N or GSA-H10N? Don't try to flash with this firmware as it's not compatible, I just want to know if the included flash program is compatible and recognizes your drive.
LG/HLDS Model: GSA-H30N SATA
Flash utility for GDR-H20N
Flash utility for GSA-H10N
LG/HLDS Model: GSA-S10N
Flash Utility for GDR-8081N, 8083N: Diskette and CD
Other LG firmware utility packages
Also try the flash utilities listed below in my next post for the 8160 series of drives.
If we get a flash utility that is compatible, we already have the 0B10 firmware, so it may just be a matter of replacing the firmware portion of the update with 0B10 and then running the flasher.
Finding and editing the firmware into the flasher is something I can handle. Essentially it should only be a matter of cut and paste with hex editor.
This message has been edited since posting. Last time this message was edited on 13. December 2007 @ 02:17
|
Member
|
13. December 2007 @ 00:40 |
Link to this message
|
Likewise, I'm wondering if any of the firmware flahers for the other GDR or 8160 drives least recognize the GDR-8160B. If you have an 8160B please try some of these flashers to see if they at least recognize the drive, but don't flash. If the flash utility is compatible, then it may also be a matter of replacing just the firmware file or portion of the .exe that contains the firmware. Of course with the 8160B, we still need to find a drive that works and dump the firmware, but at least if we have a compatible flash utility then we will have more reason to look.
Search for 8160, 8161, and 8163 here:
http://us.lgservice.com
The flash utilities I found were:
Flashup.exe for GDR-8161B
GDR-8163B0L23.exe for GDR-8163B
LG_DRD8160B-LOTR.exe for DRD-8160B
GCE-8160B
This message has been edited since posting. Last time this message was edited on 13. December 2007 @ 01:21
|
Member
|
13. December 2007 @ 03:59 |
Link to this message
|
Here's a great site for LG GDR modified firmware:
http://tdb.rpc1.org/
Now to figure out if any of these flash utilities will work with the 0B10 firmware in the OP...
|
Member
|
13. December 2007 @ 10:12 |
Link to this message
|
|
|
|
Samuel118
Newbie
|
13. December 2007 @ 20:59 |
Link to this message
|
This site appears to have some 8161b's in stock
Link
|
|
Advertisement
|
  |
|
|
IrishTR
Newbie
|
13. December 2007 @ 23:27 |
Link to this message
|
Originally posted by uou: For those of you that have a GDR-H10N, what happens when you run the flash utility for the GDR-H20N or GSA-H10N? Don't try to flash with this firmware as it's not compatible, I just want to know if the included flash program is compatible and recognizes your drive.
LG/HLDS Model: GSA-H30N SATA
Flash utility for GDR-H20N
Flash utility for GSA-H10N
LG/HLDS Model: GSA-S10N
Flash Utility for GDR-8081N, 8083N: Diskette and CD
Other LG firmware utility packages
Also try the flash utilities listed below in my next post for the 8160 series of drives.
If we get a flash utility that is compatible, we already have the 0B10 firmware, so it may just be a matter of replacing the firmware portion of the update with 0B10 and then running the flasher.
Finding and editing the firmware into the flasher is something I can handle. Essentially it should only be a matter of cut and paste with hex editor.
None recognized it :( at all
|