Jump to content
OGXbox.com

Leaderboard

Popular Content

Showing content with the highest reputation on 01/24/2021 in all areas

  1. Thanks to einsteinx2 over at ObscureGamers for upping original scene releases of some XDKs & recoveries, I've put those together with some other ones I've collected over the years, you can find them at https://mega.nz/#F!tL4HDI7J!FN6cLvccOSvXkomVrcyDhQ Collection includes: Still lots of XDKs that were released that are missing though, hopefully they'll show up one day
    1 point
  2. Cheers, got it done and flashed all ok. M7 bios will explain why I was having issues with a 1TB HDD.
    1 point
  3. Please don't take this project seriously, I know you are very dedicated to it, but health is very important in this pandemic period so look after yourself and your loved ones and be safe. There are many alternatives for all of us for xbox needs, so we can all wait patiently. Wish you a quick recovery.
    1 point
  4. If you wrote a BIOS version of 1.0.4627.X or lower to a 1.1-1.4 motherboard or a BIOS version of 1.0.4817.X or above to a 1.0 motherboard then the result would be a "coma console" because 1.0 and 1.1+ motherboards have a differing MCPX ROM and use a different encryption algorithm for decrypting 2BL into memory (1.1-1.4 boards also have an extra step in the bootchain) All official retail Microsoft BIOS' are 256KB so if you wrote a 1MB BIOS image and it wrote at least 256KB of the image to flash then that's technically okay but if you wrote a 1.0 image to a 1.1-1.4 revision or vise-versa then 2BL can't be decrypted properly and that's why your console is 'bricked'. You can recover the console by installing a modchip and I believe you can recover the TSOP as well but I'm not the one to answer how to go about that Quick rundown of critical failure states on the Xbox: Coma console: An error in 1BL or fatal hardware failure (CPU, NB (imbedded in GPU), SB (MCPX), RAM, SMC, or TSOP, and anything in between connecting those chips.. so basically anything) - no code to be able to signify an error to a user LED blinking: An error in 2BL (or FBL/2BL on 1.1+ revisions) or fatal hardware failure (RAM, GPU, or EEPROM) or something wrong with the kernel image - can blink LED's with code to write to SMC Error screen: An error in kernel or something wrong with higher level buses, devices, software, or basically any chip on the board not behaving correctly when the console is in a fully initialized state You're correct in saying BIOS' and kernels are usually separate things, the Xbox doesn't actually have a "BIOS" but that's what the modding scene labeled it as a long time ago - it's more so firmware. The Xbox "BIOS" is 2-3 separate blobs of code mushed together into a single chunk of data stuffed onto a flash chip (or ROM on 1.6) BIOS = 2BL + kernel or BIOS = FBL + 2BL + kernel (in the case of 1.1+ revisions)
    1 point
  5. Here you go again: https://1fichier.com/?wwqqkcorn4l3q2gwvrqt and https://1fichier.com/?9iwv01jyntve64q9t40d These are, more or less, two usorteret packs (i'm working on the clean out a bit) but it has banner for apps some homebrew, emulators covers icons what ever you can think of. hav3 fun (again).
    1 point

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.