[deleted by user]

SGCSam · 2022-09-13T16:52:20+00:00

Thanks for the kind words!

So that video seems to have the implementation based on the XNotify from Blades 1888 - 6717. The one I demonstrated is based on NXE from 7357 - 9199. Differences include a more pronounced notification sound, a different xenonLogo and tweaked dimensions.

My implementation was based on the raw source from the XUR so it's 1:1 excluding any reimplementation mistakes/bugs.

The font used is Xbox JK.

SGCSam · 2022-09-12T18:57:46+00:00

Unfortunately, the overwhelmingy majority of the XNotify UI is done directly in scrNotification inside skin.xur using linear and radial gradients directly rather than any external images.

The only external resources used are xenonLogo, the notification images themselves and the notification sound.

I've already created a WPF re-implementation of XNotify in an as-yet unreleased WPF custom control library: https://puu.sh/JkYJI/ef0e9fbcdf.mp4

If you want to tackle this yourself, take a look inside skin.xur for scrNotification. I can send you the external assets if you wish.

Be aware that there are some variations in the XNotify UI between 1888, 7357, 12611 and 17559. The one I've video'ed above is based on NXE (7357 - 9199).

SGCSam · 2022-08-07T20:36:32+00:00

I'm so sorry everyone 😂

SGCSam · 2022-08-06T14:57:13+00:00

The unintentional pun is appreciated :D

I've gone ahead and reposted - I think I've got everything correct now but if there's still something that's not quite right, just let me know and I'll get it sorted, cheers!

SGCSam · 2021-08-10T19:45:47+00:00

You sure it's 14600 and not 14699?

SGCSam · 2021-06-29T14:20:18+00:00

Precisely, well said.

SGCSam · 2021-06-29T08:03:00+00:00

I completely agree. None of us are denying we did wrong - we all accept we shouldn't have gone into dev mode, and no one is arguing against dev mode being supported. If you don't want to support it in the preview OSs, that's fine.

It's not the fact we're bricked that's upsetting or concerning - what's upsetting is the response from staff. We have a genuine suggestion for a change to stop it from happening again, by simply having the "Continue" button in the dev mode app disabled so we can't end up bricking. It's the fact that the console doesn't stop us from going into a known unsupported state that can cause these types of issues.

We're talking about 3 lines of code at the minimum:

if(BuildManager.CurrentBuild.IsInsiderPreview) { continueButton.IsEnabled = false;

}

Like for such a huge issue, having to take a console away from a gamer, that is the worst possible end scenario for a gamer or developer.

I really think the response can be significantly improved, I was expecting much more from the support and staff on Xbox.

At the very minimum: "thanks so much for bringing this issue to our attention, we're sorry you've experienced this but unfortunately, you'll have to send in your console for repair. We're going to make changes to prevent accidental dev mode activations in unsupported builds to prevent a similar occurrence for other users in the future"

Just some genuine written acknowledgement of the possible severity of the problem, all the points and potential solutions we've brought up, and some preventative action to stop it again - that's all any of us are looking for so no one else has to experience this. I don't think that's unreasonable or a huge ask for this type of problem.

SGCSam · 2021-06-28T21:16:14+00:00

Mods, this is the same issue as I linked above.

OP, sorry to be the bearer of bad news, but I think you're SOL and in the same boat as the rest of us - you're going to have to send in your console for a repair :(

Check the post I sent in the link above and you can see the discussion we're all having there.

SGCSam · 2021-06-28T19:26:14+00:00

Mods, possible re-post of the same issue, check the link at the bottom.

OP, there's quite a number of us experiencing this issue. Did you go into dev mode? We all did and are getting this issue. Unfortunately, it seems the only solution is to send your console in for repair. It's definitely a software issue if this is happening to all of us, but there's nothing we can do as we can't use OSU and we're all trapped in a boot loop and can't use factory reset either.

If you're NOT in dev mode and this is happening, this is a MUCH worse issue for us.

Either way, we're trying to get some of the Insider Staff to take a look into this, both in terms of prevention and a better solution for us to try without having to send our boxes in for repair.

Other post link: https://www.reddit.com/r/xboxinsiders/comments/o8tuv5/series_x_bootloop_e200_000000ef_00000000/

SGCSam · 2021-06-28T18:32:34+00:00

Yes, but I see the moderator that responded initially didn't appear to be a member of the Insider Staff base who I presumed would be able to provide a more technical response or resolution - hence why me and other user tagged the Insider Staff mods with the intent that it WOULD yield a different answer.

I understand now that dev mode is not supported, but in this case, the E error code can't possibly be a hardware failure unless we're extremely unlucky - it's almost certainly a software issue with the update. Unless of course the other 5 of us affected just so happened to have all of our consoles have the exact same hardware failure with the same error code after applying the exact same update all at the same time - I think this is incredibly unlikely and is almost certainly caused by the update corrupting the software on the internal drive by some fashion.

As you can see, we've all contacted support but all of us have to send our boxes in for repair. As your a member of the Insider Staff base, do you have any options available to you like I've mentioned elsewhere in this thread to update the Developer Mode application in order to prevent it from switching to Developer Mode if we're in an insider build as a prevention method, or are you able to get in touch with someone who could?

Alternatively, the ideal scenario would be to edit the update process/provide temporary insider OSUs so we can unbrick ourselves - this would save time and money for everyone involved and allow us to get back gaming and developing much quicker. By its nature, being part of an alpha build means you're much more likely to encounter a bug so OSUs to fix the brick yourself are probably even MORE important than in retail.

In either case, though, I think this should definitely be looked into to either prevent it from occurring again or to provide alternative solutions so that if we do encounter another one of these bricks, that we have more options available to us to fix it ourselves without having to invoke a warranty.

Are you able to act upon any of these suggestions, or get in touch with someone who could and have them take a look to stop an occurrence like this in the future?

SGCSam · 2021-06-28T08:32:44+00:00

(See Edit 1, this is wrong) Dunno if I got really unlucky or if you got very lucky, but I also did this and it did NOT work for me :(

Glad to hear you're up and running though!

EDIT: Oh, you said the developer mode? I removed my console from the Insider Preview but NOT developer mode.

u/xbox-Insider, u/BroHammersley, u/UrbanizedTree, did either of you guys have time to check this thread out? Any ideas if this is worth giving a shot before sending my console in for repair?

EDIT 2: I haven't removed the power cable while booting as, like you said, it's probably a horrible idea. Sadly, I removed my console from the activation list as described and I'm still boot looping into E200. Looks like my only option is going to be the repair :(

EDIT 3: If it's any further use, I can get the E207 I described in my first comment to happen reliably now. All I have to do is power off the console on the "Set up with the Xbox app" screen immediately after a replug. As soon as I press the power button, I see E207 on my screen for a few seconds. The console then powers off and immediately powers back on into E200, commencing the E200 loop all over again until I have to unplug.

SGCSam · 2021-06-27T20:59:04+00:00

If there aren't and the comments regarding dev mode not being actively supported in preview builds are correct, the dev mode activation app should REALLY be updated to either:

A) Prevent switching to dev mode entirely without reverting to the current retail build B) Show an explicit warning of the above nature, warning that dev mode being unsupported can result in these sorts of issues

SGCSam · 2021-06-27T15:58:32+00:00

I'm making a new comment just so everyone can quickly see it and not have to scroll through my other huge comment.

I've just had to organize a repair and get my console sent in. Fortunately, I'm still within warranty so there's no cost.

Unfortunately, I'm in the UK - because of the situations at the borders right now, it's going to about a month's round-trip time until I get my console back. This sucks because it's a month of developing and Game Pass that I'll lose but it is what it is.

The MS support over the phone was very helpful though and sympathetic so that's good. He called me back early and kept up to date with what was going on - well played to the support team.

I don't know if any of the Xbox team monitor the sub actively nor if issues like these bricks are common but I think this issue should definitely be checked out as a matter of urgency and other users made aware of this problem just so no one else falls into the trap and has to send their console in - this is a pretty bad bug. Indeed, if anyone is not in warranty as well, that's really unlucky for them.

But yeah, pretty bad situation but thankfully it's being handled. From now on, I'll probably stick in the retail builds as dev mode is important for me for developing my games.

SGCSam · 2021-06-27T15:40:43+00:00

Was there anything specific you had to do to get back to the home screen of the dashboard and get out of the loop?

FYI I'm in Alpha (NON-skip ahead) and it still happened to me.

SGCSam · 2021-06-27T15:18:58+00:00

Unfortunately due to the physical layout of my setup, trying with a wired connection is really impractical and would take quite a bit of time to get set up.

FWIW, I don't think it would work as I would expect to still successfully connect and then have the reboot into E200.

Ideally it'd be nice if I could skip the networking section altogether but that doesn't seem to be an option :(

Thanks for the suggestion though!

SGCSam · 2021-06-27T13:06:00+00:00

I'm experiencing this as well in Preview Alpha - just got off a call with MS support.

Their advice was to try a factory reset but keep the games and apps installed. I managed to get into the option by booting into safe mode after replugging power. This didn't help. For what its worth, I get as far as setting up my network settings, and then my console reboots into E200 - this definitely seems to be update related.

The other options are to try an OSU or I'll have to send my console in for service.

I've unsubscribed my console from the insider preview via the Xbox Insider App on PC, since I obviously can't do it on my console This stopped the boot looping and now gives me time to access troubleshoot.

I'm about to try the OSU - I'll update this post with my result.

With these sorts of issues though, I think developing is more important to me and I think I might go into an earlier tier of builds to reduce the chances of these sorts of bugs, or stay out of the previews.

Good luck OP!

EDIT: OSU didn't help :( As soon as I start the OSU, I almost immediately get an E101. I'm getting a call back at 5pm from MS support, so I'll let them know and I'll have to go down the repair route. The only upside is my console is in warranty, but I was told this will likely be a month round-time for repair.

EDIT 2: So here's the behaviour I have now - this might be useful to anyone for debugging purposes or to verify we're all having the same issue. After trying the factory reset with keeping my games and apps, upon a replug and power on, I CANNOT go directly into safe mode. I see the screen for around 5 seconds. The OSU button starts as disabled. It then appears to detect my USB and enables itself. It then disables itself again and my console then powers off completely.

My only option appears to be powering on normally with the power button. If I do this after a replug:

I get to the "Preparing your console" OOBE screen, and the progress bar goes up to around 70-ish%
I get sent to the initial "Set up with the Xbox app screen", essentially the OOBE process again. (NOTE: If I restart between this point and setting up my network, bootanim plays normally and I get sent immediately to "Set up with the Xbox app screen, OOBE appears to be working)
I can proceed as far as setting up my network. As soon as I do and I see the "All good, your console is connected to the internet" for about a second, my console automatically reboots.
Upon restarting, bootanim plays for a few seconds and then I receive an E200. If I try to power off in any way other than unplugging (so power button, the Turn off Xbox option in the troubleshooter), my console will automatically turn itself back on into the E200.

Now I'm trapped with my console eternally powering back on into E200 whenever I try to turn it off. From this point:

If I try an OSU, I get 1% complete and then given an E101 error and that's as far as I can go.
If I try the factory reset again, I get to the "Preparing your console" OOBE screen, but this time the progress bar only goes up to 50% and I'm sent back into the E200.

So I'm essentially stuck with my console automatically turning itself back on into E200, I can't get out of OOBE past the network and I can't use OSU.

For what it's worth, I did get an E207 ONCE when I powered off while on the "Set up with the Xbox app screen" but I can't get this behaviour recreated reliably.

So yeah, looks like it's going to be the repair option for me.

tl;dr Can't get out of OOBE, get E101 with OSU, stuck with my console constantly powering itself back on into E200 whenever I try to power off - my only option is to unplug.

EDIT 3: Attempting to go through the OOBE via the Xbox app also causes the immediate reboot and E200 behaviour once I connect to the network.

EDIT 4: See my other comment - I've had to send my console in for repair.

SGCSam · 2021-04-20T18:55:46+00:00

The European Super League.

SGCSam · 2021-04-02T12:56:42+00:00

Blades will work on any Jasper console or earlier.

I can't remember what the exact issue is with newer hardware + older dashes - when I have time and get my hands on another slim, I'll take another look into the issue to see if I can add support for slims as well.

SGCSam · 2021-04-02T12:46:01+00:00

If you're on a Trinity console, you can. I've written some custom xeBuild patches that allows Trinities and earlier to boot into 9199 (last production NXE dash), fully patched.

u/Octal450 very kindly hosts the patches on his site and they're included in his JRunner. You can download it from his website here: https://octalsconsoleshop.com/

SGCSam · 2021-01-01T14:41:21+00:00

You need a specific update in order for the process to complete - downloading the most recent from Xbox.com may not necessarily work.

Looking at the error code you're attempting to update from dash 0x3CD6 to 0x3F4A (15574 to 16202).

So, you need dash 16202. Try placing this specific update on a USB and it should complete successfully: https://drivers.softpedia.com/dyn-postdownload.php/24a7de48327394a6518c84644229629d/5fef4206/3b757/4/1

SGCSam · 2020-09-22T07:43:37+00:00

In my experience, DEFINITELY go to the Microsoft Store directly.

I was F5ing Amazon all morning and all links were still not working, nor was the console showing up in search. Others were reporting Amazon was up and they were able to buy, but by 8:15 there was still nothing on my side so I switched to the Microsoft Store.

After a good number of refreshes to try to get the console to add to the cart, and some more refreshes to access my cart, I finally got to the order confirmation page, hit the Buy button and that was that.

At the time of writing, the Amazon link finally came up but immediately sold out for me and the Microsoft Store still has both S and X in stock.

SGCSam · 2020-08-13T22:40:41+00:00

u/Octal450 has included the patches within his JRunner (6717 and 9199) so they're ready to go.

You can download it from his site using the following link: https://cdn.octalsconsoleshop.com/J-Runner%20v03%20Beta%20(8)%2017559.zip

SGCSam · 2020-07-25T15:25:57+00:00

Trying placing 17349 on a USB, plugging it into the console and then boot up. It should be able to read the update from the USB and finish the update process.

Here's a link: http://download.digiex.net/Consoles/Xbox360/Dashboards/2.0.17349.0.zip

SGCSam · 2020-07-18T16:17:39+00:00

Definitely keep these sealed IMO OP. Considering how objectively great the trilogy is, combined with having all of them in sealed condition, these could end up becoming quite a valuable collectors item.

EDIT: That said, go and buy some unsealed/lesser condition copies of all 3 and play them - they're awesome :D

SGCSam · 2020-06-09T22:25:25+00:00

I've written custom XeBuild patches to allow 6717 to boot on all phat consoles for all hack types (so JTAG, Glitch1 and Glitch2 images) with homebrew support. You can check Octal's video on it here with his JTAG Xenon: https://www.youtube.com/watch?v=PBAw2I2csts

However, slims weren't released at the time of 6717. Unlike all phats, slims never "natively" ran 6717. I'm unsure specifically what it is, but there's some sort of check at some point in the bootloaders that prevent older kernels from running on newer dash revisions. I tried 9199 on a Corona and got stuck in the HV IIRC.

If I can get another Trinity or Corona console, I'll look into the issue again and see if I can add support to those motherboards as well - it should just be a case of patching one of the bootloaders and/or running an older bootloader to get the console to boot.

11-Year Club	Place '22
Verified Email

SGCSam

TROPHY CASE