Post by: zohaer21 on November 03, 2006, 04:53:00 PM
i know alot of ppl got screwed with patched ms25/ms28 drives after they tried to do the fall update and ended up with bricking thier systems
i got me a xbox360 (unmodded,brand new) and applied the fall update today successfully
does anyone know if i patch my samsung drive (dont know if its ms25/ms28) will it brick my system??
thanks
Post by: Progz1337 on November 03, 2006, 05:16:00 PM
QUOTE(zohaer21 @ Nov 3 2006, 06:24 PM) 
hi
i know alot of ppl got screwed with patched ms25/ms28 drives after they tried to do the fall update and ended up with bricking thier systems
i got me a xbox360 (unmodded,brand new) and applied the fall update today successfully
does anyone know if i patch my samsung drive (dont know if its ms25/ms28) will it brick my system??
thanks
im pretty sure if it does brick if you put the firmware you can just change it to the orignal firmware. but hopefully someone else will post here and tell you.
Post by: jameswalter on November 03, 2006, 05:45:00 PM
Post by: zohaer21 on November 03, 2006, 11:02:00 PM
QUOTE(jameswalter @ Nov 4 2006, 01:16 AM)
Nobody's system got bricked. There were all able to be recovered by reflashing with the correct firmware version or using the new XBOXSAM 0.5. The update did nothing to the drive itself...just to the checking of the firmware version versus what shipped with the console.
not to put a bucket of water on peoples hopes..but two of my friends got E 71 errors (one has ms25 and the other ms 28) and theyre both cryinf coz they dont know how to fix this.. are you saying there is a solution .. if so could you tell me
thanks
Post by: peetyboy2006 on November 04, 2006, 05:56:00 AM
QUOTE
not to put a bucket of water on peoples hopes..but two of my friends got E 71 errors (one has ms25 and the other ms 28) and theyre both cryinf coz they dont know how to fix this.. are you saying there is a solution .. if so could you tell me
thanks
thanks
There is a solution, you just reflash the drive using XBOXSAM 0.5, like the guy above you posted. The reason this happens now is that MS has integrated some new features into the kernel, these are DVDVERSION check and DVDMODEL check (correct if im wrong there). The 360 checks these against your ORIGINAL stock firmware and if your hacked firmware is a lower version or the drive is a different model then you get an error. Its fine if the hacked firmware is a higher version because MS allow for ugrades to firmware, just not downgrades now.
So if you have an MS28 and youve flashed with xtreme 3.3 then youll have problems because the version will be lower than your original drive firmware (as 3.3 was based on ms25).
So either reflash with a higher firmware or reflash using the XBOXSAM 0.5 method (which copies the dvd version and model sections from original firmware now i think... correct me if im wrong though).
Have your friends tried to reflash the drives? if so what firmware do they have on there atm (hacked/ unhacked, version etc...)? if you post more details about what they used and are trying to do then you can get more help from people on here.
Post by: jameswalter on November 04, 2006, 11:42:00 AM
Post by: mr-smith on November 05, 2006, 12:47:00 PM
QUOTE
E71 happened to people who didn't have the spring update installed before the fall update installed. It had nothing to do with flashed firmware
I presume my August 2006 machine came with the spring update already installed then.........
Post by: j0nesy on November 05, 2006, 01:01:00 PM
Post by: son of thunder on November 09, 2006, 06:44:00 AM
Post by: jabroniekilla on November 09, 2006, 08:22:00 AM