Last Recovery Disc ?

Hi,
I search the name / number of the last Recovery Disc for connect to the XePartnerNet.
My testKit : Flash 8464.0 XDK : 9328.0

 

Salut,

Tu arrive pas a te connecter avec cette version ?

Je sais pas si c`est la dernière, mais si tu as pas fait la mise a jour avec le disque dur brancher tu aura pas acces au xeparternet.

++

 

Hi,
En fait ca plante quand je fais l'update avec le HDD : erreur 0X000000047 :/
J'ai fait l'update sans HDD mais la connexion n'est pas possible.
Je me suis dis que ça venait peut être de la version.

////

Hi,
In fact it crashes when I update with the HDD: 0X000000047 error: /
I did the update without HDD but the connection isn't possible.
I think it may just be the version.

 

Yop,

Bizare, as tu tenter de formater quand meme le HDD avant de tenter de faire une mise a jour ?

++

 

Je vais testé, merci.

 

Guys,speak english here.

So your trying to connect to PaternetNet and you get a error when trying to connect?

 

Sorry for speak french, but my english was very bad and zouzzz is french so is most facil for explain

++

 

Test connection to XePartnerNet :

Test of connection to XePartnerNet failed:
LOGON_UPDATE_NOT_PROPPED
(0x80151924)

 

When you recover to 9328 you must have your HDD attached in order to connect to PartnerNet. If you don't have your HDD attached it will be missing some files I believe.

 

Ok, i have downgrade the Test Kit in 8276 and after I have upgrade the Test Kit in 9328 with hdd and now works.
Thanks a lot Naruto, Pikkon and gabe_k

 

Is it possible to update with the resistor removed? Or will that result in E80 or something?

 

From my understanding there is no need to remove a resistor on a Xedk.

 

Can you confirm this? AFAIK (or remember) you sold your devkit a long time ago and I see a lockdown routine in NXE. (I have 6995 on it now)

 

No one really ever tried removing the R6t3 off their dev... So your in for a surprise, I say put it back on, I mean if you saw the routine was there, but also think about it, the dev never blows any ldv(<- not entirely sure about this) so why would it not boot.

 

Yeah, after all, when the sun doesn't shine, it's not that it doesn't exist for that specific amount of time, it's just that it's hidden by the clouds.

Now for the blind and deaf: if you have ever updated to NXE/8xxx and downgraded to 4532, please confirm.
I don't need to know about hear-say or comments stating the obvious - just real facts (no offence pikkon or leo).

Thanks in advance

 

I have, alot of times.

Edit: Look its hard for you that we arent technical folk, but we know alot about these machines. If I remeber correctly nxe simply checked if the fuses changed after the update if it didn't it would throw you e80, I dont think devkits blow fuses when you update them meaning it wouldn't throw that error.

 

Devkits don't blow fuses jesus. You can Jtag a devkit on the latest. If it blew fuses you wouldn't be able to downgrade, however non xenons don't go below a certain firmware due to the CB thus crash.
Okay /discussion

Back to drinking

 

Last is 9328.9 but must be newest

 

Don't want to cause you panic, but if I were you I would cover the X: status code too as that can be used to identify your console as well.