Hi all

New version of this is a new version of easy Freeboot with the ability to "Auto Jtag" the console, along with a few bug fixes, and a little re-skin.



Origernal se7ensins thread

Thanks for looking

Peanut

Can we use current nand image to create the updated image? Or must we use 9199 or below?

u can use the current nand image

Thank you sir! Pretty slick program! Will have to try out the jtag my xbox when I get a new one in.

"Cpukey grab (experimental)"

How does that work exactly?

Will this tool allow you to upgrade a previously JTAG'd unit to the latest modified dash? I have a unit that has a bad block when I dump the NAND. In the past when I have tried to dump and update it with Flash360 and Toolbox Maker, it never flashes back correctly and I have to take it back to the shop to get fixed. However, I can dump and update other people's units that do not have that bad block. If I can use this to make that task easier, it would be great? Any comments are greatly appreciated.

That caught my interest too.

stick a old freeboot image in and it should get the cpu key from that

I wonder if we can update our 12625 to 13146 with this one,anyone who could simply put it through step by step would be greatly appreciated.

smc detection is good if you don't know what jtag wiring you have nice update Just load your nand you have on your xbox now and it will use that SMC

That's cool, I have problems booting to xell with a couple of my jtags so that feature will help

I currently have a XBR 3.0 Jtag Falcon using the directions from 2009. Can I assume that the correct SMC settings is stock?

I have both the Cpu key and the stock bin file. When I run the program I get a cannot detect SMC version message.

What does SMC version mean and how do I tell what version I have?

could this app actually tell you what smc method was used, from looking at a dump of the current nand image? Would be handy to be noted down for future reference rather than waiting/relying for future applications to have a same/similar automate feature?

My xenon I did myself (standard) but my jasper box was bought pretagged and notta clue by what method (would rather not take it apart to find out either tbh)

yes it did know what smc method was used when you load your nand and set the smc detection mode

hmmm not sure if this is right

I tested creating an image....using the backed up freeboot nand I was given on the CD when I got the jasper.

Firstly, it says "Previous SMC Used Is : Stock". Now when I pm'd the guy, he wasn't entirely certain, but did seem to think that mine may have been an audclamp method of wiring.

Anyways.....when I press Yes, and then save the updflash file, it launches "360 Flash Dump Tool" opening the new file....but it stops there.....all the Key Vault info on the right hand side says "Bad Key/KV" Any ideas?

-----

edit : aah might be me misreading the info. If I launch 360 Flash Dump Tool manually (have never used this tool before) and open up the original freeboot.bin I was given......it still says the same Bad Key/KV info.

So am I right in thinking then that this is the last step and the process doesnt auto close this window?

Also, is there any way to check/see if jasper nand has got bad blocks in? I know how to do it with old xenon nands from the very early methods, but dont believe the older programs were compatable with newer nands like jaspers etc

OK, works good but here's what I wanted to do.

I've had random argon errors on my falcon but I've never bothered about it til now. So what I did was get my aud_clamp wire ready to swap over, then built my image from my orig.bin selecting the correct option for this and de-selecting AutoDetect SMC in options.

After flashing it on I expected an error with the existing ARGON wiring still in place, upon which I was going to solder it over to the aud_clamp wire and then the error should have gone(still with me?), but it boots fine and I've done this twice and it still boots to 13146 fine but with the original jtag setup which I don't want

Edit: Isn't it supposed to use the falconaud.bin for the SMC config?

I did my falcon around the time of the summer update, I remember using diodes in the wiring and did the lpt wiring thing too, I have always been scared stiff of updating this xbox for obvious reasons and everytime i`ve tried i get errors saying my cpu key doesn`t match so i progress no further each time, I would like to try this app in the hopes that it may make my life easyer, Many thanks to everyone out there making all these brilliant tool btw

which SMC option do i check? just watched a video on youtube showing what an aud_clamp method is & I know i didn`t do that.

Thanks for your help

im just going round in circles again, this is so frustrating! it`s not that there isn`t any info, just to much and all to confusing

I wanna play world of keflings

Join elitemodscene and look at the Tutorial (New fbBuild FreeBOOT v.31 Tutorial for 13146 dashboard) it will help

Did you get your cpu key from xell?

In regards to your wiring option, sounds like you used the original type so go with that.

I can get this to work with Easyfreeboot but I'm gonna give Jtag Tool v3.13 a go since it now has reintroduced the aud_clamp method.

Yeah, I know I'm being lazy, I've used fbBuild before but since I'm going down the alternative wiring route I want to start off the easiest way possible.

Edit: On a side note I hex compared all the SMC files in Easyfreeboot and while there are differences between say falcon.bin and falconaud.bin or falconfull.bin, there are no differences between falconaud.bin and falconfull.bin.

I'm no coder but that doesn't seem right, can anyone confirm? Falconfull.bin I thought would be different for the tray_open option as well as aud_clamp.

just use fbBuild is easy look for the Tutorial in elitemodscene

Ok, I better report back. After scratching my head in confusion as to why I couldn't seem to get the aud_clamp method to work but it was still booting ok with the original wiring with a supposed aud_clamp type image flashed on, I had since left the power disconnected for the past 24 hours.
After coming home from work today I had a new image built ready to flash on that had been built with jtag tool using the aud_clamp only method, same as what I'd done using Easyfreeboot.

Guess what happened upon booting..........E79. Weird, I thought, I've never had an E79 on this console before!?
I still had the original wiring in place but also noticed a quick "bip" sound through the speakers that I'd never heard before. Instantly I thought, ah that's new and the only difference is that it's had a proper power down and reset.
I grabbed my soldering iron and swapped the TMS wire from the ROL to the aud_clamp and wha-la.....it booted clean, so by failing to remove the power and let the console fully reset I hadn't let it enable the new SMC configuration that I wanted to switch to.
I feel like such a NOOB

I thought "What the hell!" and went ahead and also flashed on the image that I had ready, built with Jtag tool using the aud_clamp method also and reset the console properly this time, too.
No problem there either.

My absolute apologies to the developer for thinking that it was something wrong with the app and I hope this might save someone from the same headache.

its not your fault i learnt a while back theres a problems with the smc's i included the aud_clamp and tms one i dont think the tms is enabled properly. i get the feeling that the creator of jtagtool just copied my smc's so thats why the bug is in both programs. should be fixed in the next update for now use the import previous smc file

Thanks, for now everything's running fine.

Which smc import do you mean? If you mean my previous hacked smc, it was using the original jtag wiring so would have to be modified first.

Also, I still have my jasper to do but I'm planning on switching to both the aud_clamp and tray_open options so I'll see how that goes.