Corrupt profiles?

[fsm]

Howdy all...

    I have a retail box, latest kernel, that I have an MS25 sammy drive in. I just flashed this to iXtreme 1.4, 8x, and tested my first 'backed up' game. (No, this is really *my* game, to head off any pirate name-calling).

I removed the HDD, and removed internet (ethernet cable). I then took a live retail profile on a 64MB memory card, valid gold, and tested this game (Conflict: Denied Ops).

All appeared well, and profile loaded fine offline.

When I shut off the box, and moved the memory card back to my non-modded retail, the profile is listed as 'corrupt' on the mem. card, and won't load. I ended up having to recover it.

As well, there was another profile I tested this same scenario with, and the profile got corrupt.

Anyone ever heard of this, or would be able to speculate as to the cause?

*On a side note, the reason for no HDD is this box will load ALL content, live games, etc. fine from the HDD, but when loading a game (any), the games ALL freeze while caching.

Yes, I tried different HDD's, but as of now, it's not necessary to have one on there.

Any input would be appreciated!

...::*FSM*::...

(If you need any more info, let me know!)

[fsm]

*Sorry, can't edit the first post*

I have done some looking, and found this little thread:

http://forums.xbox-scene.com/index.php?showtopic=618449&pid=4088814&mode=threaded&show=&st=&#entry4088814

What's the take on this board? Any ideas (I am free to 'play' with this modded box for testing this issue out)   

Thanks!

...::*FSM*::...

[gigabite]

pirate !! : p kidding now....I and my customers, and my friends - have also experienced this problem HOWEVER I have narrowed it down to this....it only happens when you plug and old HDD from an old system into a new OR repaired system so conclusion, don't touch or move anything...but stay with Microsoft, oh and keep paying them to

gigabite

[fsm]

pirate !! : p kidding now....I and my customers, and my friends - have also experienced this problem HOWEVER I have narrowed it down to this....it only happens when you plug and old HDD from an old system into a new OR repaired system so conclusion, don't touch or move anything...but stay with Microsoft, oh and keep paying them to

gigabite

Thanks gigabite, 'ppreciate it...

I thought something may be up, but there is NO HDD present :|

I thought there was something wierd when ANY game would not load with a HDD on it... Well, H3, for example (retail game, I only just flashed my first drive now) will load the full menu, appear to cache the 'local' multiplayer map(s), then when trying to start the round, the loading will freeze...

R6:Vegas will load the menu, but again, freeze with the HDD attached when loading the maps/campaign.

I thought it may be an issue with the dash not being the same kernel as the one the profile came from, but *Surprise*, they match exactly

I'm not needing a HDD on this unit, at all, just use it with a mem. card... I just think there is something else going on...

Will be testing some more and letting you know!

Thanks again!

...::*FSM*::...

[gigabite]

clear the chaces (if you can format and then clear) on them...tried that ?

gigabite

[fsm]

Howdy,

     I have tried all the 'usual' things...
but the issue with the HDD is not relevant, as it's not attached

For the memory cards, yes, I have cleared both of them (two for testing, 64mb and a 256mb). I have formatted them, tried creating a new Gold (and silver) on each box, and same as the first post, when ANY profile moves from Box-X (flashed one having issues) to ANY other retail, it craps itself (the profile)

Thanks...

...::*FSM*::...

[gigabite]

hmmm....personally I only experienced the issue with a HDD (I put the HDD into a repaired system (new mobo) brother played Test Drive Unlimited on his profile, put it back on the old Xbox and his whole profile was corrupted), I think it copys/moves properly but ehh I dunno what could even cause the issue...what could cause the corruption on the other box

- it can't be the way it reads it because then it just wouldn't work on one box but when you put it back on the other box it would work fine (logically)...

- could it be the way it writes to it...say it reads it goes yeap ok then writes back to it quickly and that's when corruption occurs ?

it's really a mystery and the problem has NOT been solved through M$'s hush hush on everything...friend sent his launch day box in 2 weeks ago, got a brand new one (opening it today) - put his HDD from his old one onto his new one and everything was corrupt ! He went from the same kernal to the same kernal, this is very annoying though because you play and play and play...then RROD send the console in go to play again and have to start all over again -

-does anyone have one of those minispy things where it lets you connect to the HDD and the memory card, if you do could you please contact me via PM...I would like to test some theory's out (ehhh....assuming you also have an "old" box and a repaired box)

gigabite

[fsm]

I do have all the 'usual' tools, also

I could try to diff  (find the hex differences) between when the profile goes in to the box 'good', and when it comes out 'corrupt'... Hmm...

I will be doing some more testing with this today, gigabite, and appreciate your input

...::*FSM*::...

(PS: I've for the Pelican Xport, Minispy, Xecuter HDD kit, and some internal MS HDD adapters, no problem getting info off the memory cards/hdd's   )

[tin]

The only way that i could get it back on mine was to delete the POFILE ONLY!! Not the game saves. Then recover it back from live then all the game saves and the profile were fine. I tried everything else and it just would not play at all.

[gigabite]

Yes but if you only play offline, then that won't work - FSM have you done any testing yet ?  I am interested to know why this even happens

gigabite

[fsm]

Yes but if you only play offline, then that won't work - FSM have you done any testing yet ?  I am interested to know why this even happens

gigabite

Affirmative...

I have tried on and offline, both end with the same 'corrupt' issue. This is tested between box A ('corrupt/flashed' box) and B (HDMI box) and C (Twin non-hdmi as A, same drive and like mfg. date).

This should eliminate any kernel/hardware differences

Any other ideas?

...::*FSM*::...

[gigabite]

in this case (unless tmbinc...etc decides to comment) I believe it's something to do with the kernel (NOTHING to do with the firmware)...there could be a couple of theory's to that (now i've gone blank)

it's got nothing to physically do with the hardware (CPU...etc...and I can vouch for this cause the 65's or zephers weren't out when I faced the prob) but the kernel I believe...I don't believe it's to do with the number of e-fuses that are blown...

would it be possible that the "stock" 5xxx kernal M$ sends out differs from the actual UPDATE 5xxx kernal we can get (there for....there are technically 2 types of each kernal...not long ago TMF posted up all the updates...said there were 2 versions of a particular 2xxx kernal)

gigabite

[Arakon]

I have a similar issue now. I downgraded a console (CF 1903, 6683), upgraded to 4532, got the CPU key etc. I adjusted the lockdown counters on the original firmware to match the 4532's lockdown setting and flashed it back to 6683 with the infectus. Now ALL profiles on all storage devices are corrupt on this console only, I can create a new one that works, but as soon as I try to register it as a live account or recover another account, I get error code 80150003:4294967295.
Lockdown counter had been 0-5-6 on the 4532 FW, I set it to the same on the 6683 dump I made before downgrading.

[Arakon]

I got it fixed by re-flashing the 4532 firmware and then upgrading with an actual update (using the HDD with update on it). So it appears there's actually some change with the lockdown counters and profile.

[gigabite]

so you think it's the lock down counters that can effect the game saves (corrupting them) - it's possible...and logical to - any "new" box has a blown efuse...but I don't know how that could affect game saves (i'm still sticking with my idea of the kernel M$ sends out and the update kernel we receive are different....) -

I have a dump of my original kernel on my downgraded box which is 5759 - NOT repaired...this came with the console / if someone has a repaired box and they dumped the 5759 kernel (which came with it) could you (and i'll do the same to) send there dump of the NAND to someone like robinsod for analyzing ? - We can also compare this to a box upgraded (via update) to 5759...so 3 flashes to compare on my theory...I would do it but I don't really know what i'm doing - anyone

gigabite

[jimbo70]

Actually I had something similar happen this past week. I had a 360 Prem. console that kept dying (did xclamp mod but it only lasted a few weeks at a time so I said screw it), so I bought a new Arcade ed. console (cheap enough, it's only money right,  lol, made sure I got a Benq too). I hooked up the HDD & put in the 64mb memory card I had from original console & figured I'd start playing some games, nope. When I went to check profiles, the two that I had now said 'corrupt profile', WTF! Everything else on the memory card & HDD looked ok, just the profiles were corrupt. I couldn't see how I damaged the mem. card, so I put it back in the original Prem. unit & sure enough they were fine there. I also had to go online & recover profiles (which weren't quite as high as they should've been, but that's because I don't go online much to have it updated there).

About a year ago I changed consoles using the memory card & it worked fine in the new system. Isn't keeping your profile on the memory card supposed to be portable, so you can use it in a friends system or a new system like this?