Easily update your Jtagged Xbox 360 to Kernel / Dashboard 12611 with FbBuild 0.11
- Thread starter InsaneNutter
- Start date
i followed the direction to make the image again, i mad more than one of the same image but they dont match in total connander. says there ae differences between them. that normal?
is it ok that i create a freeboot.bin file to transfer using lpt port?
each file i create is different in 360 flash dump also.
the "6BL [CF] patch 1 <12611> LDV [2] PD <0xD5D5D5>
the part in bold is changed everytime i create an image. is that normal or ok to continue?
is it ok that i create a freeboot.bin file to transfer using lpt port?
each file i create is different in 360 flash dump also.
the "6BL [CF] patch 1 <12611> LDV [2] PD <0xD5D5D5>
the part in bold is changed everytime i create an image. is that normal or ok to continue?
BigRod989
Addict
1) Reflow the Southbridge
2) Restore the NAND content using Xell and the JTAG hack
Xbox-experts.com - Error code 2 Green & 2 Red Lights E52 / 0310
It shows that when the console is in manufacturing mode, theoretically it can also be a Southbridge issue so reflowing might work.
More likely is an improper NAND update though, so a software related problem.
The detailed description is:
Mfgbootlauncher Unable to parse the host response (factory command)
Mfgbootlauncher problem with Base64 encoding
also found this
http://www.thetechgame.com/Forums/viewtopic/t=345132.html
How To Fix Christmas Lights On a Jtag [Tutorial]
1. Rename your original freeboot image to updflash.bin
2. Put it on a usb drive that is formatted to FAT32
3. plug it into your 360 and turn console on with the eject button
4. let xell do its update
5. Unplug back power cables for about 30 seconds.
6. plug every thing back in and you should be greeted with the dashboard.
2) Restore the NAND content using Xell and the JTAG hack
Xbox-experts.com - Error code 2 Green & 2 Red Lights E52 / 0310
It shows that when the console is in manufacturing mode, theoretically it can also be a Southbridge issue so reflowing might work.
More likely is an improper NAND update though, so a software related problem.
The detailed description is:
Mfgbootlauncher Unable to parse the host response (factory command)
Mfgbootlauncher problem with Base64 encoding
also found this
http://www.thetechgame.com/Forums/viewtopic/t=345132.html
How To Fix Christmas Lights On a Jtag [Tutorial]
1. Rename your original freeboot image to updflash.bin
2. Put it on a usb drive that is formatted to FAT32
3. plug it into your 360 and turn console on with the eject button
4. let xell do its update
5. Unplug back power cables for about 30 seconds.
6. plug every thing back in and you should be greeted with the dashboard.
Last edited:
InsaneNutter
Resident Nutter
Yes I have updated the links in the tutorial to FbBuild 0.11, its the same process just a newer version of FbBuild which contains a few bug fixes.
0.11 Changes:
- add "jasper16a" LBA method as default for jasper
- add SMC check for encrypted and known hack SMC
- search for valid smc_config hash instead of hard coded
offsets, support filename "config.bin"
- refine KV encryption check
- disable extended DVD auth for OSIG keyvaults (aka: AP25)
- random non-critical changes
FbBuild 0.11 can be downloaded here
Dash Launch 2.06 for FreeBoot 12611 built with fbBuild 0.11 can be downloaded here
0.11 Changes:
- add "jasper16a" LBA method as default for jasper
- add SMC check for encrypted and known hack SMC
- search for valid smc_config hash instead of hard coded
offsets, support filename "config.bin"
- refine KV encryption check
- disable extended DVD auth for OSIG keyvaults (aka: AP25)
- random non-critical changes
FbBuild 0.11 can be downloaded here
Dash Launch 2.06 for FreeBoot 12611 built with fbBuild 0.11 can be downloaded here
InsaneNutter
Resident Nutter
Nah you can upgrade to 12611 fine.
Hello
I followed the tutorial. Used my original nand (i saved via lpt 2010.03.02). When I boot up the 360 it does nothing, the controller cant connect, cant start via eject buttom, no any red led. I used this guid to jtag hack: http://www.xboxklub.hu/az_xbreboot_installalasa and work correctly so far. I think i dont any mistake. What should I do now? Please HELP!
I followed the tutorial. Used my original nand (i saved via lpt 2010.03.02). When I boot up the 360 it does nothing, the controller cant connect, cant start via eject buttom, no any red led. I used this guid to jtag hack: http://www.xboxklub.hu/az_xbreboot_installalasa and work correctly so far. I think i dont any mistake. What should I do now? Please HELP!
Ajie Prahasto
Member
i make it jtag new dashbooard + new dashlaunch 2.06
but everytime i restarting my xbox i always start in nxe dashboard not in fsd 1.20... what should i do to make the fsd as the fist load?
but everytime i restarting my xbox i always start in nxe dashboard not in fsd 1.20... what should i do to make the fsd as the fist load?
InsaneNutter
Resident Nutter
Try again and use your previously hacked nand as the source (freeboot or xbr) that appears to have a much better success rate.
You will have to flash it by LPT.
Got your launch.ini on your hard drive telling it what to load when the console is powered on?
just a note to everyone here...DO NOT USE THE SMC EXTRACTED FROM YOUR ORIGINAL DUMP !
fbBuild uses the SMC you give it VERBATIM, it does NOT patch it to do the jtag hack (alternate points or not, i use the original points)!
so, for best results, extract your SMC from 9199 freeBoot updflash.bin or similar, if you only have your original nand, use bestpig or any other way to make it and extract the SMC from that !
USING SMC FROM ORIGINAL NAND DUMP WILL RESULT IN E79 ERROR ON EVERY BOOT !
I had to use usbjtag to reflash because of this, do not be burned !
fbBuild uses the SMC you give it VERBATIM, it does NOT patch it to do the jtag hack (alternate points or not, i use the original points)!
so, for best results, extract your SMC from 9199 freeBoot updflash.bin or similar, if you only have your original nand, use bestpig or any other way to make it and extract the SMC from that !
USING SMC FROM ORIGINAL NAND DUMP WILL RESULT IN E79 ERROR ON EVERY BOOT !
I had to use usbjtag to reflash because of this, do not be burned !
InsaneNutter
Resident Nutter
That depends, I can honestly say all the files I used are from my original dump and that worked perfectly for my console, and has done so for many others.
Of course if you have used the aud-clamp wiring thats not gonna work, so you are right in saying the upgrade has a much higher chance of working when using the files from your existing FreeBoot image.
I did edit the guide to state that last weekend anyway so hopefully that means most people have had an easier time upgrading
Of course if you have used the aud-clamp wiring thats not gonna work, so you are right in saying the upgrade has a much higher chance of working when using the files from your existing FreeBoot image.
I did edit the guide to state that last weekend anyway so hopefully that means most people have had an easier time upgrading
if you extract the SMC from the updflash.bin fbbuild makes you will see it is bit by bit the same as the SMC you put in mydata
so, as it does not add jtag hack to smc, if you use the original microsoft SMC, it will not do the jtag exploit and you will always get e79 error at boot.
and as i said, im not using aud_clamp or open_tray or any such custom SMC requiring things, i am using the dead standard layout on jasper 256
so, as it does not add jtag hack to smc, if you use the original microsoft SMC, it will not do the jtag exploit and you will always get e79 error at boot.
and as i said, im not using aud_clamp or open_tray or any such custom SMC requiring things, i am using the dead standard layout on jasper 256
Get Social
