Jump to content
RealModScene
devilhunter

Modified Mupen64 0.993 Beta 2 for Hitachi Drive (Not Working Properly)

Recommended Posts

Greetings, 

I was looking for Mupen64 0.993 source, apparently its not there. I was trying to get it working on my xbox 360 with Hitachi Drive. The problem is it keeps getting stuck at "Fat Mount". Anyways, Ive edited Xenon.elf to bypass the DVD checkup and it loads to the emulator. 

Now here is the problem, first thing I noticed is that the background image doesnt load, also when a game is selected, it loads briefly (2-3 secs) then reboots back to Xell ! 

If you have a clue on whats going on, please let me know. 

Please look in the attachment for the modified parts.

 

This ver. works flawlessly on Hitache (Phat + Slim)

 

https://www.mediafire.com/?ju3zxsabdztf4e2

post-75799-0-90378100-1462786588_thumb.png

post-75799-0-33401800-1462786592_thumb.png

Share this post


Link to post
Share on other sites

Greetings, 

I was looking for Mupen64 0.993 source, apparently its not there. I was trying to get it working on my xbox 360 with Hitachi Drive. The problem is it keeps getting stuck at "Fat Mount". Anyways, Ive edited Xenon.elf to bypass the DVD checkup and it loads to the emulator. 

Now here is the problem, first thing I noticed is that the background image doesnt load, also when a game is selected, it loads briefly (2-3 secs) then reboots back to Xell ! 

If you have a clue on whats going on, please let me know. 

Please look in the attachment for the modified parts.

hmm.. have you tried to disconnect the dvd drive?? 

and honestly.. i didnt think the dvd drive would cause a problem.. as it is being ran from USB right??.. 

  • Like 1

Share this post


Link to post
Share on other sites

hmm.. have you tried to disconnect the dvd drive?? 

and honestly.. i didnt think the dvd drive would cause a problem.. as it is being ran from USB right??.. 

There is a known bug in LibXenon that causes to hang (or wait for dvd/usb infinitely) for toshiba drives. The bug was fixed by Swizzy in a patched version of 0.993 Xell. However, the latest Mupen uses that code. 

 

If I disconnect the dvd, it will work as Xell worked for me. 

Share this post


Link to post
Share on other sites

There is a known bug in LibXenon that causes to hang (or wait for dvd/usb infinitely) for toshiba drives. The bug was fixed by Swizzy in a patched version of 0.993 Xell. However, the latest Mupen uses that code.

If I disconnect the dvd, it will work as Xell worked for me.

Well you can always get a new dvd drive and pair it with your rgh.. problem solved right?? Thats the good thing about having a rgh.. no more problems.. ;-)

All that would really be required is changing a setting in the nand.. to match the new drive.. you can use same dvd key.. if youd like..

Share this post


Link to post
Share on other sites

felida, on 09 May 2016 - 2:54 PM, said:

Well you can always get a new dvd drive and pair it with your rgh.. problem solved right?? Thats the good thing about having a rgh.. no more problems.. ;-)

All that would really be required is changing a setting in the nand.. to match the new drive.. you can use same dvd key.. if youd like..

I do have a spare Benq, I flashed it with LT+ 1.1 and the 04220 one, and spoofed the Key only then I flashed it to stock with the Hitachi Key spoofed. The drive runs @ max speed, spins really loud then the dashboard says "Eject Disk". Here is the JF log.

JungleFlasher 0.1.96 Beta (323) Log:

------------------------

Requesting Device ID

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes

Getting Status from port 0x01F0

Serial flash found with Status 0x73

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................

Dumped in 2480mS

Benq Dump file saved to BENQcfw.bin

Loading firmware from buffer

Inquiry string found

Identify string found

Drive key @ 0xE040 8BA17172C296A26C9EB8A348DEF49184

Firmware Osig: [PBDS VAD6038-64930C ]

Spoofed As: [sATA DVD-ROM 6243]

Firmware is: LT-Plus 1.1

Key database updated

Auto-Loading firmware file C:\Users\Asus\Desktop\JungleFlasher v0.1.96 Beta (323)\Firmware\LTPlus-benq-v1.1.bin

MD5 hash: c45d60fbd68cc642b2235ba12e5aad7d

Genuine LT plus v1.1

Inquiry string found

Identify string found

Drive key @ 0xE040 77777777777777777777777777777777

Firmware Osig: [PBDS VAD6038-64930C ]

Firmware is: LT-Plus 1.1

Spoofing Target

DVD Key copied to target

Inquiry string copied to Target

Identify string copied to Target

Loading MTK_Flash source file

Loading firmware file G:\BenQ backup1\BENQ-OFW.bin

MD5 hash: 3868bc328b85360082d5ba3ac4e0b46d

Inquiry string found

Identify string found

Drive key @ 0xC030 E5CFDCF5B11CE746066D2899B82ED3C1

Firmware Osig: [sATA DVD-ROM 6243]

Firmware is: Stock

Spoofing Target

DVD Key copied to target

ID strings already match

Serial data already matches

Loading firmware file C:\Users\Asus\Desktop\LTPlus-0442-v3.0.bin

MD5 hash: 8784e0f4ce27941a2a3293c8a5ac85e4

Genuine LT plus v3.0

Inquiry string found

Identify string found

Drive key @ 0xA020 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Firmware Osig: [PBDS VAD6038 0442]

Firmware is: LT-Plus 3.0

Spoofing Target

DVD Key copied to target

Target is LT - ID strings not copied to Target

DVD Key copied to target

ID strings already match

Getting Status from port 0x01F0

SPi flash found with Status 0x73

Sending Chip Erase to Port 0x01F0

Erasing:

Writing target buffer to flash

Writing Bank 0: ................

Writing Bank 1: ................

Writing Bank 2: ................

Writing Bank 3: ................

Flash Verification Test !

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................

Write verified OK !

Loading firmware file G:\BenQ backup1\BENQ-OFW.bin

MD5 hash: 3868bc328b85360082d5ba3ac4e0b46d

Inquiry string found

Identify string found

Drive key @ 0xC030 E5CFDCF5B11CE746066D2899B82ED3C1

Firmware Osig: [sATA DVD-ROM 6243]

Firmware is: Stock

Spoofing Target

DVD Key already matches

ID strings already match

Serial data already matches

DVD Key copied to target

ID strings already match

Drive is Benq..

Drive is Benq..

Sending Magic Keys to Drive on port 0x01F0

.................................................

Done!

Sending Vendor Intro

Requesting Device ID

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes

Getting Status from port 0x01F0

SPi flash found with Status 0x73

Sending Chip Erase to Port 0x01F0

Erasing:

Writing target buffer to flash

Writing Bank 0: ................

Writing Bank 1: ................

Writing Bank 2: ................

Writing Bank 3: ................

Flash Verification Test !

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................

Write verified OK !

Getting Status from port 0x01F0

Serial flash found with Status 0x73

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................

Dumped in 2465mS

Benq Dump file saved to BENQ-OFW-fal key.bin

Loading firmware from buffer

Inquiry string found

Identify string found

Drive key @ 0xC030 8BA17172C296A26C9EB8A348DEF49184

Firmware Osig: [sATA DVD-ROM 6243]

Firmware is: Stock

Key database updated

Auto-Loading firmware file C:\Users\Asus\Desktop\JungleFlasher v0.1.96 Beta (323)\Firmware\LTPlus-benq-v1.1.bin

MD5 hash: c45d60fbd68cc642b2235ba12e5aad7d

Genuine LT plus v1.1

Inquiry string found

Identify string found

Drive key @ 0xE040 77777777777777777777777777777777

Firmware Osig: [PBDS VAD6038-64930C ]

Firmware is: LT-Plus 1.1

Spoofing Target

DVD Key copied to target

Inquiry string copied to Target

Identify string copied to Target

Loading MTK_Flash source file

Loading firmware file G:\BenQ backup1\BENQ-OFW3.bin

MD5 hash: 3868bc328b85360082d5ba3ac4e0b46d

Inquiry string found

Identify string found

Drive key @ 0xC030 E5CFDCF5B11CE746066D2899B82ED3C1

Firmware Osig: [sATA DVD-ROM 6243]

Firmware is: Stock

Edited by Swizzy
Cleaned up tags for the JF log

Share this post


Link to post
Share on other sites

You dont spoof the drive, you change the drive in the nand.. from hitachi to benq.. just make sure dvd is the same on both.. you can even create a new dvd key if youd like.. spoofing would be the wrong way to change it.. lol.. as you are still stuck with hitachi in the nand..

  • Like 1

Share this post


Link to post
Share on other sites

You need to get rid of that spoof data, it's not normal to have on LT+3.0 and probably breaks it...

You may also want to double check the SATA and Power cables, if they're bad or poorly connected, this would be a possible scenario...

Share this post


Link to post
Share on other sites

You need to get rid of that spoof data, it's not normal to have on LT+3.0 and probably breaks it...

 

You dont spoof the drive, you change the drive in the nand.. from hitachi to benq.. just make sure dvd is the same on both.. you can even create a new dvd key if youd like.. spoofing would be the wrong way to change it.. lol.. as you are still stuck with hitachi in the nand..

 

You may also want to double check the SATA and Power cables, if they're bad or poorly connected, this would be a possible scenario...

ok sorry. My bad. 

Share this post


Link to post
Share on other sites

You dont spoof the drive, you change the drive in the nand.. from hitachi to benq.. just make sure dvd is the same on both.. you can even create a new dvd key if youd like.. spoofing would be the wrong way to change it.. lol.. as you are still stuck with hitachi in the nand..

No need to reflash the xbox, Ive fixed it  :sorcerer:

Its working on Hitachi now. 

By the way, if you can patch the nand by clicking on "nofcrt", you can use any drive on that. 

 

Chao. 

Share this post


Link to post
Share on other sites

No need to reflash the xbox, Ive fixed it  :sorcerer:

Its working on Hitachi now. 

By the way, if you can patch the nand by clicking on "nofcrt", you can use any drive on that. 

 

Chao.

Not quite, that patch is primarily for slim consoles to not use the fcrt (Firmware Challenge Response Table) which allows the drives to function properly, but it doesn't make any drive work, it's primarily that it doesn't care what the firmware actually says about anything...

Share this post


Link to post
Share on other sites

Not quite, that patch is primarily for slim consoles to not use the fcrt (Firmware Challenge Response Table) which allows the drives to function properly, but it doesn't make any drive work, it's primarily that it doesn't care what the firmware actually says about anything...

I see, thanks a lot once again, I remember swapping a hitachi drive with Benq two years ago. It worked. Never mind. I removed the "Dvd" mount from the hex editor and its working now.

https://www.mediafire.com/?ju3zxsabdztf4e2

Share this post


Link to post
Share on other sites

Nice, works like a charm on mine.

 

Does anyone know how to make Turok run without crashing after some time? Because you can start playing and see that the game has a good framerate and it's working fine, until it crashes.

I put "AccurateTextureMapping=1" on the Turok part of RiceVideoLinux.ini, like the other Turok titles have, and it kinda gives the game a better performance (the title screen doesn't stutter for a second anymore), but it still crashes after some time playing.

  • Like 1

Share this post


Link to post
Share on other sites
On 1/22/2017 at 10:55 PM, PauloKoast said:

Nice, works like a charm on mine.

 

Does anyone know how to make Turok run without crashing after some time? Because you can start playing and see that the game has a good framerate and it's working fine, until it crashes.

I put "AccurateTextureMapping=1" on the Turok part of RiceVideoLinux.ini, like the other Turok titles have, and it kinda gives the game a better performance (the title screen doesn't stutter for a second anymore), but it still crashes after some time playing.

the emulator isnt complete sadly, its very close though. 

Share this post


Link to post
Share on other sites

Hey, sorry to reply a super old post (if people here care about that sort of thing), but would it be possible for you to do this with the latest release of Mupen64? I have the same issue and nobody else seems to be willing to do anything besides tell me to disconnect my DVD drive.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...