Post by: alexthegr824 on December 10, 2011, 08:38:00 AM
Post by: pudink on December 10, 2011, 08:56:00 AM
QUOTE
Updated patches to Latest Dashlaunch v2.27 Patchset.
What does this exactly mean guys ?
Does it mean we dont have to install dashlaunch ? Is it pre-installed?
Post by: effbee05 on December 10, 2011, 09:43:00 AM
Post by: darayden on December 10, 2011, 09:45:00 AM
Thanks alot man - easy peasy!!!
Post by: KarlosB on December 10, 2011, 12:35:00 PM
Brilliant App....updated fine using Rawflash v3 and Xell Reloaded.... just followed the handy instructions at the end of the creation and it was done within 2 minutes.
Dashboard booting into 2.27 and running 14699 perfectly, cant ask for any more.
Thanks for making this, and even better for recommending the use of Rawflash.
Post by: miller420 on December 10, 2011, 01:43:00 PM
Post by: XE2010 on December 10, 2011, 06:09:00 PM
BTW see below
360_Multi_Builder_v0.6 on 10/12/2011
----------------------------------------------------------------
- Removed the pre-patched RGH smc files that were used in version 0.5
- Now using xeBuild to patch the RGH/smc files for better RGH images compatibility.
Credits to xeBuild / Dashlaunch devs, especially cOz.
Post by: rastiemon on December 10, 2011, 06:55:00 PM
Also you need to change the folder $systemupdate to $$ystemupdate for it to pick up sometimes because of a dashlaunch protection I believe.
Post by: aubrey_76 on December 11, 2011, 09:10:00 AM
"Put the file "nanddump.bin" in "\Data\my360" folder for Xell/ECC image build"
"Put the file "cupkey.txt" in "\Data\my360" folder for RGH/Jtag image build"
I have a Falcon JTAG so do I only do the second one or do I do both of the above steps? I have my original nand that is named "orig" so do I need to rename it to something specific to work with this program?
Sorry for all the questions, I just finished one tough semester and International Relations fried my brain a bit.
Post by: coreyinoz on December 11, 2011, 11:50:00 AM
QUOTE(aubrey_76 @ Dec 11 2011, 05:10 PM) 
When I open the program, it displays the following:
"Put the file "nanddump.bin" in "\Data\my360" folder for Xell/ECC image build"
"Put the file "cupkey.txt" in "\Data\my360" folder for RGH/Jtag image build"
I have a Falcon JTAG so do I only do the second one or do I do both of the above steps? I have my original nand that is named "orig" so do I need to rename it to something specific to work with this program?
You need both files, they are separate.
nanddump.bin is your original nand
cpukey.txt is a text file with your CPU key inside it (go figure
)If you don't have a cpukey.txt file, make one.
Assuming you are in Windows, create a file in notepad and call it cpukey.txt. Add a single line to that file - your CPU key. If you don't know your CPU key, start your 360 with the eject button so that Xell boots up. It will show your CPU key on the screen. Write it down, and save it in your file... keep it handy for next time, because it doesn't changed and you'll need it next time you want to update too.
Post by: alexthegr824 on December 11, 2011, 03:32:00 PM
Post by: ravendrow on December 11, 2011, 06:19:00 PM
Post by: Julets on December 11, 2011, 06:23:00 PM
QUOTE(aubrey_76 @ Dec 11 2011, 11:00 PM)
Thanks for the tips. Now my JTAG is updated to the latest dash. I dont have an avatar anymore and I know I have to run the official MS update to get them back. So i downloaded the official update, unrared it, put the "$systemupdate" folder on the root of a USB and the JTAG does not recognize it. Is there something special I have to do to run the official update to get avatar and Kinect support back?
thanks
Just reflash it WITHOUT dashlaunch installed, run the $systemupdate, then install dashlaunch. Much simpler, not sure if update is blocked by default with dashlaunch or not. Also if I remember correctly that unless you have a launch.ini on your storage already, the best options to use with dashlaunch are not default (ping patch, block m$ live, no NXE, etc.). So I'm not sure at all why you should install this into the flash image.
Also the update just writes the required files, and doesn't need a reboot to finish. So when it goes to reboot, I usually turn it off manually or else I sometimes get a E79 if I let it soft reboot.
Post by: aubrey_76 on December 11, 2011, 06:49:00 PM
QUOTE(alexthegr824 @ Dec 11 2011, 05:32 PM)
"Also you need to change the folder $systemupdate to $$ystemupdate for it to pick up sometimes because of a dashlaunch protection I believe."
I tried this and it didnt work. I will just wait until the update is put on a future game and do it that way
Post by: rastiemon on December 11, 2011, 07:25:00 PM
But the combination of either trying $systemupdate or $$ystemupdate always works just keep messing with it. It'll pick up after a few tries trust me.
Post by: rastiemon on December 11, 2011, 07:56:00 PM
So first check if your avatars are showing up
Second plug in the kinect and see if it prompts you for a update.
Also I am sure this is common sense but make sure you are using 14699 update if you are on 14699 etc.
Post by: mac-life on December 12, 2011, 02:13:00 AM
QUOTE(steplay29 @ Dec 11 2011, 07:31 PM)
hi guys was just wondering does the nand dump have to be an original one or could you use a dump of your current one (13604).i used a dump of my last one to upgrade to (13604)think prog was ggbuild.i have a jasper 512mb jtag.i put my nand dump and cpu key in different folders (forget names)and ran a command line for my jasper to create new image.
Does not have to be the original dump. Just use flash360 tool to make an nanddump file of your current dash and create the 14699 image using that. Then flash the 14699 dash with flash360 keeping current settings. Worked perfectly on an xenon. Also nanddump.bin and cpukey.txt goes in my360 directory.
Post by: wlintek on December 12, 2011, 02:42:00 AM
i have two RGH Xbox to update. the first one i restored to stock 13604, then updated to stock 14699 via USB stick, then re-dumped the nand and created the 14699 RGH image with the dump. it finally worked for me.
but the second one, i tried both 13604 hacked and original to create the 14699 image, although the creation went fine, the Xbox just does not boot with the image i created.
Post by: steplay29 on December 12, 2011, 06:18:00 AM
p.s sorry for the double post guys.posted this in thread about version 0.3 aswell.
Post by: danthaman673 on December 12, 2011, 09:01:00 PM
Post by: Midnight Tboy on December 14, 2011, 06:06:00 PM
That way would keep all settings like kinect configuration, blocked live settings etc
Post by: steveo1978 on December 14, 2011, 06:36:00 PM
QUOTE(drysset @ Dec 13 2011, 07:06 AM)
Newer used multi builder before.
Should I install FSD before I update my JTAG with dashlaunch preinstalled in the nand image?
And I just flash my JTAG with flash360?
Use multi builder v0.7 its easy to do it either way.
@Midnight TboyI am not sure where those setting are actually saved but they maybe not effected by flashing the NAND.
Just if either of you have a 256MB or 512MB Make sure you backup everything.
Post by: HiGhLaNdR on December 19, 2011, 04:54:00 PM
QUOTE(steplay29 @ Dec 12 2011, 01:18 PM)
hi just updated a jasper 512mb with the new version 0.7 and it worked a treat even for me lol.am going to to the kids two falcons v3 but when i run the progam beside option 5:it says a falcon with cb 5771,but my two falcons are 5770.just wondering is it ok to go ahead and flash this or to wait?
p.s sorry for the double post guys.posted this in thread about version 0.3 aswell.
Had the same problem, it even changed the smc version to 2.3 instead of 1.6. The xebuild Gui v1.1 did the job, kept the 1.6 and the cb 5770.
My 5 cents.