Easily update your Jtagged Xbox 360 to Kernel / Dashboard 13604 with FbBuild 0.33

hi hi everybody!

thank you for your advice InsaneNutter! i am now on 13604 thanks to you.
here is how i proceeded (may be it will help other people):
1) i made the update to 9199 using my ORIGINAL nand (not the one dumped by flash360, following your tuto :How to update your Jtagged Xbox 360 to Freeboot 0.032 (9199 Dash / Kernal)
2) i made a dump of the fresh flashed 9199 freeboot using nand flash.
3) i use the nand 9199 to update to 13604 (following your tuto : Easily update your Jtagged Xbox 360 to Kernel / Dashboard 13604 with FbBuild 0.33).
4) i flassh the new fresh flashed 13604 using nand flash.

everything worked fisrt try ! just so awesome.

just had one little problem (hope it won't happen again) : after i powered on my xbox, i wanted to plug my external usb drive (with all my games). so i turn my xbox off. i plugged the externed hdd drive and when i turned it on, i had the 3red leds and my screen was blue and purple. i though it was a nighmare and i turned it off. i took a deep breathe and waited 10 minutes, thinking what was this s**t. i turned it on again without the usb hdd and everything went back to normal. i was still in 13604. only then i plugged my usb hdd and launched xexloader and played to my games.

hope this experience will help other.

 

I follow your tutorial, and now I get working 13604 with avatar on my JTAG. Nice tutorial!

See you again at kernel 14xxx. thanks!

 

E79 Error

I followed your TUT to the letter and now I get the E79 error with one red ring (the lower right one)

Any ideas?

 

E70 error on startup JTAG update failure

I also followed the tutorial to the letter and I'm getting E79 error on startup now.

I am using a falcon 16mb console. I was previously on a 8095 dash. A very early dash. I hadn't used the console in a while, but booted up and everything was running fine. Decided to update the dash using this tutorial.

Everything was going fine up until the restart. I powered off the console for 2 minutes by unplugging the cord. When I restart I get the E79 screen. I did have one bad block and that was marked by NAND flasher - but I don't know if that is/was the problem.

I can still access XELL by pressing eject button on startup, so I'm hoping all is not lost.

Is there a way I can reflash or get back to the dashboard?

 

OK, I got my 8955 NAND back using Xell

Any suggestion on why it didn't work or what I can do to update?

Would putting cpu key in lower case make a difference?

here's the output from the fbbuild log file:

????????

 

I can still get into xell as well but my nand backup dump I made still gives me the E79 Error.

 

so did you update the nand (using xell) with your old backup by renaming the file on the usb to updflash.bin?

As I'm on 8955 I want to update to 9199 using freeboot instead of xbr and then maybe update to the latest dashboard using this tutorial. Someone earlier seems to have had success with that method.

Although a couple of things are holding me back.... mainly.... I have bad blocks and I have referred to this turtorial : digiex.net/guides-reviews/console-guides/xbox-360-guides/7177-how-update-your-jtagged-xbox-360-freeboot-0-032-9199-dash-kernal.html

which uses flash360 tool? Am I safe to use this despite having 1 bad block on my nand? can I use NAndflasher or do I have to use flash360 tool if I want to go to 9199 - as in that tutorial.

and the second issue i have is the thing about an original NAND mentioned in that tutorial. I have my original NAND saved for me in a RAR file and sent to me by the person who JTAG'ed my xbox a couple of years ago. Do I have to use that Orignal NAND backup I have or am I safe to use the NAND backup I made using NANDflasher tool in this tutorial.

An Answer to those 2 questions would be greatly appreciated.

Thanks

 

Yes I renamed my "orig_nand.bin" to updflash.bin and booted into xell. It did its thing and said success but still have the E79 error

I also have the 16meg Falcon

 

not sure what you can do... hopefully someone with more knowledge will reply to this thread shortly and answer both of our queries...

 

OK, I used my NAND dump made with nandflasher and freeboot toolbox to get to 9199

and then used nandflasher to flash it... and everything looks good. Xbox started up and system version is 9199.

I then followed this tutorial to get to the latest dash, I was going to use NADNflasher to dump my 9199 nand, I restarted the xbox again, had a brief flashing red light with blank screen. restarted again and it booted up this time...

However, I ran xexmenu and a very strange thing happened. my usb was empty. Just a few moments before I had checked it and it had my old NAND renamed and obviously NANDflasher. SO I removed it and reinserted it... and I got a small TMP file created. SO I removed it again and put it back into Windows to check. And it was cleared with only a test.tmp file and a nameless blank file. So I reformatted the USB (luckily nothing else was on it before everything was deleted) as the blank file was undeletable in windows.

copied NANDfllasher back on and same thing happened, I tried inserting the USB disk later this time, after I have got into xexmenu.

This has just happened 4 times, each time NANDflasher or anything else on the USB is deleted and I only have a tmp file.

Any ideas why this is happening

and what can I use to start NANDflasher?

 

Thanks for that.

Although now I am back where I'm started... The ISO worked. Used it to dump NAND then modify the 9199 using fbbuild. I then flashed this updflash.bin using nandflasher from the dvd.

but that brought up e79 error again.

used xell to try and flash using the 9199 freeboot image that was working but that also brought up E79 error again

So I had to use Xell to flash back to 8955 working NAND - back where I started.

InsaneNutter, Question: would you know why my 9199 image (when it did flash)` was clearing my USB flash disk whenever I inserted, it would leave a test.tmp file on. Even when only on the dashboard (not xexmenu)?

Do you think I should flash to freeboot 9199 dashboard by using my orig NAND, maybe I might not get that usb disk problem? last time I used my hacked 8955 NAND, it worked but I had the problem mentioned above with the USB disk.

EDIT: ok, tried flashing with orig NAND. Got 9199 with freeboot working again.

But still getting the problem with the USB disk - it deletes the disk when I insert it into either of the two usb ports on the front. leaving just a test.tmp file.

Can anyone tell me why this is happening?

Is it possible to have just use xell to update the NAND, rather than using NANDflash? what are the advantages and risks with just using xell instead?

I have quuite a few NAND dups now and I would like to try update the flash using differant combinations. and I'm unable to get NANDflash to work now even with the ISO I burnt. the USB disk just reads blank and when I check back in windows, everything is deleted.

SO, I want to use xell as that seems the easiestway to flash NAND. just want to know what are the risks in using Xell instead of NANDflasher or flash360

 

Insane Nutter:

I tried to use best pig to update freeboot hoping that was my issue.

When I run the orig_nand.bin I made through NAND_Flasher 360 through best pig I get the an error "Your dump has not been properly extracted"

This was the same dump I used for you TUT to begin with. Am I right in thinking that since the nand was dumpled poorly and I flashed the updated version from it, that is what is causing my E79 and even when I try to reflash the un-updated nand I still get the error.

Being as though these were the only nands I have since I bough my JTAG from someone, is there anything I can do at this point?

 

update from previous post...

it appears the USB flashdisk I was using doesn't work to well on 9199 dashboard. using a diff usb flash disk helped overcome the problem.

but still can't flash to 13604 dashboard.

I've tried quite a few things. I can manage to get to 9199 NAND from xell now.

But that's where I'm stuck. I've tried extracting kv smc and config files as detailed elsewhere. But that doesn't seem to make a differance.

The last NAND I used was from my 9199 backup. - again just brought me to E79 screen.

What suggestiions do you have to update... I'm on 9199 should I increment 1 dashboard at a time?

 

I've been scanning through the updflash log file in fbbuild and I noticed the above lines.... Would that be causing the problems?

I've tried numerous flashes. I think I've been lucky considering I've always had Xell on each failed go.

why doesn't launch.xex be read.... earlier in the log file it states

 

UPDATE:

I finally managed to update to 12625 using my 9199 backup NAND as a base and then using Easy Freeboot to create a new nand image.

Flashed with NAndflasher 360 while on 9199.

Now, I will try to get from 12625 to 13604 - this seems a lot more harder than others seem to have found it.... I wonder if it's anything to do with having a falcon 16MB?

anyway, I will try to update and let you guys know, so any future jtagers with similar problems might try out what worked for me.

FURTHER UPDATE:

OK I managed to get up to dash 13599 via 12625. Each time using Easy FreeBOOT 5.32 to create the new NAND update image.

As FreeBOOT 5.32 only goes upto 13599 I was then forced to go back to using fbBuild .33 - Again, this caused an E79 on restart. Therefore, I think my problem is linked to the creation of NAND with fbBuild. I think I may have to wait for FreeBOOT 5.32 updates to include the most recent dashboard (13604).

It's been a very long day, but at least I've managed to update from 8599 upto 13599...

Thanks for all your help so far

 

Registered just to say a big Thanks..Very nice and easy tutorial..I was a bit worried about updating stuff but after reading here,i did it in minutes without any problem..Now I can also play Forza 4..

 

Had the same problem. Reason was upgrading directly from 12611 to 13604.Had to first go to Freeboot 13146, install original update, then 13599 and finally 13604.

 

I wish you would have said that in the main post...
I followed the instructions to the letter, didn't get any error, flashed the new nand, and now I got a RROD (3 leds).
Any idea what I can do now ? I get the RROD with the eject button too.