Help with updating 14699 (RGH)

[andynov123]

I have just flashed my glitch console with 14699 (I was updating from a previous version). Everything was working fine before this. Now I am reading blackwolf's guide and it says to get the actual ms 14699 and install that. I have renamed it $systemupdate and $$ystemupdate but none seem to respond and put it in root of FAT32 drive. I am also having another issue where I can't load fsd like I always used to be able to? Is that because of this system update that I need to install? Basically what happens now is whether I try to load fsd or not (I have it on external with all other content) it will go directly to 14699 dash like it was retail. I was also planning on updating dashlaunch but I read I'm supposed to do that after the systemupdate install. Please help.

 

[keil423]

The system update that you instructed to install is only to update the avatars and the kinect sensor. You dont even need it if you dont care about your avatars showing up.

Are you able to get into XEX menu? If so can you launch FSD from there or not?

 

[andynov123]

I would like to install the update and have kinect and avatars show up. As for xex menu, I never had that installed. Whenever I want to execute xex I just go to file manager. Either way, I need to figure out how to get this update installed. It is the only folder on the disc and from what I hear it should be working. I renamed it to the other way and still not working. Am I supposed to have the hard drive with fsd plugged in or not for this update to work? I'm confused as to why I can't get fsd to load automatically when my fsd external is plugged in. This has never been an issue before.

 

[cfull1]

You could try reflashing the 14699 image without dashlaunch installed (did you use multi builder?), then try to install the $systemupdate, then install dashlaunch.

I'm confused as to why I can't get fsd to load automatically when my fsd external is plugged in. This has never been an issue before.

Is there a launch.ini on the external drive that's overriding the internal one?


Also you could use quickboot to create a shortcut to fsd that will show up in nxe (to avoid using xexmenu to boot into fsd).

 

[andynov123]

I was able to get it done succesfully but now I notice a couple things. One is that when I go to the option for auto sign-in with fsd, it freezes my xbox. Also, my xbla save files seem to be gone and all have changed to trial version when before I had them unlocked. As I said before, I was able to load the update and then put on dashlaunch 2.29.

 

[cfull1]

Not sure about auto-sign in. Maybe try setting it through nxe?

Yeah ms changed their "keysigner". I think that's what it its called. It's mentioned in the dashlaunch readme.

Most, if not all, of my xbla went to trial too. I copied them to my computer and used YarisSwap v6 (v9 buggy). This removes the console id from the file. Copied them back to the xbox and they worked great. Also I disabled the contpatch in my launch.ini

 

[DayvG]

all have changed to trial version when before I had them unlocked. As I said before, I was able to load the update and then put on dashlaunch 2.29.

I can answer this, change contpatch to false in launch.ini. Had me stumped a few days ago. Credit to dgenx for that one.

 

[x360ccm]

I can answer this, change contpatch to false in launch.ini. Had me stumped a few days ago. Credit to dgenx for that one.

i like the bit that you can answer it :biggrin:

i take no credit for it tho as.i had the same issue and i just search the net for it and it worked for me when 2.29 was out.:rolleyes2:

 

[DayvG]

I need to brush up on my googling skills then, I was at it for hours!!! Still, don't be so modest and take the credit lol

 

[andynov123]

I actually saw another thread where somebody said they went down to 2.28 after it happened to him. After that the files went back to unlocked. I couldn't find 2.28 but I used 2.27 and that fixed it. Maybe later I will go to 2.29 again and change contpath. Can somebody here give the recommended settings for 2.29? I know a lot of it is preference, but the main ones I would like to know about are in regards to live and not allowing it to access it.

 

[cfull1]

Here's mine. Pretty much all the recommended settings are default so you don't need to include them.

Default settings block live, but do not block all dns so fsd still works correctly.

The only ones in there that aren't default are: pingpatch, fatalreboot, regionspoof, and autoshut.

 

[x360ccm]

i set mine to this

[QuickLaunchButtons]
BUT_A = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_B = Hdd:\Freestyle\default.xex
BUT_X = Mu:\Freestyle\default.xex
BUT_Y = FlashMu:\Freestyle\default.xex
Start = UsbMu:\Freestyle\default.xex
Default =
[Settings]
nxemini = true
pingpatch = true
contpatch = false
fatalfreeze = false
fatalreboot = true
regionspoof = true
dvdexitdash = false
xblaexitdash = true
nosysexit = false
exchandler = true
noupdater = true
debugout = false
liveblock = true
livestrong = false
remotenxe = false
nohud = false

 

[andynov123]

I still don't fully understand the quicklaunch part. Can somebody please elaborate? I'm guessing it's like a shortcut to a .xex file?

 

[cfull1]

I still don't fully understand the quicklaunch part. Can somebody please elaborate? I'm guessing it's like a shortcut to a .xex file?

Yeah exactly. You know how you return to the nxe dashboard by hitting the xbox button, hitting Y, then hitting A to confirm? Well after you hit A, just hold one of the quicklaunchbuttons and you will go straight to that file/game/xex specified in the launch.ini instead of the nxe dashboard.

Note: You need to reboot your xbox for the changes to take effect.

 

[x360ccm]

i just press the big x button.tape the y then tap the b then i in fsd.