BlackZpider

Does someone have any idea what this could be? MFG 2008-07, not a Service Date tag. It has 16.5A printed on the same label, and on the label above the powerport. It has no HDMI. It has a Zephyr GPU heatsink. It has edge glued CPU and GPU. It has the Xenon power connector. It has a BenQ DVD rom MFG 08. It has no 256/512MB internal memory. Chassie stamped 05. Had no warranty reflective sticker under the faceplate more than the silver Microsoft strip, that I have cut to open the console. LAN and AV port has some stickers residue and markings. I can't get this console information to match anything that I know about Xbox 360. It seems like a Serviced 2005 with MFG 2008 tag, 08 BenQ and newer MB that has the old Xenon fanpower connector and no HDMI, like an OPUS?,, but then, why 16.5A tag and power connector? Can anyone who has more knowledge than me shed some light over this strange mix?

Hi again. I came over an Xbox 360 from 2006, complete in original box. But when I opened it I got confused by the motherboard. At first I thought it was another Opus, but it did not match. The motherboard is an Xenon motherboard, no doubt,, But, with glued Canada CPU and glued GPU as an Zephyr/Falcon. It has the Zephyr GPU extended heatsink and the older copperpipe CPU heatsink, but no extra Dram coolerpads. But there is no "Serviced 20xx-xx-xx" label on top of the original "MF date, Serial Number" label on the back. It is the original 2006 label. Is it just so simple that is an very very early repaired console who got a new Canada CPU and GPU with the Zephyr/Falcon style glued edges? My RGH'd Halo 3 Edition Zephyr has an "Serviced 2010-xx-xx" label on the back over the original MF date 2007 label. I did not think about taking pictures of it when I had it apart, cleaned it up and made an RGH 1.2 of it, but it is the same style as the picture I uploaded on the Canada CPU. I don't believe it's any "Mysterious Prototype MB" or anything like that 🙂 I just never seen any of my Xenon's with this kind of Xenon MB, glued GPU and Canada CPU mixture, except the ones I have with an Opus MB which just is an Falcon without HDMI, so I wonder if anyone here has seen it during their years with Xbox 360?

Sorry, have'nt been online for some time,, has been too nice weather outside :) But if I have a nand read out, like from my original 2006 console, that is on dash 5xxx something, I don't remember exactly which 5xxx dash right now,, would'nt there be a way to either put the information needed, cpukey etc into that one and use, since it don't use that encrypted secondary cpu key on those older dash,, or put the information needed into that nand copy and get it to boot on the system as Jtag'ed? Or would it have to be the exact same dash version that was on it when it was Jtag'ed for all the checks to pass? But then,, since the Jtag makes the console OK every check anyway,, should it not be possible to use that 5xxx nand backup file in any way to use on this 2005 Jtag'ed MB? Since it could boot the 9199 without problem.

But still, wouldn't there be a way to put the 6717 dash files in a 9199 Jtag build? Isn't all the CB-CD-CE-CF-CG different checks before the boot process? Or does it some way interact with the dashfiles during the boot process? Or does it interact with the SMC config somehow who then checks the dashfiles, or what is it that prevents the 6717 dashfiles to be booted?

Is 1888.fsroot.bin equal to the data.bin in the extracted 6717?

I used Horizon, just drag'n drop and extract,,, but no boot. "This game could not start", so it wasn't just that easy removed the $flash_ in the filenames incase that had something to to with it,, but nope. The 1888 dash has some 1888something.bin file in it's folder,, it booted on my Japer with 17526,, but crashed when I scrolled through the Console Settings, as fast as I scroll past Language tab it freezes and crashes, that doesn't happen on the 9199. Forgot to mention that I tried the 6717 on the Jasper too,, but no go

So the hacked 1888 is just for hacked to boot on RGH on higher dashboards? You mean that I can extract teh 6717 SU and run it from the 9199 on the Jtag? I found another Xenon and zephyr board in the parts shelf I forgotten about, both with some reballing to make,, but unfortunatly the Xenon ran on an lover 16xxx dash and the Zephyr ran on the 8955, but gonna reball them anyways, don't understand why Zephyrs are so unliked, my Halo 3 Ed. Zephyr insta or two cycles boots almost everytime with RGH2 and runs as cool as any Falcon I have. Well, back to topic I'm going to try the extracted 6717 on the Xenon, see what happens,, if it'll blow up and make a new hole for a window in the wall or if it'll work.

The 1888 dash boted on one of my RGH to, dash,, 14xxx,, I don't remember, was over a year ago. But even so the 9199 just freezes,, thought I'd try it just for the fun od it,, but not even that would boot properly. Edit: I suspected that there was some flaw with the J-runner so I tried another copy of it, so now the console boot 9199 without problems,, tried the 1888 hacked dash, it seems to work better with the 9199, but still some windows opens as 9199 UI. So it's about 70% of what I'm after,,, but still would prefer if there was a way to get the raw 6717 dash into the nand. Saw another forum where they discussed how to get the 9199 to boot from an RGH1 console, they managed it after some work, so I suppose it's the same with the 6717 on a Jtag, it should be possible somehow.

Well, yes, as you pointed out Felida, I mentioned that this is a Xenon, from very early 2005, and the fuseset point to that it has been Jtag in a very early state with a dash in the 4xxx range, so there should be no problems with fuseset's or such hardware things. It evem says on a sticker on the MoBo, "X805954-001 Kernel 1888" But I solved the Xell not booting, seems like I have to reball the membricks to, made a temporary fix for the moment, until I can get this sorted if the board can get the -6717 booting. I think one problem can be that there was no Bin files folder to the 6717 J-runner dash I made, so I just copied the bin folder from 7371, and I don't think those two probably goes hand in hand. I'm totally lost when it comes to coding and how those kind of files works, Bin, Patch, BL and so on, I'm more of the practical type of guy, solder, hardware and such, so that's why these things that's obvious to those who has the knowledge of files is like an alien language to me. But theoreticly I can add one plus one that 7371 Bin files would be a No Go, to blend with the 6717 dash files So I don't think I've made an correct nand image that would boot,,, on any console,, what so ever. But the Xell boots fine now, so I have tried to flash some different dashes, 9199 that boots but freezes at the Bootanim everytime,, a 12xxx, boots fine, a 13xxx series that boots fine, another 17511 that boots fine,, a 7371 that don't boot, only green flashing,, no RRoD, and the 6717,, probably made up of wrong files that don't boot, just green flashing, no RRoD. But now the problem is to find/get a hold on some bin files for the 6717,, if it's even needed, so anyone with more brains than me in that area are more then welcome with any info regarding bin files, are they neccesary for a Jtag nand? What do they do? What I've red is that a Jtag console would boot "any" dash, so wouldn't that theoreticly mean that it is be possible to boot even a 1888, 2xxx, 3xxx, 4xxx dash to, since it doesn't "care" what it's booting as long that it gets all the right commands in the boot process?

Well, I've tried to make a new image, extracted 6717, crc32 checked every file, put it in a new folder and made the _jtag.ini file with the dashfiles and crc32 checksums, now it appears in j-runner, it was no problem making a new nand but it doesn't boot with it, neighter does xell,, it just flashes green,, (no dvd drive connected yet), but doesn't christmastree me or anything like that. I tried to make a new nand with the donornand tut, I can create one, flash it, boot to xell,, I used it and made a nand from my old kv.bin etc,, made a new nand with 6717 dash, but still the same with that one, just stays flashing green,, no boot, no christmas-tree,, it only flashes very angry (Put the f,, cable back!!) full red ring when I pull the AV cable out but quickly turns to a friendly green flashing again when I put the AV cable back,, thats the only RR it will make. Can it depend on any LDV settings or such? From xell I red the fuse set and this cpu is on,, fuseset 02: 0f00000000000000 fuseset 07: f000000000000000 That would mean an very early dash and LDV 1. I choosed LDV 1 when I made the first nand from the donornand tut,,, buuut the other original NAND info values info in Jrunner is as following: 2BL [CB] 1921 LDV 0 PD 0x000000 4BL [CD] 1921 5BL [CE] 1888 6BL [CF] Patch 0 4532 7BL [CG] Patch 0 4532 LDV 0 PD 0x000000 Can you see anything that doesn't blend well togheter out of this info? The console only boots to xell now with a donornand made image,, but not with the 12611 jtag img that was on it when I got it,, well, it didn't boot with that image then either, but I made an 17526 image from that nand, and that booted the console right up,, but if I try to do it now, it just flashes green. It's like it sits there and just wait for something.

So if I get the Su extracted, then find the CRC32 sums and create a jtag.ini by copying it from 9199 then add the filenames from the extracted Su and the CRC32 checksums under [flashfs] and dash version under [version] , ,, put it in a folder i J-runner and create a new img file from that? Or do I have to edit any other files in J-runner for it to find it? I just tried to make a 9199 img in J-runner just to see if it was possible since it was in the list and had the _jtag.ini file, but every dashfile CRC32 checksum was wrong,, even though it was a original 9199 Su file in the folder in Xebuild. Why would that happen? Different rev Su to what was used in J-runner at that time? I tried that 1888 dash, it worked but I had to downgrade to around 14.xxx for it to not crash,, but still, if you try to use any special functions it just redirects you to the 14.xxx dash systems musicplayer, some of the settings etc. I had it as the default dash through DL3.18, but after redirecting to the 14.xxx dash in settings and such, it went to the 14.xxx dash when you backed out again, no fun. Well fun and fun, not the right word, but more non-"authentic".

Thanks That was the information I hoped for. I know it's going to be quite useless, unless I would like to relive the memories of playing the first Saints Row again,, but so are painting, just hangs on a wall for you to look at,, but that is my goal with this old console, it's from 03/2005 so it is in a way just like piece of history to sit there among all the other consoles on the shelf,, and when powered on,, well well there's the old blade from that time. Otherwise if it would boot to 17526 it would be like putting on a pair of sun-glasses and a beer in the hand of Mona-Lisa, it just wouldn't be quite right. But now, how would I go about to make a Jtag image with that SU update file? I have the rawkv, rawconfig and all that from the image that was on the console. I know J-runner surely won't help me make one, since it doesn't go lower than 7371, and does not even has the _jtag.ini for that dash. I've tried to use my other 2006 original blade dash consoles nand as a donor, patched the rawkv, rawconfig with nandpro, and draged it through JtagTools to XBR it, but that didn't work.

As I wrote earlier, I know about the hacked 1888 Dash on Jtag/RGH consoles, had that on one of my 360 a year ago as bootdash, but as I explained, you can't use any functions on it, it launches the NXE dash music/mediaplayer, settings and so on, and familysettings made the 360 crach and boot to stock NXE/Metro dash,, it's a good idea, but that's not what I'm after. I looking for a way to restore it to a Blade dash nand,, Jtagged motherboard or not,, does not matter to me. I don't need dashlaunch, don't need xex menu or anything like that. just that it runs a Blade dash nand image,, not an freeboot NXE or Metro. It should be possible as one forum from late 2009 explained, since it is an early exploitable kernel, not e-fused burned beyond Blade dash, and since it is such an early dash it din't have that dual cpukey whereas one is hidden and can't be used to encrypt a new retail nand to pass the security check on a retail console,,, as I understood it,, but all the links to the "How to do it" on every forum or thread that had some discussions about it is dead since many years.

No, I have 16 other xbox if it was just listening to music I was after,, but this is if, and in if so, how to revert this revived xenon back to an old <-5659 Blade dash nand. Either retail,, or hacked and leave the Jtag wires in. I've red in some old posts dating back to 2009-10 that it should be possible, but no further information regarding how, or links dead.

If that would be possible I could live with that, I'm not that fuzzy that three short wires and two diods are on the motherboard, as long as it boots up on the 4xxx-5xxx Dash, but haven't found any info that it would be possible., the only info I've found is that 7371 is the lowest dash to make a new upflash.bin from. Can't find anything that there exists lower Dash builds :/ When running the hacked Blade on a Jtag or RGH, you can't use the original music/mediaplayer or setting, they redirect to the NXE style music/mediaplayer and setting, and that is not "stock-like" enough so to say. I know that there are a lot of people that can't understand why anyone wants a xbox with Blade dash more than to flicker trough the tabs for a couple of minutes and then get tired of it since you can't do anymore with it, but I'm just one of those few who can have that Blade dash glowing up my tv-screen for hours. Bought my first Xbox 360 2006 after my house burned down to the ground, so that Blade Dash has a lot of memoiries for me after all the nights I spent with it the following year just to relax and ease my mind.