RGH Better to update oficially then RGH,or first RGH then update?

[bruno_rv]

Which is better solution? Better to officially update to 14699 via usb stick and then do a RGH,or first RGH then update to 14699?
Is there any big difference?
I have a jasper with lots of save data on it and 13604 dash. Wanted to flash drive to stock first,then update to 14699, then LT3.0, then RGH. If i update officially with usb stick, and then glitch it,is there less chance to have problems some people have when updating after RGH like avatars or similar?

 

[playingmax]

well u still have to run the offical update after ur rgh. so it would be easier to run the date b4.

 

[RavenPhoenix]

No difference in my opinion really but the way I would probably do it is to RGH on current dash then build the hack 14699 dash and install the official update once all is well.

 

[WNYConsoles]

It really depends but I have seen issues when going from an old dash to a new FB Dash. For example if you are on 12625 retail dash and create your 14699 FB from the 12625 retail dump. I have seen issues, specifically on BB Jaspers.

It doesn't make much sense to me not to update to the newest dash before starting the RGH process and dumping the NAND. Update, install the CoolRunner/RGH, ECC, FB creation. If you run into problems you can at the very least rule out that it is not a old dash problem.

 

[Martin C]

It doesn't make much sense to me not to update to the newest dash before starting the RGH process and dumping the NAND.

It does if you don't have the original drive and you're on 12625, or you have a slim on 12625 or less and a 9504 unlocked

Best solution to avoid any problems is to build a 14699 RETAIL first, then use THIS as the source for the 14699 RGH. I had one console with E79 after jumping versions but the above resolved it.

 

[JtagMan]

good to hear since i already am on 14699

 

[bruno_rv]

It does if you don't have the original drive and you're on 12625, or you have a slim on 12625 or less and a 9504 unlocked

Best solution to avoid any problems is to build a 14699 RETAIL first, then use THIS as the source for the 14699 RGH. I had one console with E79 after jumping versions but the above resolved it.

So u mean, if i have 12625 or similar,i make rgh,read backup nand,flash ecc,take cpukey out,and with multibuilder make 14699 retail,and then use that file as source file for making hacked nand? Why this nand would be better that original backup nand? Its cleaner or?
Thanx for answer.

 

[Martin C]

So u mean, if i have 12625 or similar,i make rgh,read backup nand,flash ecc,take cpukey out,and with multibuilder make 14699 retail,and then use that file as source file for making hacked nand? Why this nand would be better that original backup nand? Its cleaner or?
Thanx for answer.

'Better' probably isn't the right term. It will be 'closer' to the RGH image you will build. It will certainly be 'cleaner', since any data you dumped which maybe wasn't 100% (yes, retail images on stock consoles can have bugs like profile corruption etc).

 

[bruno_rv]

Thank you all

 

[WNYConsoles]

It does if you don't have the original drive and you're on 12625, or you have a slim on 12625 or less and a 9504 unlocked

Yes, of course. Slim with 12625 and a unlocked drive or have a XBOX that does not have a matching drive, don't run official update.

Other than that I see no reason not to