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

Thanks for the quick response.

Yes I copied the 13604 data into the folder. But there was already a filelist.ini file in there already so I replaced it with the 13604 data. When that didn't work I just used the .ini file that was already in the folder. That didn't work either. I still got the same error.

Unless I'm supposed to have both. They seem to be the exact same file.

I have a falcon jtag and I'm running Windows 7 if that makes any difference. I'm going to start again from scratch later. But I've been up all night and I'm exhausted. Going to bed right now. Hopefully I will have some luck in round 2
 
I have a Falcon JTAG I followed all your steps. I didn't get any errors. Everything went just like you said until I powered it back on. I checked the kernel number in the settings menu and it was correct. I just cannot get back to my Freestyle dash. I have no clue what went wrong. It acts like a non-JTAG Xbox now. Any thoughts on what could have happened?
 
3rl

Guys,
Unfortunately, after I have strict followed the tutorial I also have the 3rl, not even xell boots up. Could someone help me?

Just remembering, before all the process, my xbox was with xbr and 8955 dash. I dumped the nand following the tutorial steps and everithing seemed to be ok, but when I flashed back the modified nand, at the verification, I've got some bad blocks warnings, as you can see at the picture below.

Imagem 002.jpg

InsaneNutter, you said that if that occur, we should flash the xbox using a USB or LPT flasher... I still have the LPT connection I used the last time I JTAGed my xbox, but I have no clue about how to do it (I really don't remember the tutorial I followed, and I did it just once). Could you help me with that? What NAND dump I should use, the xbr one or the modified one?

Thank you for your help

obs: at first I also had the problem of fbBuild not extract the kv.bin and others files, I double checked and found that the CPU key I was entering was typed wrong. After I fixed that everything went just fine.
 
Looking my old files, I've found the way I did the first time JTAG. I think i should use nandpro, the newest version is v3.0, am I correct? Could someone please help me with the commands I should use to flash the nand with the correct dump (I still don't know if I should use the XBR dump or the newest modiffied one)? I think I have to make a full nand flash, am I correct? If so, I think this process made throught LPT cable take way too long to finish, am I right? Is there a easier and faster way to do that?
 
the_GUNN_man said:
I have a Falcon JTAG I followed all your steps. I didn't get any errors. Everything went just like you said until I powered it back on. I checked the kernel number in the settings menu and it was correct. I just cannot get back to my Freestyle dash. I have no clue what went wrong. It acts like a non-JTAG Xbox now. Any thoughts on what could have happened?
Click to expand...

You need to install dashlaunch again, here is the latest version that works with this dash.

When installing it should pickup your existing launch.ini, tell it to keep that and your Freestyle dash will boot again when you next start the 360 if thats how you had it configured.

unnamed said:
Looking my old files, I've found the way I did the first time JTAG. I think i should use nandpro, the newest version is v3.0, am I correct? Could someone please help me with the commands I should use to flash the nand with the correct dump (I still don't know if I should use the XBR dump or the newest modiffied one)? I think I have to make a full nand flash, am I correct? If so, I think this process made throught LPT cable take way too long to finish, am I right? Is there a easier and faster way to do that?
Click to expand...

From what you have said your initial flash only failed because you used the wrong cpu key when building the new nand.

Use the new nand you created with the correct CPU key and flash this.

Presuming you have a console with a 16mb nand the command should be NandPro dev: -w16 nand.bin
I think thats right i'm not at home and am going off the top of my head. In the above nand.bin would be the name of the nand you wish to flash.
 
InsaneNutter,
I have corrected the CPU key and made another modified nand before flashed it to xbox, so I dont think this is the problem. I got some bad block errors when flashing the new nand with nandflasher 360, as you can see at the image attached to my post, should I not be aware with it? As you also can see at the image, I have a 256mb jasper (I was wrong for the first time, when I said I had a 512mb jasper), but I have used all these correct information when made the modified nand, so I really don't know what happened. I have read some information about where xell is placed in xbr and freeboot nand versions, and how that is different it should result in a non bootable xbox, should I not be aware of that? There is also the JTAG Tool program, is it better than NANDPro? I also remember that reading the full nand using lpt cable take way too long time to finish, does it also happens when writing?
 
I have found the older files I generated when I first installed xbr to my xbox. I followed the tutorial "Complete Guide On Flashing Xbr With Xellous, includes commands for big block nands", from xbox-scene forum (I dont know why I get an error everytime I paste the link to the tutorial here). I copies of all the files, including full nand backup (264mb downloaded through web browser and xell), kv.bin, config.bin, etc, all tripple downloaded and checked with no differences found between them. Should these files be helpfull in some manner?

As my xbox is a 256mb jasper, I have a LPT cable and the name of my moddified nand file with freeboot is updflash.bin, the correct nandpro command is:

NandPro lpt: -w256 updflash.bin

Is that correct? Is it safe to do this with the LPT cable, or I really need to look for a USB SPI flasher?

Sorry for the posts in a row, but a 3rls on a previously working xbox have a huge psychological impact ehehehehe, and I am really afraid of screw up this permanently.
 
This is the first time I have attempted to update myself and can't quite figure out how to install the dashlaunch 2.5. I read the readme text when I downloaded but am lost. Any tips you can give me would be great.
 
the_GUNN_man said:
This is the first time I have attempted to update myself and can't quite figure out how to install the dashlaunch 2.5. I read the readme text when I downloaded but am lost. Any tips you can give me would be great.
Click to expand...

Unzip dashlaunch and copy it to your USB drive

Download this ISO: here

Unzip it and burn it to a disc

Put it in your console and go to the game library

You should then have XEX Menu.

jtag-hdd5.jpg


Load it up, once in XEX menu use the left and right bumpers to navigate to the USB stick.

Now find the Dashlaunch folder, go to that and select the install folder and load the default.xex, that will start the dash launch installer.
 
unnamed said:
I have found the older files I generated when I first installed xbr to my xbox. I followed the tutorial "Complete Guide On Flashing Xbr With Xellous, includes commands for big block nands", from xbox-scene forum (I dont know why I get an error everytime I paste the link to the tutorial here). I copies of all the files, including full nand backup (264mb downloaded through web browser and xell), kv.bin, config.bin, etc, all tripple downloaded and checked with no differences found between them. Should these files be helpfull in some manner?

As my xbox is a 256mb jasper, I have a LPT cable and the name of my moddified nand file with freeboot is updflash.bin, the correct nandpro command is:

NandPro lpt: -w256 updflash.bin

Is that correct? Is it safe to do this with the LPT cable, or I really need to look for a USB SPI flasher?

Sorry for the posts in a row, but a 3rls on a previously working xbox have a huge psychological impact ehehehehe, and I am really afraid of screw up this permanently.
Click to expand...

You can flash your nand via LTP, a USB solution will just be much much faster.

Try doing this tutorial again but using your original nand to obtain the data from to build your image.

You could also try putting your smc_config.bin, a decrypted KV.bin and a a decrypted SMC.bin in the mydata folder.
 
Worked like a charm. Thank you very much.

Now I cannot get the avatars to update. I have put it on a USB and on a cd and nothing works. It does not ask me to update.
 
the_GUNN_man said:
Worked like a charm. Thank you very much.

Now I cannot get the avatars to update. I have put it on a USB and on a cd and nothing works. It does not ask me to update.
Click to expand...

Add this to your launch.ini file

noupdater = false
Click to expand...

A feature of Dashlaunch is to ignore system updates so you dont accidently update with a newer update.

When you have your avatars set it to true again.
 
I looked in there and it was already was set to true. I think you meant to say set it to false, then update and then turn it back. That is what I did and now I am good to go. Updating to the new kernel went very smooth for me. It was not knowing I needed the XEXMenu disc to be able to get to the dashlaunch file I needed to install. Then installing the avatar update was just a matter of going in there and turning the noupdater to false so it would accept an update.

Thank you for all you help and your patience.
 
InsaneNutter,
Thanks for your help.
I made the process using my original nand dump (the one I have downloaded through xell and webbrowser, before xbr was installed). Now I ended up with a completely different resulting updflash.bin file (I have compared this to the other one I made with the nand dump aquired by NANDFLASHER 360, using nandpro feature). Also looking to the log files fbBuild created, I have some remmaping warnings for the supposed erroneous one, which not occured to de modified nand using the original nand dump). Should this be the problem? There is some way of detecting this newer modiffied NAND is correct before flashing it to xbox? I've made a reproduction of the log file:

"------ Checking .\mydata\nanddump.bin ------
Loading NAND dump...done!
NAND dump is from a big block machine
NAND dump uses big block controller
parsing dump into user and spare...
block 0x8 was remapped to block 0x1, entering remap instance 1
block 0x10 was remapped to block 0x2, entering remap instance 2
block 0x18 was remapped to block 0x3, entering remap instance 3
block 0x20 was remapped to block 0x4, entering remap instance 4
block 0x28 was remapped to block 0x5, entering remap instance 5
block 0x40 was remapped to block 0x8, entering remap instance 6
block 0x48 was remapped to block 0x9, entering remap instance 7
block 0x50 was remapped to block 0xa, entering remap instance 8
block 0x58 was remapped to block 0xb, entering remap instance 9
block 0x60 was remapped to block 0xc, entering remap instance 10
block 0x68 was remapped to block 0xd, entering remap instance 11
block 0x70 was remapped to block 0xe, entering remap instance 12
block 0x78 was remapped to block 0xf, entering remap instance 13
block 0x80 was remapped to block 0x10, entering remap instance 14
block 0x88 was remapped to block 0x11, entering remap instance 15


**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************

done!
cleaning up stray remaps
done!
--remap summary--
0: source: 0x0008 dest: 0x0001
1: source: 0x0010 dest: 0x0002
2: source: 0x0018 dest: 0x0003
3: source: 0x0020 dest: 0x0004
4: source: 0x0028 dest: 0x0005
5: source: 0x0040 dest: 0x0008
6: source: 0x0048 dest: 0x0009
7: source: 0x0050 dest: 0x000a
8: source: 0x0058 dest: 0x000b
9: source: 0x0060 dest: 0x000c
10: source: 0x0068 dest: 0x000d
11: source: 0x0070 dest: 0x000e
12: source: 0x0078 dest: 0x000f
13: source: 0x0080 dest: 0x0010
14: source: 0x0088 dest: 0x0011
-----------------"

Again, thank you very much.
 
I`ve just finished flashing the image I made from my original nand backup... and it didnt work, still got 3rls, no xell either... I will try to reestablish the backup I made with NANDFlasher 360 and see if I can go back to xbr... if I dont, I think I will need a usb hardware to flash the original image, flashing 256mb with lpt cable will take soo long to finish I think... Any Ideas?
 
I have been looking in to this for you, I think the problem could be freeBOOT has a different layout compared to XBR, so XeLL is in a different place on the nand. I'm not 100% sure though as i never used XBR, i started out on FreeBoot 9199.

People on 9199 or above appear to have no problems upgrading. Maybe try building a FreeBoot 9199 image with this tool https://digiex.net/guides-reviews/c...xbox-360-freeboot-0-032-9199-dash-kernal.html and just see if that works, if that does we can try upgrade from there. You should not have to go to 9199 first, however i'm lost as to why your having no luck.

Also to make flashing quicker try just flashing Xellous to your nand "nandpro.exe ltp: -w16 xellous.bin" if you can boot in to that you can flash an updflash.bin loads quicker from your USB stick.

Your backup made with NANDFlasher 360 should work fine though if flashed back however, I have to dash right now but that might be something to look in to.
 
ok insanenutter, latter I will try this option, thanks again :D

I also have found these others 2 tutorials, I think I will try them if FreeBoot ToolBox Maker by BestPig failed, what do you think?
Easy XBR to Freeboot. - Se7enSins Forums
[TUT] How to Update to freeBOOT .032 with just XBR nand - Se7enSins Forums

But I`ve seen other people in xbr (others topics) using this FreeBoot ToolBox and everything worked for them, I dont see why it should not work for me...

Then, supose that the freeboot toolbox resulting nand image i will flash works, then I have to repeat your tutorial all the way down again to have it updated to 13604 is that right?

thank you very much
 
Wohooo! I am at 9199 now! Thanks InsaneNutter! I used my original nand dump instead, I really dont know if it would work with the xbr3 dump...
Now assembling everything back again, and I will try to update to 13604 with your tutorial! Again, thank you very much!

Just to record, as I was with xellous (made everything much easier then the LPT cable), I tried to do your tutorial starting with my original full dump, before go to 9199... It didnt work, I dont know why, as it is a original dump, without xell,xellous,xbr,nothing... Now I will try to dump 9199 nand with NANDFlasher 360 and follow your tutorial... Then I will come back with news...
Thanks Again (I'm very happy Xbox is back to life)
 
You must log in or register to reply here.
Top Bottom