peterpop
-
Posts
32 -
Joined
-
Last visited
Posts posted by peterpop
-
-
The kernel version is 1.0.4983.67
-
I'm watching this MrMario2011 video where he is installing exactly what I want to install (well the LPC PCB is different...): Aladdin XT Plut2 in a v1.6 Xbox. This is the first time I learn about even more pins to remove.
Pin 12 (which I don't have any data on), pin 4 (which is a no brainer), pin 6 (5V - why?) and pin 3.
Now, pin 3 is kind of interesting since I initially cut the L, but ran into problems so I restored it. Should I just remove that pin from the pin header?
-
Let me revive this old thread again... after a rather long hiatus I tried to see if I could get this modchip to work on this xbox.
I now know for a fact that the Aladdin modchip works, because I have tried it in another xbox (non v1.6)
I also replaced all the wiring with this https://github.com/Kekule-OXC/OXC_LPCorrectr/blob/master/LPC install v4.pdf - and also managed to wreck the lad2 pad in the process. Anyway I think I managed to get everything routed to the correct places using this as guide: https://www.ogxbox.com/forums/index.php?/topic/12168-lpc-repair/&do=findComment&comment=61059
I have tested for shorts between the pins and to the best of my abilities I don't have any. I also tried checking the resistance between the lad0:3 pins to ground: all ~10K Ohms (I don't know if its important, I don't know electrics)
I keep reading that D0 is not to be grounded on v1.6. I do have a loose wire connected to it to test with (the Kekule install guide also says to short it...). If I leave the wire be (unconnected) the Xbox starts TSOP BIOS when it is supposed to boot from the chip. If I hold the wire to ground it definitely tries to boot from LPC, but it keeps rebooting - the same as if I remove the chip and hold the wire to ground.
-
My goal is to take this xbox and make it a debug machine. But first I just wanted to know what was on it. Do I need a specific BIOS to make it a debug machine?
-
I just got hold of an Xbox with a RAM upgrade. Opening the machine reveals traces of a modchip. The LPC pin header is installed and theD0 has solder leftovers from what I can only guess is a wire to ground.
But as there is no modchip so the TSOP must have been flashed. The R7D1, R7D2 and R7D10 pads are also shorted.
Booting the box shows what appears to be the stock flubber animation. It stutters a little and just before ending shows Xecutor2 with white letters at the bottom.
Booting with no HDD gives this error message overview:
What am I looking at here?
-
I was too fast. I forgot to pull off the chip. It actually works now! How in the world can the upload order of two font files matter that much?
-
5 hours ago, Amethyst said:
Make sure ernie.xtf goes across before xbox.xtf
That seems kind of arbitrary...
Anyway I just copied all C and E files from a newly softmodded HDD (removing those two files and reuploading in the order you said), but it still goes black after flubber. I will try to get a hold of an older ATA drive and see if that makes a difference. I also notice that when I have tried booting without the chip, when I reconnect it I have to reattach the SSD or else it might not boot up.
-
2 hours ago, KaosEngineer said:
the OpenXenium modchip cannot be flashed using XBlastOS
That isn't my goal. Neither is it to flash the TSOP. I just want to get the info on the TSOP. And the only way I know right now is through XBlast. I just find it curious that even when I pull the modchip off the board, I can't properly softmod it.
-
I guess a way easier way is to copy C and E from another softmodded console and try to boot that... and the question now is, will it also go to black. I do have one more box to mod. I guess I can try with that one after I have softmodded it.
-
Title is weird I know. Let me explain.
Got an Xbox with faulty HDD.
Installed OpenXenium chip (D0 on MB to D0 on chip) with PrometheOS 1.5.0.
Installed 120GB SSD drive with a SATA/PATA adapter.
Formatted HDD in PrometheOS.
Copied evox dashboard and XBlast onto the console.
Can boot into dashboardThis is where I wanted to use XBlast to see if TSOP is writeable - but without writing to it. I know it doesn't matter with the stock BIOS. This is more a thing about trying random stuff for the fun of it.
I get the "No valid Flash device Detected!!!" and I immediately thinks its because the modchip is active and hides it. Am I correct in that assumption?
So my strategy now is to copy stock files over FTP from the TruHeXEn 2021 StockFiles/FactoryC and E, and pull off the modchip. This way the system should function EXACTLY like an unmodified XBox (only difference is the SATA SSD)
Booting works just fine. I can even play games. So it IS in fact a stock XBox right now running a stock BIOS and the stock Dashboard (I assume. I didn't put it on the HeXen image) from a locked hard drive.
Ok, so to read the TSOP info I need to be able to run XBlast. This requires a modded system. So I run the Endgame exploit from a USB drive. It goes all the way without problems. But when rebooting the final time, it just reboots to black. The flubber animation is there, but it's black afterwards.
If I reconnect the modchip and check the contents of the hard drive it looks like the exploit has placed all the files it should.
Am I trying something that is not supposed to work? The only things different from a completely stock system is:
1. The SATA SSD with adapter and 80 pin cable
2. The two solder bridges to enable TSOP writing
3. A wire soldered to D0 going to a disconnected modchip -
I stumbled upon this reply in another thread:
It explains a lot for me.
-
I'm simply curious. As I read and understand it the BIOS and kernel (in an unmodded vanilla MS Xbox) are both stored on the flash chip. To flash it with a custom bios I have to make it writable...
How did MS update the kernel then back in the day? The dash I can understand since it's just a file on the harddrive.
-
I have both a couple of openxenium and a stellar under way, so I get to try it I guess.
About usb softmod - I currently use the endgame exploit to softmod and then back up the disks. Using it puts the softmod on the harddrive. Is there a "live boot" like thing that boots the xbox into a tools menu instead where XBpartitioner can be run from, like a linux live cd that doesn't alter the harddrive?
-
Quick question:
Is it possible to just pop in a random HDD and format it on a hardmodded console?I have read that the Project Stellar chip have tools for it. Does cerbios (ChatGPT says so, but I have a hard time finding any information that verifies it)? Any other BIOS? Or does it require a modchip to have those kinds of capabilites?
It's simply to avoid the hassle of using FATxplorer in a virtual machine and avoiding stress on the DVD drive.
-
1 minute ago, Bowlsnapper said:
No. The softmod uses the MS bios on the TSOP. When you boot from the TSOP, THAT is what's available to flash. Same goes for the LPC. If you boot from one you cannot address the other. It is possible to boot from another chip and then hotswap them while you are in XBlast or any other piece of flashing software. However I am assuming that you don't have one...
Correct...
-
38 minutes ago, MadMartigan said:
I guess it could be possible that the chip on the Aladdin didn’t get a bios flashed to it. Have you attempted to check that with an external flasher?
No. I don't have one. Is there any way to flash it from a softmod?
-
1 minute ago, SakisTheDrifter said:
Thats because when you ground the d0, you tell the xbox to boot from the modchip and not the onboard bios
Yes, I figured that much out. It was simply to follow the guide KaosEngineer linked to to completion to rule that out.
But it doesn't change the fact that when the xbox tries to boot from the chip it'll frag. And I can't figure out why.
-
If I also do the step that says connect D0 to ground, I get a black screen and fragging with or without the chip.
-
10 hours ago, KaosEngineer said:
You should remove pin 4 from the pin header.
Check out this installation guide for the modchip:
circuit-board.de/forum/index.php/Attachment/72198-Aladdin-XT-installation-Guide-pdf/
The LED on the modchip only tells you that the modchip is powered.
That made a difference. Now when I turn on the xbox with the chip in, the led on the chip will flash a couple of times, and the the xbox will frag. If I remove the chip it boots from stock.
-
I've just tried to install the chip using this guide: https://consolemods.org/wiki/Xbox:Aladdin
More precisely I soldered the pin header and the 3.3V, LAD0, LAD1, LAD2 and LAD3. I made a blunder and ruined the trace by R7P4, so needed to reroute it. I would have routed through the hole at the chip pin, but the hole had solder in it that I haven't been able to remove, so I resorted to the hideous mess you can see on the picture. I have checked all the connections with a multimeter. There is 3.3 on pin9. LAD1-3) I have checked as much as I could by putting one of the multimeter probes on the tip of the pin and the other on a point on the trace that is not the solder point directly. In other words, I am reasonably sure that the soldering is "ok"
I also cut the L trace because the MrMario2011 video said so.
But when I booted only a black screen would show and FRAG. So I restored the L trace to be able to boot into stock BIOS.
Now I can only boot into stock. Am I missing something? Have I done something wrong? What can I check?
The chip lights red whenever power is plugged into the xbox. I noticed that if I put the chip in with the BT not soldered on the chip the led would dim slightly whenever the xbox was turned on. After I soldering it, it would not dim. Don't know if it means anything. Just mentioning it.
-
I have tried to research the connector. I think most refer to it as a JST (like you just did) 3-pin connector, but I think it's actually a PicoBlade 3-pin with 1.25mm pitch. Like this one: https://www.ebay.com/itm/134886687394
The red/green/gray could be bought years ago: https://web.archive.org/web/20111210215747/http://secure.llamma.com/catalog/xecuter-26-x3-d0-red-gray-green-wire-bundle-with-connector-p-488.html
Another question: On the Xapt3r there is a wire going to D0. I have read somewhere that that is used to tell the system to read the bios onboard or via lpc. Do you know if when the D0 is connected from the Xapt3r instead of from the chip board means that the bios on the mod chip is always used. I don't know anything about the X3 but I would guess that it's user configurable whether the Xbox should use onboard or modchip bios.
-
I think I got lucky. I was looking for an Xbox below 1.6 to do a RAM upgrade on. I found one with the X3 front switch panel for the same price as any old Xbox without it. Just got it and it turns on. The chip turned out to be the newer CE version. But it's installed with the Xapt3r adapter. In https://command-tab.com/static/x3_ce_v10_v16.pdf there is an image of the standard kit:
The parts that came with this Xbox are 1, 2, 3, 4 and 7. If I want to solder it I will need 9 also. That I can make myself from one of the scrap headers I have. But what is 8 and 10? My guess is that 10 is irrelevant. Is 8 for some drive activity led flashing? Is it available to buy somewhere?
-
On 2/26/2024 at 9:18 AM, Bowlsnapper said:
The "Name" is what shows up at the bottom of the screen when selecting the bios manually in xblastOS, I am not sure where this name is stored, but I think it will show up in XBlast if ever run as an XBE on your system. So just type in "Cerbios" for the name.
0.56 is the one that is on the kit and that is plenty sufficient. You should not have an issue. Go ahead and flash. Once you do, make sure that the Cerbios HDD files/folders are on C so that you can have your ini and boot animations.
Did you select an appropriate UDMA mode as outlined in the Cerbios thread OP?
Well, I asked Discord and because I don't have the SATA adapters yet, I just chose the hybrid one. It works flawlessly. I did run into some problems right after flashing where I booted to a black screen. Popping in the tools cd (to get ftp access) and clearing out the C drive solved it. I guess it's something to do with shadowc (which I don't really know how works/what is). But it's working now.
So I have moved on to the first xbox, and I actually noticed a patch of dust around the capacitor. I can't see anything on the cap itself. Anyway, the cap is removed, I cleaned the area and the box boots fine. So now it's on to modding that one too.
-
5 hours ago, MadMartigan said:
@Bowlsnapperhas you linked to the goods. If it gets to be too overwhelming(it’s a lot to take in), you can reach out to one of us in DMs or on discord if you have it. I don’t mind walking you through it all. It’s really a simple process after the learning curve.
It IS a lot to take in. But when you're not in a hurry and can take your time reading up on stuff it's a lot of fun. I'm learning all sorts of new stuff. E.g. I didn't know that ATA drives had built in security. I thought it was MS specific to the XBox.
Finding the right ressources is quite the adventure.
6 hours ago, Bowlsnapper said:Use the TSOP flashing tool. In the OP I explain how I use the tool to flash the latest version of Cerbios.
Edit: You can use the "Xblast Only" version near the bottom which will make this MUCH simpler for you. Just run the exploit and it will immediately run XBlast. Then you can net flash Cerbios from your PC over the network.
As for the latest version of Cerbios:
That is the one we're all using these days.
If I go to the XBlast-only links the first one links to an NTSC version. I never really said that I'm on a PAL system, sorry
. And the second one (from Dark Destiny) has two dead links.
So I used the 1fichier one and downloaded OGXBox XBlastOS MC TSOP Flasher v2.1.0 8MB BASIC (07.12.2023).rar, extracted until I reached "OGXBox XBlastOS MC TSOP Flasher v2.1.0 8MB BASIC\Flasher\21585554\000000000000\XBlast\XBlastE\XBlast". Ftped that folder over and started default.xbe from there.
I just need to be sure that that is the correct version. On my screen I see this:
The web form (when started of course) asks for the bios file, but also for a name. What is the name used for? Can I write anything there?
Board Life Status
Board startup date: April 23, 2017 12:45:48
The "Easy XDK Installer"
in Installation Disks
Posted
The big warning signs are used about the recovery tool bricking the xbox. Is the danger the same if using a modchip like openXenium with PrometheOS? Wouldn't it just be a matter of flashing another kernel over it? I can see the problem if booting from the TSOP.