Donnie-Burger
-
Posts
317 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Calendar
Store
Posts posted by Donnie-Burger
-
-
https://electron-shepherd.com/xbox2hdmi/
These are crap! Not worth bothering with and i doubt very much that the Cerbios team will ever add any kind of support for it.
Not sure what you were talking about then. They look clean on 1.4s and up and for $30 and can use on multiple systems, cant beat that. I ordered a cheap ebay to compare and have 2 x make Mhz on order of each flavor.
Been loving Cerbios lately and if someone can ad UDMA5 its over.
-
1
-
-
45 minutes ago, nikeymikey said:
These are crap! Not worth bothering with and i doubt very much that the Cerbios team will ever add any kind of support for it.
Fingers crossed that Cerbios will be the bios to beat them all, all the latest and greatest features in one place. I hope they will add the MakeMhz patches and all the goodies from the Titan patches too!
EDIT: Little sidenote for those of you that didnt already know it. Xboxs have been able to play iso files for ages already, those handful of games that wont play when extracted have played fine as an iso. Cerbios just makes it easier as you dont need to use an attach.xbe anymore.
I will probably convert my full xbox set back to iso once i have a box setup with Cerbios and a huuuuuuuge HDD. Iso files are better for the cluster sizes. Extracted games on a 512k cluster (which i believe is needed for 8tb support) will be a huge waste of space as all those 100's of tiny few kb files will all take 512k each!!!
I have XBOX2HDMi and they are very nice and work with any bios I have tried, cerbios, titan and M8, IND, TX. Only issue on 1.0 Xboxes and there is a fix. I need more thats why I ask. They are the next best thing to the Make MHZ hdmi hd+.
I'm converting all my collection to ISO and I am 25% done.
-
20 hours ago, Onaga said:
okay, I check the modem again and give a feedback soon! Thank's for all the help so far!
You can also use fatxplorer and never ftp ever again. Its way faster just need to hook up your drive. Good luck bud.
-
1 hour ago, KaosEngineer said:
Have you tried to use Gentoox Loader
or XBlast OSto reflash the rebadged SST49LF002A part?Edit: Wait, XBlast OS not being able to reflash the modchip is the whole reason why this thread was started.
P.S. I wonder if some of the Linux-based flashing discs can reflash it (e.g., eurasia_pro_generic_flash_disc_1_3)?
It uses a program named raincoat to flash a BIOS to the modchip/TSOP.
I'll take a look.
-
12 minutes ago, KaosEngineer said:
Thanks for the clarification. Therefore, it is a problem with the relabeled/rebadged SST49LF002A (MFG ID: BF Device ID: 57) showing it to be an SST49LF020A that is causing the problem.
Now I wonder if some of the earlier Aladdin XT Plus 2 modchips that have a different printed circuit board layout than the one you currently have has different CPLD programming to allow the SST49LF002A to be reflashed.
Why I'm wondering that possible CPLD code difference is because the SST49LF002A has been listed in evox.ini's Flash= llnes for a long time of devices I thought it could flash:
- Flash = 0xbf57,"SST 49LF002A",0x40000
as are the SST49LF020 and SST49LF020A devices:
- Flash = 0xbf61,"SST 49LF020 (Matrix)",0x40000
- Flash = 0xbf52,"SST 49LF020A",0x40000
Although, so have many Winbond W49F0XXX devices which cannot be reflashed by evoxdash:
- Flash = 0xda0b,"Winbond W49F002U",0x40000
- Flash = 0xda8c,"Winbond W49F020",0x40000
and this wrong entry for a Winbond W49F020T
- #Flash = 0x9000,"Winbond W49F020T",0x40000
commented out (the first character of the line is a # character) of the evox.ini file I saw it in. I think they were trying to make the Winbond TSOP show it was not flashable reading the first two bytes of the BIOS 0x0900, not x9000. Someone goofed?
Like this line too which is wrong when the TSOP flash chip on the motherboard has not been write enabled:
- Flash = 0x9000,"Chip not writeable",0x40000
It should read:
- Flash = 0x0900,"Chip not writeable",0x40000
Interesting, thank you for the info. Glad we can flash these now to not have to worry about what we get when ordered. Nano usb on order.
-
3 hours ago, KaosEngineer said:
Ok, so both flash memory chips can be flashed in the working modchip.
For 33-4c-NHE designation, the Environmental suffix “E” denotes non-Pb solder. RoHS compliant part.
If you use Evoxdash to flash the two different flash memory chips in the working modchip, do they show two different device IDs?
Manufacturer ID for SST devices = BF
Real SST49LF020A Device ID = 52
And, the SST49LF002A(rebadged/labeled as an SST49LF020A from the non-working modchip) Device ID = 57.
Moving chip around has same result, can only flash Real SST49LF020A Device ID = 52. I will order a Nano usb programmer. Thanks to both of you guys.
-
17 minutes ago, KaosEngineer said:
Do all of the visible traces on the front and back of the two modchips look exactly the same?
Are there any differences however slight?
I can swap chips and they work the same - The flashable one is flashable and the non flashable one is non flashable no matter how I swap or hotswap with xbox / chip. I'll double check but they look the same.
With my current batch :
33-4c-nh Flashable
33-4c-nhe Not Flashable -
On the left is the flash-able version, on the right is the clone non-flashable. I tired many methods with hot swapping and its a no go. I'm open to any ideas.
If you figure out how to flash the clones (Nano USB flasher or an y method) and can boot successfully please share. Thank you.
-
On 4/30/2022 at 4:18 PM, MadMartigan said:
All part of my reasoning for a pinned topic. Tons of great info here.
On the left is the flash-able version, on the right is the clone non-flashable. I tired many methods with hot swapping and its a no go.
-
37 minutes ago, mmx_in_orbit said:
So I have this 1.0 OGXbox and it has been FRAG'ing since coming out from being locked away in storage for a several years. I remember it working fine last time I used it. It tries to boot three times and then FRAG's 50/50 fast, does not output video, and does not output audio. I have noticed that when I press the eject button that the hard drive makes some sounds like as if it's working maybe and also the noise of the fan/fans gets louder or higher in pitch (not sure), but the FRAG'ing continues and still doesn't output video/audio. I noticed is (while having the Xbox connected to an ethernet switch) that when I press the eject button the ethernet link LED comes on for about a second or two, then goes out for about five seconds, and then comes back on and stays on. I also see the ethernet activity LED blink a seemingly healthy amount too. I'm thinking the problem is one or more of the following: EEPROM, TSOP, PSU, trace rot, maybe big shield (mildly/moderately rusted) that the motherboard sits in is not making contact with required connections on the bottom of motherboard, one or more capacitors on the motherboard possibly need replacing.
I'm kind of hesitant about putting a modchip in as I'm not sure if it may get damaged/destroyed by this particular Xbox (I have an OpenXenium on hand).
Open Xbox and remove clock capacitor and clean up around that area as best and as gently as possible with ipa 91%+. Dry area before testing with compressed air. Clean up av port with some ipa and q-tip/cotton swab and then dry with compressed air etc. Check underside of motherboard for trace corrosion on point A,B,C,D.
-
6 minutes ago, MadMartigan said:
That would be Dustin from MakeMHz. You can ask in the discord https://discord.gg/knj3Qfb6
I was referring to this one:
-
1 hour ago, RunsilenT said:
Trying to rescue a 1.6 box. The unit booted to microsoft dash but dvd rom drive has failed, tried cleaning and pot adjustment, no luck. Next obvious option was installing a modchip.Installed an Aladdin XT plus I had working in another 1.6 as was already flashed. On boot I get the unit cycle on and off until the third attempt where it flashes Green and red really fast. I removed the lpc wiring and modchip, even pinheader, checked for damage, the header is perfect and the xbox boots normally. I have never had an issue like this before. Do I just keep trying to install again or am i missing something. Does the 3 boot attempts mean something? I am unsure to the sequence of events from pressing the power button. Any pointers, help would be appreciated. Just dont want to throw it out. Update, the green / red fragging is not modchip related and happens intermittently when running the box without a modchip. Progressively worse the more boot resets.
Have you tried grounding D0?
-
5 minutes ago, Hydr0Reaper666 said:
I actually own 2 of these modded xboxes but one needs a new bios it wont boot into flashme and the other works fine i just gotta find myself a controller and ill be playing again
..
I'll buy the broken one off of you
-
2 hours ago, Yoinx said:
The harddrive is a Maxto 4A250J0, which i'm just realizing is an old 5400rpm drive... so I can't expect much out of it. It's not locked. There's no adapter, and it's just the OEM ribbon cable. (Partition Layout attached)
I ended up deleting the XBMC-Emustation folder and copying it back over via FTP and just putting 1 NES rom into the roms folder on 'E' and letting it scan. The menu does come up a lot faster like that, around 3-4 seconds. The gameslist.xml was only 2kb though, so that's not so surprising. It might just be an issue with a slow hard-drive. Though, I thought that the XBOX only gets like 10MB/s through its IDE controller anyway so I wouldn't have expected it to be *that* slow off of a slow drive.
I went ahead and rescanned them all back in and the gamelist.xml is around 47kb for that system (NES) and it's back to ~25 seconds for the game list menu to open in the basic view. I know that the list has to be processed and all that, but I can't imagine that the hard-drive speed would have that huge of an effect for a 47kb list to be read off of it. Is it trying to validate that everything exists as it processes the list or something (this would make sense for hdd seek speeds and such to slow it down)? Is there a way to disable that so that it just shows the list without validation? Obviously, if something doesn't exist anymore since the games were scanned this could cause a crash... But I'd rather that being a problem and the list opening quickly.
I have fast game parsing on per your previous suggestion.
It could be your old drive. I always format evenly cause I get corruption after 50% filled if I don't. I always go back into XBpartitioner and make sure both cluster sizes show for each drive with no graphic glitching. This always works. Have any spare drives to rule that one out? You can also try fatxplorer and copy something to the drive. If its super slow or slower than normal then its the drive.
-
1
-
-
1 hour ago, Yoinx said:
That's probably where I'm going wrong. I put the roms on f and put the media on g. Emustation is on E
I'm only using a 250gb hdd, with the f/g partitions around 115gb each. If they shouldn't go on e/f/g where *should* I put them for better results?
Or should I have made an extra partition with like 10-20gb to store them?
Just follow what he said as thats how mine is and smooth as organic butter.
put up:
hard drive
addapter
cable
models
-
5 minutes ago, Squashed said:
I'm not sure how to check which X2 bios it has. I'm assuming its old based on the outdated EvoX V 3921. It says Bios version unknown but the Kernel is 1.00.4980.06.
Try Xblast Os.
-
44 minutes ago, Yoinx said:
So I've gotten my Xbox all setup and am using xbmc-emustation. Which is amazing. However, it seems like my game list menus are a lot slower than any of the YouTube videos I've watched. The videos look like it takes a second or two for the games lists to come up, but mine is more like 30-40 seconds. When exiting a rom (with the option to return to the list enabled) it only stays on the black screen for a second or two then displays the list.
Is it normal for it to hang for 30+ when loading the list from the carousel? I can still hear the button press noises it you press them.
I'm on the latest version as far as any update checking tells me... It scanned everything fine. And the lists look/work fine once they open.
Thanks in advance for and help.
The more you have on the HDD the slower it gets. Do you have fast game parsing on? settings/programs/advanced.
-
1
-
-
19 minutes ago, Playa-V said:
Yes, that's the point. But no one is telling me how much it's worth
Put up some pictures for assessment.
-
1
-
-
1 hour ago, MarkC1970 said:
I have just taken the heatsink of a v1.0, cleaned it up and replaced with MX4. It seem to work OK but the heat sink is not clamped to the CPU at all well. I can rotate it with no trouble and even rock it side to side. Were the original thermal pads adhesive? Were they 1mm thick and I need to now pack the clamp out? Any thoughts? Thanks.
Gpu can slightly move when clamped. CPU should be pretty tight clamped down even with arctic mx 2/4.
-
18 minutes ago, Bowlsnapper said:
Looking for X3 chips, Control Panels, etc. Plus, if itˋs new in the package and unopened.
If the planets align, that is.
Good luck my friend.
-
21 hours ago, Playa-V said:
I didnt find a price check thread and wasnt sure where to post this. But wanted to ask how much would this go for?
V1.0 Xbox with X3CE + X3CP front panel + 200GB HDD
Or you can sell to me instead
-
1 hour ago, Squashed said:
I just wanted to share what I think may be a beauty of a find. The Ebay listing had it going for parts only but I'm cheap and had a good feeling about it. As far as I can tell other than it starting up as soon as it's plugged in it is 100% functional. The listing said that it had trouble reading disks and spits them out randomly. I have yet to experience or replicate this behavior(I played and ripped two games from the DVD drive). I was expecting a broken stock machine but as soon as I cracked it open I saw a 160GB Seagate HD. Once I pulled out the drives I noticed that it had in fact been hard modded. It's date of manufacture is December of 2001 so it has to be a 1.0 right? Why would someone sell a gem like this for so little? I'm quite new to all of this but other than the slightly janky wiring and outdated version of Xecuter am I wrong to feel stoked about this one? Anything I should be wary of? I went into this expecting to at least have to recap the board but it seems that that may not be necessary.
Customers always gift me these consoles. Have got free Xecuter chips and other various rare gems for free. Have over 10 left I'm going through them to find 1.4s for 1.4ghz cpu install candidates. Good find though.
-
Practicing on spare boards while I wait for all the parts to come in. Found a stencil that almost lined up perfect.
-
3
-
-
3 minutes ago, Eaton said:
I'm not the one to ask, I don't make/sell that product.
Oh shoot my bad.
Board Life Status
Board startup date: April 23, 2017 12:45:48
Cerbios new xbox bios
in Bios
Posted
Yeah but no 128MB support. Gotta pick one or the other and UDMA5 is real nice honestly.
Waiting for Cerbios to get UDMA5 or
Titan to get 128MB support
Really liking xiso and I dont think they run on Titan. Tested 1 game and rebooted back into XBMC4GAMERS.