RGH Slim 13146 glitch needs 14699 rgh image?

[dogeatdog]

Posting this for a friend of mine. I trust him enough to know he's not bullshitting on this one. Here goes.

He had a Slim Trinity. Stock dash : 2.0.13164. Decided to RGH it (not his first, he knows what he's doing).

Used Multibuilder 0.82 to create .ecc. Got xell, cpu key.
Creates 2.0.14719 rgh image and flashes it back.
No glitch, no matter how many times he booted and how long he waited.

Then decided to create a 2.0.14699 RGH image. Just for giggles. Flashes this to the Slim and it glitches (after the third green flash). Tries another few times, consistent booting (2-3 green flashes). Very nice.

Decides to test once again and flashes back the 2.0.14719 again. No glitch. Ever.

Flashes back the 2.0.14699 and .. ah well.. you can guess it I think.. glitches.

So.. what gives ? Do you need to be on 2.0.14717 official dash or higher first to be able to use the 2.0.14719 RGH image ?

I couldn't reproduce it since the only Slim I had since his story was one which was already at 2.0.14719 (and that one worked fine with 2.0.14719 RGH).

Or was this in some readme which me and my friend completely missed ?

 

[Martin C]

Nope - shouldn't be the case. The 14719 RGH should work regardless of what pre 14717 dash you were on for all consoles. Obviously the slim can now be done regardless.

 

[dogeatdog]

Ok, thanks for the feedback !

 

[bmonster007]

I've also updated to 14719 with Multibuilder 0.82, and had no problems.

Hope you get it fixed.

 

[digiman]

So you can be on an older MS dashboard (stock) and RGH on a 14719 freeboot image dashboard without update the console to 14719.