ANSWERED 14699 New Profile Creation Freeze

[GryphZer0]

I just got a new RGH Jasper 512, installed a new HDD, clean install of FSD 2.2 and Dashlaunch 2.29(well I used the new DVD FSD installer) and whenever I go to NXE and create a new profile it locks before the avatar creation where it says "Updating Profile"

Of course I searched and found
https://team-xecuter.com/forums/showthread.php?t=79147
and there's really no answers and I can't reply there yet.

I got the bright idea to hold RB before that and it actually seems to work.. so maybe if I change Dashlaunch to default to NXE? (Can you default to NXE? just take out the Default=hdd:\fsd\default.xex in the launch.ini?) Though I like FSD 2.2 as default..

 

[dontdr0ptheS0AP]

I would go back to dashlaunch 2.28, I have read in several places v2.29 was buggy.

In your launch.ini, you leave default blank and it will boot to the retail dash, eg.....

[QuickLaunchButtons]
BUT_X = Hdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_Y = Usb:\Freestyle\FreestyleDash.xex
Default = 
[Settings]
nxemini = true
pingpatch = true

 

[jtag360.nl]

You must update your HDD with the official M$ $sytemupdate of the dash that your Xbox is running on(14699).

 

[GryphZer0]

Thanks dontdr0ptheS0AP I will give dashlaunch 2.28 a try and see if that works any better.

I did do the $$ystemupdate already, and have avatars and props working fine, it's just when I create a new account it locks up.

 

[xbox360 hacker]

I notice in your original post you got the link to the thread i started. Sorry i cant be of any help what i do know though it doesnt matter what version of dash launch or freestyle dash you use the same thing happens but removing freestyle fixes the freeze problem. This bug has just shown its face in the new 14699 dash as if i leave all settings as is and revert back to dash 13604 everything works fine no freezing. Another thing that happened to me was my original profile corrupted beyond repair shortly after the new dash update not sure if this is related but seems a bit of a coincidence. Hope you have better luck resolving this issue and if so would you please report back as i would be very interested in your findings.