My son broke my RGH by updating to 16202, I fixed it, but...

fnsubgenius

Full Member
May 24, 2006
36
0
My son decided to update the dash of my 15574 to 16202 and effectively hosed dashlaunch and the console would only boot to NXE.

I checked the LDV and decided to just use the original updatedump.bin via XELL to reflash and see if that would fix it.

So far so good. I booted NXE and loaded XEXmenu in the Content folder of a USB, and XEX booted, installed Dashlaunch again, FSD boots as default.

Now...why does the Dash version still report as 16202 from system info when I used a flash I KNOW contains 15574? I am missing some magic here.

Dashlaunch got hammered with the update, but by going to the apps folder and using the old installer for dashlaunch, it fixed it.

How does dashlaunch work, does it reside in flash? Does the ini reside in flash as well? I don't know how this xbox is working at all TBH.

-Fn
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
If it works, I dont see what the problem is. The real question is how did your son try to update it? I would assume if he used a game update, or usb update, that the console would have bricked until the nand was reflashed,and that xell would be erased. The logical explination is he overwrote the updatedump.bin, and didnt include dashlaunch patches when creating it.

As for the dashlaunch patches, They are patches that are embeded into the nxedash, that are configureable via ini file. There is a launch.ini file in the nand, and it is used when 1 cannot be found on HDD,or USB, or CD for that matter.

Also, since u updated, u really should create a new image with the latest dash, so this isnt a problem in the future. The new Xebuild(Included in J-runner), And any dashlaunch 3.08+ make this really easy.
 
  • Like
Reactions: fnsubgenius

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
After reading just the first line, it's obvious all that happened was an image was built without dashlaunch patches. You could have just ran dashlaunch installer to reinstall them.

The image wasn't wrong - do you really think it would have booted at all?

If it's on 16202 then it's on 16202 - whatever you thought you did, you did wrong or didn't do at all. There's no magic happening.

I'd personally just update to 16547 anyways, since new games will eventually need it.
 
  • Like
Reactions: fnsubgenius