JungleFlasher v0.1.64 (16) Options

[Xbox-Scene]

JungleFlasher v0.1.64 (16) Posted by XanTium | July 3 22:43 EST | News Category: Xbox360

A new version of JungleFlasher(info) has been released: [QUOTE] * General items Updated Ctrl + F4 to open iXtreme from firmware folder to Target Added context menus to Source and target tabs Source - open f/w from working folder - clear source - update to key data base Target - open f/w from working folder - open f/w from .\firmware folder - clear target Removed - not allowing blank serial in for Lite-on Dummy.bin - previously if serial was blank the iX file serial was left as is - Warning changed for dummy.bin w/o serial, to mention is possibly ok. * Key Database in Registry Database will be populated automatically from a dump. Ctrl + F10 to add/update key database from Source tab info Ctrl + F12 to launch notepad with key database Ctrl + F11 to create .csv from key database Added extra item to explorer(info) context to load as source and add key to db - iX will not autoload to target for this task - can select mutliple f/w files, these will load in turn * Hitachi Support Updated Fixed bug in Rev 36 Ram Upload Dump Code All dumps are rev checked immediately, a failure to identify will abort sequence - dumps from other drives and locked 79's (coming back empty) would proceed to key - check and fail * MTKFlash32 Added warning message Yes/No to Flash Erase Button (default is No!) Added Esc to abort to flash read within auto reads in moddermode Bypassed Sammy-Un-Lock warning in ModderMode [/QUOTE] Official Site: http://jungleflasher.net Download: here

[biggnick]

Damn, good release.


This would have been useful to me 4 days ago when I locked my v78 due to that Ram Upload Error! Now it is worthless without TSOP unsoldering.


Beta is Beta is Beta.


Thanks though!

[Martinchris23]

Damn, good release.
This would have been useful to me 4 days ago when I locked my v78 due to that Ram Upload Error! Now it is worthless without TSOP unsoldering.
Beta is Beta is Beta.
Thanks though!

I'm still using v0.1.55 for Hitachi drives as I find the PortIO better than WinAPI. It's a shame your drive wasn't pre v78 as you may have been able to restore it. As it stands, you can't get it into Mode-b now so it's not going to help you.

[OggyUK]

Theres a hidden option to enable portio withuout via/no drivers

This post has been edited by OggyUK: Jul 5 2009, 01:15 AM

[steak]

I have a Hitachi 79FL, what is the best way to go now? should I wait for the 1.6 or 1.51 working fine?

thx!

steak

[DoomSayerSantos]

I have a Hitachi 79FL, what is the best way to go now? should I wait for the 1.6 or 1.51 working fine?

thx!

steak

1.51 is fine.
Just make sure your games are properly backed up.
1.6 for Hitachi could still be very far away.

[Martinchris23]

Theres a hidden option to enable portio withuout via/no drivers

Care to divulge?

[brwcrw]

ya, check 'VIA ports Only' under the DVDKey32 tab (top center of that tab)

[saulin]

1.51 is fine.
Just make sure your games are properly backed up.
1.6 for Hitachi could still be very far away.

Well that's bad news. I was hoping that after so long 1.6 for Hitachi would be very close to release. Mmmm well if 1.51 is working just fine for new games then I might just upgrade to that one then. I haven't touched my 360 in probably 3-4 months. But I feel like playing SF4 and perhaps one or two more 360 games so I guess it's time to upgrade the F/W.

[Martinchris23]

ya, check 'VIA ports Only' under the DVDKey32 tab (top center of that tab)

Umm, yeah thanks... I know how to restrict the ports to via only...

I was asking how to enable the PortIO method for Hitachi drives as it's been greyed out on all versions newer than 0.1.55 ..

[podger]

Martinchris23: The PortIO method was included and intended for use with Via cards. Mainly in light of the situation where users had removed the drivers to overcome the Lite-On-Erase lockup issues. Obviously, without drivers the Hitachi cannot show in windows with a driver letter, so conventional WinApi methods were useless.

Portio will only be available when "Via ports only" is selected AND where the card reports error (code 39) in the device manager, basically the error reported with the drivers removed.

[Martinchris23]

Martinchris23: The PortIO method was included and intended for use with Via cards. Mainly in light of the situation where users had removed the drivers to overcome the Lite-On-Erase lockup issues. Obviously, without drivers the Hitachi cannot show in windows with a driver letter, so conventional WinApi methods were useless.

Portio will only be available when "Via ports only" is selected AND where the card reports error (code 39) in the device manager, basically the error reported with the drivers removed.

Cheers for the reply Podger - at least that explains why my option is greyed out! I use uniATA drivers instead of VIA ones as PortIO32 doesn't directly support my VIA 6421 PCMCIA card. Is there any way I can force PortIO mode without having error 39 in Device Manager?

This post has been edited by Martinchris23: Jul 6 2009, 10:22 AM

[podger]

I guess then that you are using a PCMCIA card or that your PCI slot is south of a PCI-PCI bridge. The bridging in both these cases seems to mess up JF's ability to use the IO ports w/o drivers.

I also noticed on my laptop that although, the UniATA driver gets the portIO going it does not install "fully" enough for hitachi's to show up properly with a drive letter.... I find USB 2 Sata a good fall back in this case.

This post has been edited by podger: Jul 6 2009, 11:03 AM

[Retroplay]

1.51 is fine.
Just make sure your games are properly backed up.
1.6 for Hitachi could still be very far away.

Even if 1.6 was released for Hitachis I don't see any reason why I would want to update anyway.
1.51 plays all games just fine and I always scan backups with ABGX360 to make sure they're properly stealth patched.

[tomgreen99200]

great work! This program works great, i used to two days ago to do a friends hitachi. I have also done a couple benq without a problem. Thanks a lot !!