can u make original nand with a hacked 9199 or use hacked 9199 for hacked 12611

[xboxbreaker]

Just start from scratch.
Get the blank fbbuild folder. Extract the 12611 dash files straight into the correct fbbuild folder. Then follow the read me's exactly taking the files from the existing 9199 image.

[l_oliveira]

Man you just need the keyvault (kv.bin) and SMC settings section (smc_config.bin) files. All the rest of the console specific files fbbuild will *create* for the image.

[uk_dan2k]

hi all,

after giving up on updating my dash, i started updating my console apps instead and came across the same problem which could be a clue i hope.

updating from dashlaunch 1.0 to anythin newer for my 9199 dash causes the same problem of on booting up no video just green power l.e.d.
i went through all the options it gives you to find out which one causes the problem and it's the last one "Do you want to upgrade your freeboot patches"

the adding of newer freeboot patches screwes it up, so what if this hacked 9199 i have is not even freeboot and xbr instead, would trying to add freeboot patches to a xbr flash cause these problems, if so i guess all the tools i been trying keep updating to newer freeboot patches as well.

i hope its something to do with this, and if it is does anyone know any guides for updating 9199 xbr to 12611 freeboot ?

[bluespace77]

9199 xbr to 12611 freeboot ?

There is no 9199 xbr, if you have a 9199 JTAG then you have FreeBoot 0.032.

I've upgraded a few consoles to freeBoot 0.04 , and in all of them I used a fresh dump of the NAND through Xellous (ie freeBoot 0.032) as the source NAND. I find that easier than using the original NAND as it keeps the fan settings. You don't need the original NAND. If you;re really struggling, try the easy freeboot tool.

As for DashLaunch, try using 2.00 - 2.02, as it does state in the readme 2.03+ are only compatible with freeBoot 0.04. I prefer to build the freeBoot image with dashlauch rather than later running the dashlaunch installer, just drag launch.xex and lhelper.xex into the data directory before building the freeBoot 0.04 image. I'd also check for bad blocks.

[uk_dan2k]

Man you just need the keyvault (kv.bin) and SMC settings section (smc_config.bin) files. All the rest of the console specific files fbbuild will *create* for the image.

fbbuild wont work without smc.bin

[l_oliveira]

Man you just need the keyvault (kv.bin) and SMC settings section (smc_config.bin) files. All the rest of the console specific files fbbuild will *create* for the image.

fbbuild wont work without smc.bin

I didn't mention that BECAUSE ANY ONE SHOULD KNOW that a XBOX360 won't run without the SMC firmware.

[uk_dan2k]

There is no 9199 xbr, if you have a 9199 JTAG then you have FreeBoot 0.032.

I've upgraded a few consoles to freeBoot 0.04 , and in all of them I used a fresh dump of the NAND through Xellous (ie freeBoot 0.032) as the source NAND. I find that easier than using the original NAND as it keeps the fan settings. You don't need the original NAND. If you;re really struggling, try the easy freeboot tool.

As for DashLaunch, try using 2.00 - 2.02, as it does state in the readme 2.03+ are only compatible with freeBoot 0.04. I prefer to build the freeBoot image with dashlauch rather than later running the dashlaunch installer, just drag launch.xex and lhelper.xex into the data directory before building the freeBoot 0.04 image. I'd also check for bad blocks.

tried using fbbuild and either get christmas lights followed by e55 or my old problem no video with green power led on.

tried using jtag tool = same green power led again

tried easy freeboot tool by bestpig = green power led again

also tested for bad blocks and nothing came up

[uk_dan2k]

I didn't mention that BECAUSE ANY ONE SHOULD KNOW that a XBOX360 won't run without the SMC firmware.

lol i have been using it any still getting probs.

i've tried an smc from my current working flash that has 2 alt jtag points
i've tried an smc from my old working flash before the 2 alt jtag points
tried and smc from an unhacked clean donor falcon nand

[uk_dan2k]

just a quick question might be dumb lol.

mydata folders readme file and i quote:-

none of these should be necissary but can be placed here for the builder,
must be provided in pairs of bin and meta, currently only encrypted bins are supported:
---------------------------------------------------------------------------------------
-crl.bin / crl.bin.meta             (encrypted) (alternately you can use crl_enc.bin)
-extended.bin / extended.bin.meta    (encrypted) (alternately you can use extended_enc.bin)
-odd.bin / odd.bin.meta             (encrypted) (alternately you can use odd_enc.bin)
-secdata.bin / secdata.bin.meta       (encrypted) (alternately you can use secdata_enc.bin)
-dae.bin / dae.bin.meta             (encrypted) (alternately you can use dae_enc.bin)

i don't have these files not sure if thats causing a problem
i also have the mobileB.dat file if i need that or not.
also for "data" folder

put firmware files here, including bootloaders
optionally you can include launch.xex and lhelper.xex here
if a version that matches the kernel exists

when it says firmware does it just mean 12611 files and as for bootloaders does that just mean dashlaunchs launch.xex, launch.ini, ihelper.xex?

[bluespace77]

tried easy freeboot tool by bestpig = green power led again

Easy freeBoot isn't by bestpig, his is FreeBoot Toolbox Maker. I've found easyfreeboot to be the quickest for quickly updating a few consoles. However, these are all just GUI frontends for fbBuild used to save you a little bit of time. They are still using fbBuild beneath, so if in doubt run fbBuild directly especially for Jaspers.

i don't have these files not sure if thats causing a problem
i also have the mobileB.dat file if i need that or not.

You should have these files, as otherwise 9199/ freeBoot 0.032 wouldn't be working, they are present in every 0.032 image I have. L' on here says you don't need them and it generates it's own if they are missing. I believe it's been said somewhere on here to have a dae.bin, your console would needed to been taken on live before it was JTAG'ed. I believe it's also been said to get the 12611 dae.bin you need to run the official dashboard update (with U6T1 bridged to prevent it blowing the eFuses), dump the NAND and get the dae.bin,


You don't unless you specically dump it, I believe it's just the configuation and isn't needed unless you specifically want. I've never flashed the config to a NAND.

when it says firmware does it just mean 12611 files and as for bootloaders does that just mean dashlaunchs launch.xex, launch.ini, ihelper.xex?

The 12611 from xbins gets extracted to the data directory. Launch.ini must be placed on the root of the storage device. launch.xex and lhelper.xex must be placed in data directory.

[uk_dan2k]

managed extract some missing files from my dump using 360 flash tool, but still don't have a "dae.bin"
complied it anyway and sent it to my harddrive where i got flash360.

when i select "A" update nand using updflash.bin" and then "A" again keep current KV and config it comes up with the error.

nands are not zeros paired, ignore or swap nands - now i usually ignore, flash and unable to boot up, is there any zero pairing i can do?

[phonsey]

I didn't mention that BECAUSE ANY ONE SHOULD KNOW that a XBOX360 won't run without the SMC firmware.

lol i have been using it any still getting probs.

i've tried an smc from my current working flash that has 2 alt jtag points
i've tried an smc from my old working flash before the 2 alt jtag points
tried and smc from an unhacked clean donor falcon nand

its nothing ur doing wrong m8 its just that ur console has kv hashing which means u cant update because of this $#!tty freeboot some kid made that isnt really stable and only half functional. there is only 2 things that can sort this 1. u have to wait until a new patch comes out to remove this chec! 2. Build a better more stable Freeboot

[uk_dan2k]

its nothing ur doing wrong m8 its just that ur console has kv hashing which means u cant update because of this $#!tty freeboot some kid made that isnt really stable and only half functional. there is only 2 things that can sort this 1. u have to wait until a new patch comes out to remove this chec! 2. Build a better more stable Freeboot

any ideas on how to build a more stable freeboot

[l_oliveira]

All problems come from things beign used wrong.

The current rebooter is fine. All my consoles (many of them) work properly (save for hardware issues). Now, even with their proper/correct SMCs (thanks Blackaddr).

Few things to consider:


DO NOT USE FAILbox, failkit or any other spoonfeeding tool to make your flash. The command is easy enough to be typed by hand or inserted in a small batch file for command prompt.

AN PROPERLY fbbuild or freeboot image WILL RUN ON ANY CONSOLE of matching motherboard type, regardless if the CPUKEY for the physical CPU is matching or not.

If you mismatch CPUKEY for the KEYVAULT you're likely to have CHRISTMAS LIGHTS on hashed keyvaults. Otherwise it's like if it was an "unbanned" Xenon with an changed keyvault.

You DO NOT NEED security files for fbbuild as it's perfectly capable of generating them. It will use if you provide them, though. For freeboot you're obligated to provide them, but it can be from donor system.

If used, the security files should match the keyvault and CPU KEY.

AP25 checks only seem to work on machines whose KEYVAULT is hashed.

What I am calling "KEYVAULT CPUKEY" is the CPUKEY used on the virtual fuseset, not the real CPUKEY.

[bluespace77]

its nothing ur doing wrong m8 its just that ur console has kv hashing which means u cant update because of this $#!tty freeboot some kid made that isnt really stable and only half functional. there is only 2 things that can sort this 1. u have to wait until a new patch comes out to remove this chec! 2. Build a better more stable Freeboot

That's disrespectful. It's absurd to call this 'half functional'.

I've updated 9 consoles to 12611, and none of them have issues. If people are having issues with the KV, then they shouldn't be swapping KV's.

If that's your opinion of the person responsible for fbBuild, don't use it!

[cory1492]

It seems to me that more often than not there are two issues people are running into:
- they are using a donor keyvault and are either not building the image with the cpu key of the machine the keyvault came from, or using a donor from a different motherboard/OSIG. Considering all the banned consoles from live hacking, I'm honestly surprised no one has started a repo of banned donor keyvault+matching cpu key by now - guess it just goes to show how much folks who were running through hoards of keyvaults care about "the scene"
- they refuse to comprehend the automated flashers may not be handling bad blocks correctly, especially when it's a "soft" bad block

Sorry to say it, but neither of these cases points to unstable software on the builder side - it does exactly what it is supposed to which is build working NAND images from user supplied data and info. If the data/info is incorrect, how is the tool supposed to know? Also, as it doesn't flash the image to the console (which is also left up to the user), nothing related to that can really place blame on the builder. I've done paired (donor kv)+(donor machine cpu key) swaps on both my jasper big block (with another jasper of the same mobo type and OSIG as the drive has) and my falcon (with another falcon of the same mobo type and OSIG as the drive has) and have had absolutely no issue so long as I follow the note in the readme.

phonsey: Begging or insulting trying to get a KV sig check patch makes me wonder how the rapidly depleting oxygen supply is being misappropriated... do the work yourself. Just try even, before you troll. IMHO there are heaps more blame to be had for making it easier to violate LIVE than there ever possibly can be for not including a patch for someone who did not back up and keep the original data for the console. If you bought it that way, who'd you buy it from? Because they deserve a helping of that blame far more than the author behind fbbuild, kid or not.

l_oliveira: the tool does not create those files, what happens is any errors from those files missing or failing to match up with the hardware are patched out of the security routines. Not using the files, or even just using 0byte dummies has the same effect as using all the correct ones - which should be none at all if nothing was missed in the patching :p The console itself will create extended.bin if it's missing.

uk_dan2k: I'm honestly still scratching my head as to the thread OT - are you trying to make a rebooter/9199/12611 image or a retail 9199 image? Because a retail 9199 image with the proper CB isn't going to run on the console unless you burn another LDV efuse.

[uk_dan2k]

uk_dan2k: I'm honestly still scratching my head as to the thread OT - are you trying to make a rebooter/9199/12611 image or a retail 9199 image? Because a retail 9199 image with the proper CB isn't going to run on the console unless you burn another LDV efuse.

yup this threads gone back and forth like a tennis match, my problem was i brought a pre hacked console. came with dash 9199 (seems cant be xbr so it must be freeboot). i use this console for testing and have a retail slim for online play etc.

i wanted to update the hacked 9199 to 12611 but the git whole sold it me never gave original dumps and can no longer contact him.
i originally tried updating with current dumps using nandpro / flash360 / fsd2 nand dumper then using jtag tool / bestpig tool / easy freeboot.
then tried more manual routes using fbbuild etc.

always end up with the stupied error on power up nothin boots just stuck with green power l.e.d. but xell bloody works.
some people blammed my solder skills - but if i reflash old hacked 9199 that boots fine.

then it was suggested trying to recreate an original using clean donor nand and injecting my kv etc and trying from there to make a 12611 - end up same error

when i open all these flash files in 360 flash tool they all seem fine, kv details are displyed etc - so im stuck at this roadblock for the last 3 weeks.

[l_oliveira]

I'll post something you can try, for keeping your current KV and config blocks:


Take your current working 9199 dump and do this with it:

Code:

nandPro image.bin: -R16 vfuses.bin 25 1

A 16384 bytes file called "vfuses.bin" will be saved. Within it you will have the whole dump of the virtual fuseset being used by the rebooter along with the patches data right after the virtual fuses.

This is what you want, inside the file:


00001000   C0 FF  FF FF  FF FF  FF FF   Àÿÿÿÿÿÿÿ
00001008   0F 0F  0F 0F  0F 0F  0F F0          ð
00001010   00 00  0F 00  00 00  00 00          
00001018   01 02  03 04  05 06  07 08          
00001020   01 02  03 04  05 06  07 08          
00001028   09 0A  0B 0C  0D 0E  0F 10          
00001030   09 0A  0B 0C  0D 0E  0F 10          
00001038   FF FF  00 00  00 00  00 00   ÿÿ      
00001040   00 00  00 00  00 00  00 00          
00001048   00 00  00 00  00 00  00 00          
00001050   00 00  00 00  00 00  00 00          
00001058   00 00  00 00  00 00  00 00                


Where underlined numbers represent the 1st half of the key (it's repeated twice) bold represents the second half of the virtual CPU key (again repeats twice) so ignore the second.
In this example the virtual CPUKEY is 0102030405060708090A0B0C0D0E0F10.

Set the key on fbbuild my_data folder as "0102030405060708090A0B0C0D0E0F10" (in fact use the key you recover from your dump using this method) which should match the keyvault you have.

[phonsey]

that not what i need m8 i already knew about that and changing anything in that will have no differents to the outcome of the nand! the virtual fuses is at offset 0x99aa0 which contains ur cpu key etc. the kv hash has to be complied into the patchs file b4 u create the nand! if the kv hash isnt removed then ppl like me cant run the lastest dashboard! i had a corrupt kv when i was building freeboot 0.30 so i had to use a donor!   does any1 no the code source to removing it?

[uk_dan2k]

checked that and fuses matches the same cpu key i been using that i pulled of xell