Ikari's Freeboot v0.03 is Out -- 9199 JTAG

From XBH and XS:

http://www.megaupload.com/?d=ERBD9C4X

http://www.sendspace.com/file/5197x5

-hl718

 

Update: Freeboot v0.031 released!

The "keyvault and console signature checks have been disabled" feature has been removed!

Here's the DL - link:http://www.megaupload.com/?d=5TDX1QJZ

 

Early reports are that there are still a few security checks to be worked out.

Some profiles are not working and the unlocked Xbox emulator fails on Freeboot 9199.

-hl718

 

Also its not noob friendly and I cant use it as of no org nand or LDV values.

 

Well I just tried this to make a video for youtube, all the building ect went fine but the console reboots and displays E79. Others have had this issue as well, needless to say the video's production is um pushed back until further notice. I've tried it multiple times and still the same result. I've used 360flash, nandpro, xellous, to flash the new image produced from ibuild and the same result everytime. All original nand dump, builds fine, just doesn't boot.

Hawk

 

For the people wondering why the readme asks you to update the console to 7371 prior to attempt installing freebot:


It uses the SECURITY backbone files from the original image:

crl.bin (Console Revocation List)
odd.bin (Optical Disc Drive statistics and security report data)
secdata.bin (main SECurity DATA logs)
extended.bin (Extended keyvault)

And their respective metadata (date/hour of last update on flash directory tree)

Along with the main keyvault/certificates storage (kv.bin) and persistent system settings such as DVD player region, mac address and video system (smc_config).

"- keyvault and console signature checks have been disabled (Bliep4Ever)" This means you can hexedit (for game region change, yay) hashed keyvaults now. (Zephyr and newer or serviced Xenon units with CB1920+)


Because Freeboot aims is to create the closes possible set from a original image, it uses the files from the original dump. because this stuff been source for a lot of whining at X-S, I decided to make this post.

While I know we have a more mature public here I am sure some people would still wonder why Freeboot has such requirements. Also I used files from pre NXE dash on my odd fuseset FALCON console :



This console obviously cannot be updated to 7371 due to that "loose" 1 at end of fuses row 07. It won't boot anything but an zero-paired image.

 

How the hell did you manage to burn an odd fuse like that?

Were you experimenting with the hardware?

Or was this a broken system that you fixed up and got working?

That's an impressive glitch.

-hl718

 

It's a system I was given for free. Considering that it's original flash image seems to be corrupted, I suppose it glitched while updating.

The guy wanted to reball the GPU (which obviously would not change anything on this case) but then eventually gave up on it, sending the unit to me.

With it here I dumped it's flash and determined the CB to be of the exploitable type, I thought "hell why not" and flashed XeLL in it. Here we are, lol.

I posted that glitch on XBH but people didn't seem much interested on this kind of stuff... (which I find sad as investigating faults on machines is one of the things I find most exciting on electronics)

 

Not to get too off-topic, but that's the sort of thing that I wish more people would chime in on as that sort of thing isn't supposed to happen. I'm sure there's a QA engineer somewhere at Microsoft that would love to get their hands on it.

I'd suggest making a new topic, but I don't know enough about the hardware at that low a level to even know where to start looking. My best guess would be what you said, a random glitch (power perhaps) during a failed update.

-hl718

 

Ok I got mine working. do everything exactly like the instructions say to, the difference is that you get your smc.bin from your xbr image. Use flash tool .92 to open and extract your smc. make sure to use the smc_dec.bin rename it to smc.bin, put it in the data folder, should boot right up. I did this and used flash360 to flash it, I wasn't expecting much but it worked on my Falcon, not sure if I'm going to do it on my jasper yet.

Hawk

 

lol flash failed, man now i got to dig up my old a** LPT cable to reflash the system back to xellous and reflash xbr XD

 

There seems to be some issues with E79 with this freeboot. The topic title in #Freeboot says to wait for a new version, to fix these issues.

 

Yeah but if you would use the smc bin from your XBR console it should work, at least mine did.

Hawk

 

0.032 was released

 

Damn it. Well off to figure this on out.

Edit, Worked first try, I used the same smc bin from my XBR console, went smooth did not hve any porblems, however flash360 was showing something about zero paired images and warnings about this and that, I said oh well and just flashed it, it booted right up no probs. The one things that I'm glad is working in freeboot is the clock stays set when you turn the console off, also full memory editing is possible? Haven't messed with that at all, but it's in there.

Hawk

 

I'm still trying to figure out what is wrong with my setup. I get power but no boot and no 3RL. :shrug:

 

Your smc, use the smc from your xbr console.

 

~BLEEP~
WRONG !


I was using the right SMC. I was naming the generated image "freeboot.bin" which in turn was replacing the file "freeboot.bin" which is the rebooter core. (rofl-lmao :lol

Turns out that once I changed the command to name the output image as something different, things went dandy.

 

I think this is where RTFM is appropriate.

If you use the commands exactly as written in the readme, it's all good.

(Don't worry though, we've all pulled similar "doh" moments in the past.)

Glad you got it working.

-hl718

 

A question for anyone running the new freeboot.

If you have any 360 debug games that did not work with xbr3 do they work with freebot now.