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

Discussion in 'Xbox 360 Guides' started by InsaneNutter, Oct 23, 2011.

  1. darksmart

    darksmart New Member

    Joined:
    Nov 21, 2011
    Messages:
    3
    Likes Received:
    0
    Hi
    I updated,it worked for some days and now it does not start up at all showing 3 rrod..is it the update dash fault or just a co-incident that i got rrod after the update??
     
  2. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,180
    Likes Received:
    3,324
    Location:
    Yorkshire, England
    Its something i will add, it was not apparent at the time as i have never had a Jtag on XBR it would be impossible for me to have known when doing the tutorial.

    You need to get a USB nand flasher such as the nand x, this will need soldering to the 360's motherboard and then you can flash back to your working backup.

    If it worked at the time then its just an unlucky coincidence, if the update had gone wrong your console would not have worked after it.
     
  3. knuckz

    knuckz New Member

    Joined:
    Dec 4, 2011
    Messages:
    1
    Likes Received:
    0
    Awesome guide, really easy, just bought the Jtag today off a friend and was completely clueless, got through it without a hitch, look forward to getting to grips with it and learning this stuff.
     
  4. cabernet77

    cabernet77 New Member

    Joined:
    Dec 5, 2011
    Messages:
    3
    Likes Received:
    0
    jasper 16mb nand

    hi there i have a jasper 16mb nand just wonderin when building with fbuild
    would i type
    fbbuild.exe -c jasper -f 13604 -d mydata updflash.bin?
    or do i have to write
    fbbuild.exe -c jasper16 -f 13604 -d mydata updflash.bin?
     
  5. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,180
    Likes Received:
    3,324
    Location:
    Yorkshire, England
    You would type fbbuild.exe -c jasper -f 13604 -d mydata updflash.bin
     
  6. cabernet77

    cabernet77 New Member

    Joined:
    Dec 5, 2011
    Messages:
    3
    Likes Received:
    0
    one other small question im currently on 12611 can i go directly to 13604 or do i need to do a step wize approach? Thanks in advance
     
  7. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,180
    Likes Received:
    3,324
    Location:
    Yorkshire, England
    That will be fine, I went from 12611 to 13604 when creating this tutorial.
     
  8. cabernet77

    cabernet77 New Member

    Joined:
    Dec 5, 2011
    Messages:
    3
    Likes Received:
    0
    when trying to run fbbuild from cmd
    got the following error

    "an unhandled exception 0xc0000005 has occured, exiting....."

    what could that mean?
     
  9. 75mak

    75mak Member

    Joined:
    Nov 17, 2011
    Messages:
    13
    Likes Received:
    0
    I would try differant software tools to apply the NAND flash. As in my experience it makes a big differance depending on what tools you use e.g. Xell update flasher, nandflash tool, flashpro etc. Once I even had to use rawflash.elf which was due to flashing a bad NAND which had xell reloaded instead of xell. I couldn't use update flash so I tried rawflash. This didn't work, but it did change the NAND image back to xell. I then flashed the exact same NAND using xell, at xbox booted up fine.

    I would say try using various tools to rebuild the NAND. Easyfreeboot etc.

    It's not like you have much choice now, if you want to recover you'll probably need nandx hardware tool anyway, so try out as much as you can with differant flash tools mentioned above and you might get lucky.
     
  10. fst

    fst New Member

    Joined:
    Dec 25, 2011
    Messages:
    1
    Likes Received:
    0
    Thanks, InsaneNutter, you helped me a lot in updating my Falcon from 12611 to 13604.

    However, seeing a lot of failure reports I've decided to follow another tutorial I felt more confident of: "How to use XeBuild v1.0 (FreeBoot/GGBoot/Retail Images 7371 - 14699)". It's on 360iso , and apparently you can't link to that site here.
    It uses XeBuild instead of FbBuild (which I believe is a newer version or a fork of some kind), and you have to extract end decrypt SMC using "360 Flash Dump Tool" and put the resulting SMC_dec.bin in mydata folder as smc.bin, otherwise it's similar to the procedure described here.

    A couple of bits I've figured out:
    • fbBuild produces different binaries depending on whether you were using lower case or UPPER CASE to write down the CPU key. They will probably both work, but I never tested them anyway and ended up using upper case for XeBuild even though Xell displays the key in lower case. 360 Flash Dump Tool automatically converts the key you give it to upper case.
    • If you're using these tools on a virtual Windows machine like I do via Oracle's VirtualBox with Mac OS as a host, you want to copy the nand dump to the guest Windows and not to open it from a folder shared with the host otherwise the build may fail with the following messages in the log:
      Code:
      NAND dump is from a big block machine
      NAND dump uses big block controller
      In that case if you copy your nanddump.bin to the guest OS' file system, the build will be successful and the log will say that NAND dump came from a small block machine. The log I'm talking about is updflash.bin.log located in the FbBuild/XeBuild root folder. You should definitely check it after building a new firmware binary.
     
    Last edited: Dec 26, 2011
  11. anttimonty

    anttimonty Member

    Joined:
    Nov 29, 2010
    Messages:
    7
    Likes Received:
    0
    fbbuild gives me the following error:

    fbBuild_0.33>fbbuild.exe -c falcon -f 13604 -d mydata u
    pdflaash.bin
    ---------------------------------------------------------------
    fbBuild v0.33 (R:272)
    ---------------------------------------------------------------
    **** could not read smc.bin (-1) ****
    ******* ERROR: critical bootloader files are missing, cannot proceed!
    ***** FATAL BUILD ERROR: -1 unable to complete NAND image

    EDIT: Never mind got it working when I extracted smc_config.bin, a decrypted KV.bin and a decrypted SMC.bin with 360 Flash Dump Tool 0.97 and placed them in mydata folder.
     
  12. Miki800

    Miki800 New Member

    Joined:
    Jul 11, 2012
    Messages:
    2
    Likes Received:
    0
    I think everything passed successfully but now FSD is disabled, my xbox stopped booting into FSD when I turn it on after I completed your guide, what gives?

    please tell me how do I restore this? I only upgraded because I wanted my KINECT to work :(

    edit:
    wait, I do not have FSD anymore... so how can I write the original flash ever again if I can not use FSD to run Nand Flasher 360??

    HOLY CRAP MY XBOX IS TRASHED NOW? O_O WOW... NOO... what do I do now???

    Please give a warning in the first post regarding the danger of loosing FSD when following your guide!
    or reply here for a fix?
     
  13. InsaneNutter

    InsaneNutter Resident Nutter Staff Member

    Joined:
    Jun 1, 2007
    Messages:
    11,180
    Likes Received:
    3,324
    Location:
    Yorkshire, England
    This guide has nothing to do with FSD, its about updating your console only. FSD is something YOU (well the person who hacked your console i guess) chose to make boot when the console powers on.

    Install Dashlaunch 3.02 and your console will boot FSD again.

    As you need some way of launching the Dashlaunch install, burn the ISO of XEX Menu to disc, put it in the Xbox 360 and load it up from the games tab. You can then load the Dashlaunch installer off a USB drive from there.

    It should pick your existing Dashlaunch settings up and will function how your console was before you updated.
     

Share This Page