Strange Insignia signup issue

[clueless]

I am trying to get one of my Xboxen ready for when Insignia drops, and I am having a wierd issue.

If I put in a HDD built with OGXbox installer, it works.  I can get all the way through to the create a gamertag screen.  If I put a hdd that is a clean build, only MS dash files on it (5960), it fails just after "create an accont" screen.  "something went wrong.."

Same bios, same dash, only difference being one was hand built with fatxplorer. with just the dash files, the other with fatxplorer and "OGXBox Installer 2021 - v1.5.3 beta 2 For FatXplorer + XBoxHDM" files...  The only modification I made to the ogxbox files, was adding the ini file for cerbios.

Ideas?

[zatchbot]

Bios?

[clueless]

1 minute ago, zatchbot said:

Bios?

originally cerbios 2.203r, but also tried with evoXm8+ behaviour is the same between the two drives independant of the bios.  This is really doing my head in!

[clueless]

ok, so I just nuked the non working drive again, and with Cerbios 2.03R, as expected it didnt work.  Flashed to EvoXm8+, and it took me through to create Gamertag.

Flashed back to Cerbios, and all is working now.  NFI what was up with the files on the old drive, but that was annoying!

[zatchbot]

That's what I thought.

 

The running theory is 2.0.3R blocks MACS for some reason. Once the machine account has been built everything is good. The machine account resides in the config area of the HDD from address 0x0000000 to 0x00080000. Assuming this therory is correct, anytime you put a new HDD in you need to run MACS to connect to Insignia initially. https://xboxdevwiki.net/Xbox_Live/Connection_Test

 

The suggestion from the Cerbios discord currently is revert to 2.0.2R retail -> connect to Insignia -> back to 2.0.3R. 

[clueless]

8 minutes ago, zatchbot said:

That's what I thought.

 

The running theory is 2.0.3R blocks MACS for some reason. Once the machine account has been built everything is good. The machine account resides in the config area of the HDD from address 0x0000000 to 0x00080000. Assuming this therory is correct, anytime you put a new HDD in you need to run MACS to connect to Insignia initially. https://xboxdevwiki.net/Xbox_Live/Connection_Test

 

The suggestion from the Cerbios discord currently is revert to 2.0.2R retail -> connect to Insignia -> back to 2.0.3R. 

Here's the thing though, the connection test passed with cerbios 2.03r.  It would bomb out right before the country select screen when you try and setup an account.

 

[zatchbot]

Is the MS dash the same on both drives?

[clueless]

15 minutes ago, zatchbot said:

Is the MS dash the same on both drives?

identical

[zatchbot]

Strange... Maybe there is a slight difference in config between the two you aren't noticing?

 

I have a replacement PSU arriving Tuesday for my next build. I will see if I can replicate what you are saying.

[clueless]

23 minutes ago, zatchbot said:

Strange... Maybe there is a slight difference in config between the two you aren't noticing?

 

I have a replacement PSU arriving Tuesday for my next build. I will see if I can replicate what you are saying.

Like I said, I belw it away, and did it again, and it now works, but it was really, really strange

[bulkchart32]

u can't swap drives like that with insignia unless u have cloned them so they have the original hdd key that u registered the xbox with.

[Bowlsnapper]

On 1/5/2023 at 5:27 PM, bulkchart32 said:

u can't swap drives like that with insignia unless u have cloned them so they have the original hdd key that u registered the xbox with.

Sorry to bring this thread back to life, but correct.

It's actually the machine's EEPROM. The HDD key, serial number, and online key need to be identical or that profile on the HDD will not show up in the dashboard and will be hidden. This is being addressed by the Insignia team.