Search the Community

using command: "wmic diskdrive get model,name". Results are: Model Name Innostor Ext. HDD USB Device \\.\PHYSICALDRIVE4 fatxplorer 3.0 is not detecting it too.

Hi all, I'm relatively new to the original Xbox modding scene, and if you read my recent post in the welcome section you will be aware that I'm currently making up a batch of Jafar modchips. I know there are better chips with more features, but I wanted to start with something simple and work my way up to the more complex things if that makes sense. It's been going well and I've learned a lot but I'm curious about a small issue I've come across and wondered if anybody in the community has come across the same thing and created a work-around... I ordered 100 SST49LF080A chips from aliexpress (yes, I know, but I'm not made of money and 50p each vs £3 - £4 each from somewhere like digikey I figured it was worth the risk!). Anyway, out of these 100, 93 of them work absolutely fine. In Xgecu Pro, the device ID is shown to be BF 5B. These all flash perfectly and work perfectly in the Jafar modchips. 6 of the 7 that don't work, show a device ID of BF 5A instead. The 1 remaining chip shows a device ID of 3B 3B. The 6 "BF 5A" ones will flash absolutely fine in Xgecu Pro providing I untick the device id check first, and the contents of the flash chip are read back absolutely fine also (again, with device id check unticked). This leads me to believe that although the device ID is slightly different, the pin outs etc and the way the device operates must be the same, since I can both read and flash using the SST49LF080A@PLCC32 profile in Xgecu Pro. HOWEVER, when I put any of these in a Jafar and install in the Xbox, I get the 3 boot attempts and FRAG. This leads me to think that the Lattice CPLD code has been written to specifically target device IDs BF 5B and wont work with anything else even if the pinouts etc are the same. Am I wrong in making that assumption? So, since the VHDL coding for the Lattice CPLD has been released and is open source, I thought I may be able to inspect it, find the reference to BF 5B and possibly modify it to include BF 5A aswell. I clearly have a lot to learn because I cant find reference to that device ID anywhere. Furthermore, the ispLever classic software required to compile the CPLD code is no longer free, its something ridiculous like $600 per year and I don't have that kind of money. So I was wondering if anybody else who is familiar with building the Jafar modchips, had come across these chips branded as SST49LF080A but with the slightly different device ID's, and had managed to make an updated CPLD code that would allow them to work? For reference, I've been using the 1MB_LPCmod_OSSupport_MosfetD0 from https://github.com/Team-Resurgent/Aladdin-Lattice It's a shame Lattice have made the software so expensive because I would have liked to have learned how to make my own code etc and would love to learn how these modchips work, so that one day I may be able to make meaningful contributions to projects myself. As for the one chip identified as 3B 3B - it doesn't even read, flash or erase in Xgecu Pro using the SST49LF080A profile, so that one must be some completely different chip altogether, unless it's just corrupted somehow and that's causing a false ID to be read?. As I say, I don't really fully understand how these things work yet - but I'd like to learn, just not sure where to start!

Hello guys, I tried to change large hard drive by use Chimp application, but show this error message. Could you help me? I am not sure what step is wrong. My process step as below: 1. Console turn-off, plug new hard drive power. (no connect IDE bus) 2.Console turn-on, my console already softmod by hotswapping 3.Run Chimp application 4.Take out DVD IDE bus and plug to new hard drive 5.I saw console show some message, should be OK 6.Go to dialog box, but show this message, "slave device can not be locked" And I check program function, slave device function is disable. By the way, before plug new hard drive, I format by FATXplorer. Any mistake of the procedure? Need you help! thanks so much!

Hi guys, I can confirm that this device works if you want to make a one to one clone of your XBOX Sata HDD: ORICO 6629US3-C-V1-US-BK USB3.0 to SATA Dual Bay External Hard Drive Docking Station I was able to successfully clone my my 1TB WD HDD for backup purposes: Cloned that with the same exact model. The actual amount of storage used was a little over 700 GB and took under 4 hours. Plugged the cloned HDD in and worked like a charm no issues. Great thing about it is the offline cloning function...so no need to connect it to your PC.

So my friend and I are trying to replace the front panel LEDs with RGB LEDs using a separate microcontroller. We were able to read the status from the current front panel so we can react to error codes properly, so it isn't just a "dumb" LED replacement with an external controller. Our next goal was to send commands over the SMBus to the Arduino (Nano, ATmega328P) we use to control the RGB LEDs. I customized the XBMC code to send data to the new address I defined for the Arduino, in our case we used 0xE9. Since the Wire library of the Arduino already shifts the bits, we set the Arduino's address to 0xE9 too. The thing is, the Xbox sends the signal, but the Arduino isn't reacting to the given address. We already tried to analyze the signal and we can confirm that there is data being sent through the SMBus. OFC we wired up SDA and SCL correctly, we checked twice and since the logic analyzer is able to sniff data, it should be correct. Has anyone ever tried this yet? I've seen a couple of threads talking about controlling Ambilight over the SMBus but it seems like nobody has tried it yet. I guess we are doing something wrong, but we haven't yet figured out what it is that we are missing. Next thing would be buying a proper logic analyzer, but maybe somebody here has some experience and could lead us in the right direction before we spend the money. Is there any more documentation on the SMBus of the Xbox out there? I've just found the documented stuff on the xboxdevwiki. Thanks in advance!