JTAG 16203

nosherfj

VIP Member
Nov 1, 2010
1,094
0
Manchester UK
gonna feel like a right tard now but seem to be having a issue updating to freeboot 16203.

1.created my updflash.bin as usual in latest jrunner.had include dashlaunch settings ticked.

2.placed on root of fat32 usb flash drive and eject started my 16MB jasper Jtag.Flash went ok and switched console off at end and removed power lead for 30 secs.

3.switched xbox back on and it booted fine the usual intro choose language and location ect.then clicked my profile and declined to sign into live.It loaded up nxe no probs.

4.but iam sure it should have just loaded up fsd3 first as it did before as my launch.ini is fine and it loaded up fsd3 fine on 16202 before this update process.

5.so i figured dashlaunch patch hasn't gone through properly. so instead of booting xex menu and then booting dashlaunch3.06 i just inserted my fsd3 installer cd and ticked download latest dashlaunch and install it.

6. this went ok but i did notice it only downloaded version 3.05 so the boys at team fsd3 could do with updating this bit.anyhow i started to configure the various dashlaunch bits but when i get to ping patch enable the system crashes. so i try again and this time don't alter anything and exit dashlaunch with the hope it will then boot fsd3 but it just boots nxe again.

when i boot fsd3 from xex menu the fan setting in fsd kicks in so i know my launch.ini is ok too.

so why am i having this issue.done this tons of times before. must admit my brain isn't working at optimum as i did this late at night.

tried reflashing the updflash.bin and doing it all again but still having same issue?
 

daretogo

VIP Member
Feb 4, 2011
294
33
Denver, CO
Isn't it dashlaunch that has the liveblock settings in it that don't allow a JTAG / RGH to connect to Live? Therefore if dashlaunch hasn't been updated to be compatible with the new 16203 kernel then it would make sense it could get on Live?
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Isn't it dashlaunch that has the liveblock settings in it that don't allow a JTAG / RGH to connect to Live? Therefore if dashlaunch hasn't been updated to be compatible with the new 16203 kernel then it would make sense it could get on Live?
That's true, but it would instantly ban the console's key vault.
 

daretogo

VIP Member
Feb 4, 2011
294
33
Denver, CO
For some reason you don't get insta banned, I was playing for a few hours before just to see if it was true
Wow. I'm thinking you have to be expecting a ban though? I mean, MSFT certainly can detect it I would imagine.

If systems can get online with 16203 without insta-ban it could mean a whole new world of in game XBL modding.
 

Spaz2203

VIP Member
Dec 17, 2011
690
0
Connecticut
team-xecuter.com
oh I'm 100% expecting a ban, i dont have any plans for a demon or anything on this console in the future, just figured id give it a go

edit - i'm trying to get on now but its saying theres a problem with my connection but no mention of a console ban YET....
 
Last edited:

madhaxer

VIP Member
Sep 27, 2012
879
0
Arkansas USA
MS hot patched this, and will probably have another dashboard in a day or two with more checks in place.
 

moco

VIP Member
Feb 3, 2004
458
0
Australia
What about the keystream? Has anyone DGX'd one to see if it still works on the new update. Seriously, the consoles lifecycle is coming to an end in regards to retail games somewhere in the near future. I dont get why they would even bother pumping out anymore updates now.
 

nosherfj

VIP Member
Nov 1, 2010
1,094
0
Manchester UK
thanks for the repies folks i really did think i was going mad or noobed it up again.not seen any news on this 16303 problem with dashlaunch 3.06.seems to be happening alot lately these dashlaunch updates (last one cus of blops) not that iam complaining.
 

BraveH43

VIP Member
Sep 13, 2008
1,514
0
Somewhere in the 'verse
thanks for the repies folks i really did think i was going mad or noobed it up again.not seen any news on this 16303 problem with dashlaunch 3.06.seems to be happening alot lately these dashlaunch updates (last one cus of blops) not that iam complaining.
Dashlaunch always requires updating on new dashes being released. Personally I would wait until new dashlaunch is released before updating. Otherwise you risk live bans from unintentionally connecting to live

sent using tippytalkytappa thingy
 
  • Like
Reactions: nosherfj

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
What about the keystream? Has anyone DGX'd one to see if it still works on the new update. Seriously, the consoles lifecycle is coming to an end in regards to retail games somewhere in the near future. I dont get why they would even bother pumping out anymore updates now.
Read the SYSTEM UPDATE thread. There's nothing which would stop the DGX working on existing consoles. Ever.

---------- Post added at 10:01 ---------- Previous post was at 10:00 ----------

Well there kind of is for some reasons, like if you wanted to get on xbl with an rgh console because for some reason your able to now with the new update
IMHO this is arguing for the sake of arguing.

There is NO reason for anyone building 16203 RGH right now and I would suggest no-one does until dashlaunch supports it. Because you CAN get on doesn't mean you SHOULD.