hi i am trying to update to the latest 13599 dash but when i get to the stage where i put my cpu key in i get (could not find a path of a path'xell\xellous.bin) problem.ive tryed easyfreeboot 5.31,5.32,5.33 but all do the same.does anybody know how to fix this problem
when i dump my nand using flash360 and put it on my desktop.i ran it through 360flash tool and the key vault (section on the right) all say bad key\kv.is this where the problem is? hope some one can help
Originally posted by arkie3: hi i am trying to update to the latest 13599 dash but when i get to the stage where i put my cpu key in i get (could not find a path of a path'xell\xellous.bin) problem.ive tryed easyfreeboot 5.31,5.32,5.33 but all do the same.does anybody know how to fix this problem
i've just solved this problem for myself. i was able to write a correct 13599 updflash using "coolshrimp's" jtag tool, i tried all the sneaky peanut freeboots and they all gave me the same problem. if you do not have windows xp, download a windows virtual machine of xp from microsoft, then download .netframework v2.0.50727, then download jtagtool from coolshrimp, use your original nand image and cpu key to create key...manually compare a working image to the new imagine using 360flash tool to see if the smc version is the same, if not go back and use the options (looks like a wrench) to change the smc type for writing the image. thanks to sneakypeanut (his software has only recently failed me) and thanks to coolshrimp for having a great alternative app.
Originally posted by arkie3: hi i am trying to update to the latest 13599 dash but when i get to the stage where i put my cpu key in i get (could not find a path of a path'xell\xellous.bin) problem.ive tryed easyfreeboot 5.31,5.32,5.33 but all do the same.does anybody know how to fix this problem
i have solved your problem, as well as mine my friend :). i had the exact same issue and tried every version of EFB from SnekyP...furthermor i had windows 7 which it didn't even work on, so here it goes.
download windows xp mode from MS (for win7 users) then download .netframework v2.0.50727 so the applications can run on your machine. then instead of using sneakypeanut's EFB, go and find Coolshrimp's jtag tool. rather than giving you errors about not being able to find xell, it will give you a properly written nand image. check all the options (looks like a wrench) to make sure the smc is right (confirm by comparing a working dump to the new image using 360flash tool). create a test image to see that you can, then compare. save the image as Updflash.bin and it's good to go. i checked my old working image for 13146 on 360 flash and then checked the new image and it came up as 13599 with the exact same smc, v2.3 for my zephyr.
also, anyone using the virtual machine, forget about importing anything saved on ur win7 to xp because it wont work, just download and update everything you need from the virtual machine, like u have a brand new computer.
Originally posted by arkie3: when i dump my nand using flash360 and put it on my desktop.i ran it through 360flash tool and the key vault (section on the right) all say bad key\kv.is this where the problem is? hope some one can help
on this note. all my stuff comes up as bad kv and all that as well, i'm pretty sure it just means that your xbox is banned. i'm pretty sure mine is banned. the image will still write just fine and the xbox will be fully playable.
just make sure when comparing images that the smc version is the same and that the original nand says retail (wtvr board) and the new freeboot image says 2.0 and the bottom 2 patches are 13599
you can save your stuff on your win 7 machine to a flash drive then after you update your VM then you can get your stuff off the flash drive on to you VM. just need to change one or two settings so the VM sees the flash drive.
