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! :D

See you again at kernel 14xxx. thanks!
 
Last edited:
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?
 
Last edited:
E70 error on startup JTAG update failure

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

Any ideas?
Click to expand...

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?
 
75mak said:
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?
Click to expand...

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:

---------------------------------------------------------------
fbBuild v0.33 (R:272)
---------------------------------------------------------------
data directory overridden from command line to '13604'
per build directory overridden from command line to 'mydata'
file name overridden from command line to 'updflash.bin'

------ parsing user ini at '.\mydata\options.ini' ------
loading file...done!
pre-parsing and sanitizing
done!
User options.ini loaded, 0x13a bytes in memory
loading cpukey.txt from .\mydata\cpukey.txt
CPU Key set to: 0x4B9A364C2527519F9DEA81B7A8C61A1C
loading 1blkey.txt from 1blkey.txt
1BL Key set to: 0xDD88AD0C9ED669E7B56794FB68563EFA sum: 0x983 (expects: 0x983)
Using nonandmu option (ini file)

------ Checking .\mydata\nanddump.bin ------
Loading NAND dump...done!
NAND dump is from a small block machine
NAND dump uses small block controller
parsing dump into user and spare...
block 0x24a was remapped to block 0x24b, entering remap instance 1
block 0x24b was remapped to block 0x3e0, entering remap instance 2
done!
cleaning up stray remaps
done!
--remap summary--
0: source: 0x024a dest: 0x024b
1: source: 0x024b dest: 0x03e0
-----------------
decrypting KeyVault at address 0x4000 of size 0x4000
keyvault decrypted OK, will use if no kv.bin is provided
decrypting SMC at address 0x1000 of size 0x3000
SMC decrypted OK, checking for hack
SMC in image is hacked, will use if no external smc.bin is provided
seeking smc config in dump...found at offset 0xf7c000! Using if no smc config is provided.
MobileB.dat found at page 0x74dc, size 2048 (0x800) bytes

------ parsing ini at '.\13604\filelist.ini' ------
ini version 13604

ini: label [falconbl] found
found (1) 'cb_5770.bin' crc: 0x3279f0d5
found (2) 'cd_5770.bin' crc: 0xd04e8927
found (3) 'ce_1888.bin' crc: 0xff9b60df
found (4) 'cf_4532.bin' crc: 0xd28ef722
found (5) 'cg_4532.bin' crc: 0x2cc9b951
found (6) 'cb_5771.bin' crc: 0x859140f0
found (7) 'cd_8453.bin' crc: 0x25e0acd0
found (8) 'cf_13604.bin' crc: 0x639a4cd7
found (9) 'cg_13604.bin' crc: 0x7e9f5364

ini: label [flashfs] found
found (1) 'aac.xexp' crc: 0xdaed8bc7
found (2) 'bootanim.xex' crc: 0x8a7ab1b4
found (3) 'createprofile.xex' crc: 0xe19ca8c4
found (4) 'dash.xex' crc: 0xecdaf6c0
found (5) 'deviceselector.xex' crc: 0xaa4579d1
found (6) 'gamerprofile.xex' crc: 0xebc5fec3
found (7) 'hud.xex' crc: 0xe2410ee1
found (8) 'huduiskin.xex' crc: 0x390eac39
found (9) 'mfgbootlauncher.xex' crc: 0xf3637ed9
found (10) 'minimediaplayer.xex' crc: 0x23d28bb8
found (11) 'nomni.xexp' crc: 0xed7cd3f5
found (12) 'nomnifwk.xexp' crc: 0x2c6fd7e8
found (13) 'nomnifwm.xexp' crc: 0xaa978831
found (14) 'signin.xex' crc: 0xf7436a62
found (15) 'updater.xex' crc: 0xd0cd6753
found (16) 'vk.xex' crc: 0x65f4eec0
found (17) 'xam.xex' crc: 0x2a74ee0f
found (18) 'xenonclatin.xtt' crc: 0xd5d17ff5
found (19) 'xenonclatin.xttp' crc: 0x7a507ad1
found (20) 'xenonjklatin.xtt' crc: 0xdde4a14c
found (21) 'xenonjklatin.xttp' crc: 0x945b7092
found (22) 'ximecore.xex' crc: 0xccb87938
found (23) 'ximedic.xex' crc: 0x1d992bfb
found (24) 'ximedic.xexp' crc: 0x47a55af9
found (25) '..\launch.xex' crc: 0x00000000
found (26) '..\lhelper.xex' crc: 0x00000000

ini: label [security] found
found (1) 'crl.bin' crc: 0x00000000
found (2) 'dae.bin' crc: 0x00000000
found (3) 'extended.bin' crc: 0x00000000
found (4) 'secdata.bin' crc: 0x00000000
------ ini parsing completed ------

output name overridden to: updflash.bin

Writing initial header to flash image

------ Loading bootloaders and required security files ------
could not read \bin\payload.bin, using built in payload (0x200 bytes)
reading .\mydata\smc.bin failed, using smc.bin from nand dump
reading .\mydata\kv.bin failed, using kv.bin from nand dump
reading .\13604\cb_5770.bin (0x8e40 bytes) (crc32: 0x3279f0d5 ini: 0x3279f0d5)
reading .\13604\cd_5770.bin (0x56c0 bytes) (crc32: 0xd04e8927 ini: 0xd04e8927)
reading .\13604\ce_1888.bin (0x5606a b pad 0x56070 b) (crc32: 0xff9b60df ini: 0xff9b60df)
reading .\13604\cf_4532.bin (0x44c0 bytes) (crc32: 0xd28ef722 ini: 0xd28ef722)
reading .\13604\cg_4532.bin (0x2ef40 bytes) (crc32: 0x2cc9b951 ini: 0x2cc9b951)
reading .\13604\cf_13604.bin (0x4450 bytes) (crc32: 0x639a4cd7 ini: 0x639a4cd7)
reading .\13604\cg_13604.bin (0x659e0 bytes) (crc32: 0x7e9f5364 ini: 0x7e9f5364)
could not read \bin\freeboot.bin, using built in core (0xd50 bytes)
reading .\13604\bin\patches_falcon.bin (0x8bc bytes)
**** ldv line 3 set to 00 f0 type: 3
xell not found in perbuild directory, checking firmware /bin folder
xell not found in firmware /bin folder, checking base path
reading xell-2f.bin (0x38a60 bytes)
reading .\13604\cb_5771.bin (0x9340 bytes) (crc32: 0x859140f0 ini: 0x859140f0)
reading .\13604\cd_8453.bin (0x5780 bytes) (crc32: 0x25e0acd0 ini: 0x25e0acd0)
reading .\mydata\smc_config.bin failed, using smc_config.bin from nand dump
-------------------
checking smc_config
-------------------
extracting config
------------------
SMC config info:
------------------
Target temps: Cpu: 80øC Gpu: 75øC Edram: 78øC
Max temps : Cpu: 100øC Gpu: 100øC Edram: 102øC
Cpu Fan : (auto)
Gpu Fan : (auto)
MAC Address :
AVRegion : 0x00000300 (PAL50)
GameRegion : 0x02fe (NTSC/EU)
DVDRegion : 2
resetKey : LAUY
---------------------
Checking ini for smc config data patches
smc was not patched
---------------------
done!

------ Encrypting and finalizing bootloaders ------
patching payload.bin to load size 0xd50 (0x354 reps)
hack found in smc.bin!
done!

------ Adding bootloaders to flash image ------
Fixing up FS table...done!
Writing zeropair CG patch slot overflow data to sysupdate.xexp1...done!
Writing target CG patch slot overflow data to sysupdate.xexp2...done!

------ adding 26 firmware files ------
reading .\13604\aac.xexp (0x4800 bytes) (crc32: 0xdaed8bc7 ini: 0xdaed8bc7)
reading .\13604\bootanim.xex (0x55000 bytes) (crc32: 0x8a7ab1b4 ini: 0x8a7ab1b4)
reading .\13604\createprofile.xex (0xc000 bytes) (crc32: 0xe19ca8c4 ini: 0xe19ca8c4)
reading .\13604\dash.xex (0x5e7000 bytes) (crc32: 0xecdaf6c0 ini: 0xecdaf6c0)
reading .\13604\deviceselector.xex (0x9000 bytes) (crc32: 0xaa4579d1 ini: 0xaa4579d1)
reading .\13604\gamerprofile.xex (0x1a000 bytes) (crc32: 0xebc5fec3 ini: 0xebc5fec3)
reading .\13604\hud.xex (0x1f000 bytes) (crc32: 0xe2410ee1 ini: 0xe2410ee1)
reading .\13604\huduiskin.xex (0x11000 bytes) (crc32: 0x390eac39 ini: 0x390eac39)
reading .\13604\mfgbootlauncher.xex (0x8000 bytes) (crc32: 0xf3637ed9 ini: 0xf3637ed9)
reading .\13604\minimediaplayer.xex (0xc000 bytes) (crc32: 0x23d28bb8 ini: 0x23d28bb8)
reading .\13604\nomni.xexp (0xd000 bytes) (crc32: 0xed7cd3f5 ini: 0xed7cd3f5)
reading .\13604\nomnifwk.xexp (0x2000 bytes) (crc32: 0x2c6fd7e8 ini: 0x2c6fd7e8)
reading .\13604\nomnifwm.xexp (0x5000 bytes) (crc32: 0xaa978831 ini: 0xaa978831)
reading .\13604\signin.xex (0x12000 bytes) (crc32: 0xf7436a62 ini: 0xf7436a62)
reading .\13604\updater.xex (0x8000 bytes) (crc32: 0xd0cd6753 ini: 0xd0cd6753)
reading .\13604\vk.xex (0x9000 bytes) (crc32: 0x65f4eec0 ini: 0x65f4eec0)
reading .\13604\xam.xex (0x218000 bytes) (crc32: 0x2a74ee0f ini: 0x2a74ee0f)
reading .\13604\xenonclatin.xtt (0x11b000 bytes) (crc32: 0xd5d17ff5 ini: 0xd5d17ff5)
reading .\13604\xenonclatin.xttp (0x18000 bytes) (crc32: 0x7a507ad1 ini: 0x7a507ad1)
reading .\13604\xenonjklatin.xtt (0x1a8000 bytes) (crc32: 0xdde4a14c ini: 0xdde4a14c)
reading .\13604\xenonjklatin.xttp (0x7000 bytes) (crc32: 0x945b7092 ini: 0x945b7092)
reading .\13604\ximecore.xex (0x15000 bytes) (crc32: 0xccb87938 ini: 0xccb87938)
reading .\13604\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
reading .\13604\ximedic.xexp (0x2800 bytes) (crc32: 0x47a55af9 ini: 0x47a55af9)

***** could not read .\13604\..\launch.xex, skipping *****

***** could not read .\13604\..\lhelper.xex, skipping *****

------ adding 4 security files ------
reading .\mydata\crl.bin (0x9e0 bytes)
writing as crl.bin to flash
reading .\mydata\dae.bin (0xad30 bytes)
writing as dae.bin to flash
reading .\mydata\extended.bin (0x4000 bytes)
writing as extended.bin to flash
reading .\mydata\secdata.bin (0x400 bytes)
writing as secdata.bin to flash

------ checking for Mobile*.dat ------
MobileB.dat was found in dump, 0x800 bytes, adding type 0x31

------ adding smc_config.bin ------

------ finalizing image ------
Fixing up empty FS block entries...done!
Writing FS table to image...done!
calculating ECD bytes and assembling raw image...done!
remapping 2 blocks
copying 0x4200 bytes of LBA 0x24a to block 0x24b...zero fill origin...done!
copying 0x4200 bytes of LBA 0x24b to block 0x3e0...zero fill origin...done!
done!
writing file 'updflash.bin' to disk...done!
updflash.bin written OK

---------------------------------------------------------------
updflash.bin built, info:
---------------------------------------------------------------
console : falcon
NAND size: 16MiB
xell : power on console with console eject button
CPU KEY....
Click to expand...

????????
 
Last edited:
veritas2884 said:
I can still get into xell as well but my nand backup dump I made still gives me the E79 Error.
Click to expand...

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...
 
8955 users (XBR) appear to have a lot of problems updating to FreeBoot (9199+)

If you are on 8955 update to 9199 first using this tutorial - https://digiex.net/guides-reviews/console-guides/xbox-360-guides/7177-how-update-your-jtagged-xbox-360-freeboot-0-032-9199-dash-kernal.html

After that follow this tutorial to get to the latest verson.

You can use Nandflasher, that is better with bad blocks. It was just not out when the other tutorial was created so is not mentioned in the above link.
Use your existing nand if you can, that should keep any config changes, although you should be able to use your orig.
 
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?
 
Unzip and Burn this ISO to a CD - XEX Menu
XEX Menu should appear in the demo section when you put the disc in the console, load it then use it to explore your USB drive with NandFlasher360 on it.
 
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?
 

Attachments

  • error.jpg
    error.jpg
    482.2 KB · Views: 2,092
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?
 
reading .\13604\ximecore.xex (0x15000 bytes) (crc32: 0xccb87938 ini: 0xccb87938)
reading .\13604\ximedic.xex (0x90000 bytes) (crc32: 0x1d992bfb ini: 0x1d992bfb)
reading .\13604\ximedic.xexp (0x2800 bytes) (crc32: 0x47a55af9 ini: 0x47a55af9)

***** could not read .\13604\..\launch.xex, skipping *****

***** could not read .\13604\..\lhelper.xex, skipping *****
Click to expand...

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

found (22) 'ximecore.xex' crc: 0xccb87938
found (23) 'ximedic.xex' crc: 0x1d992bfb
found (24) 'ximedic.xexp' crc: 0x47a55af9
found (25) '..\launch.xex' crc: 0x00000000
found (26) '..\lhelper.xex' crc: 0x00000000
Click to expand...
 
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..:D
 
Sp3kt3r said:
I do have the same problem, my xbox 360 won't detect the 13604 update after updating my JTAG with the 13604.I tried the USB and CD. when I launch the CD it's says your console is up to date.FAT,FAT32 different kind of usb key and no pop up for update.
Click to expand...
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.
 
InsaneNutter said:
8955 users (XBR) appear to have a lot of problems updating to FreeBoot (9199+)<br>
<br>
If you are on 8955 update to 9199 first using this tutorial - <a href="http ://digiex.net/guides-reviews/console-guides/xbox-360-guides/7177-how-update-your-jtagged-xbox-360-freeboot-0-032-9199-dash-kernal.html" target="_blank">http ://digiex.net/guides-reviews/console-guides/xbox-360-guides/7177-how-update-your-jtagged-xbox-360-freeboot-0-032-9199-dash-kernal.html<br>
<br>
</a>After that follow this tutorial to get to the latest verson.<br>
<br>
You can use Nandflasher, that is better with bad blocks. It was just not out when the other tutorial was created so is not mentioned in the above link.<br>
Use your existing nand if you can, that should keep any config changes, although you should be able to use your orig.
Click to expand...

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.
 
You must log in or register to reply here.
Top Bottom