Thanks for posting that info. Some slight clarification though, if you could..
- Your OSIG is an MS28, and that drive currently has CFW on it but you arent using it because it doesnt work for w/e reason. However you installed this drive in order to proceed with the system update and upon doing so, you received an E66 upon boot thereafter.
- After receiving this error you installed you spoofed Hitachi drive and proceeded with the update again. The update installed fine with your Hitachi drive and you have no issues playing backups.
Correct me if I misunderstood anything. Thanks again for taking the time to post some relevant data.
QUOTE(Alexbeav @ Jun 2 2011, 02:43 PM)

Well I downloaded the update and installed it thru USB while offline. a couple of things to note :
1) the 'original' drive of the console was a samsung m28. trying the update, I got the E66 error while on CFW.
2) the spoofed drive I have is a hitachi 57 (or 59 not sure). with CFW, the update installed correctly. I didn't need to reflash, because it reads everything fine. (haven't tried Halo Reach, but since I haven't installed that game's update, it's not AP 2,5 yet - i think. it was working fine though)
3) logged into live, had no problems dling content. disconnected the cable once i was done and now keeping my fingers crossed while waiting for LT 2.0
anyone can remind me whats the tool that u input a number from your settings and it tells you if you've been flagged ?