Topic: Unflashed Console Flash Flash After Or Before Update (Read 95 times)

vicfalc09 · « **on:** November 01, 2006, 08:00:00 AM »

Is there any reason I couldnt flash after the update? When should I flash?

OriginalCompGeek · « **Reply #1 on:** November 01, 2006, 10:00:00 AM »

Flash before, that's my recommendation. Although, I can't really give you solid evidence that supports one choice over the other. Most people have made it through just fine with their drive flashed before updating.

bartje006 · « **Reply #2 on:** November 02, 2006, 06:32:00 AM »

Mine isn't opened yet also. Any more suggestions?

Doesnt affect the update the flashing process?

PhatheadWRX · « **Reply #3 on:** November 02, 2006, 06:49:00 AM »

what drive what model?

If hitachi don't worry and just flash because it only patches the fw, not rewrites it.

If Samsung ms 25 you can flash with Xtreme 3.3 before or after.

If Samsung ms 28 you need to flash Xtreme 4.1+ before the update.

vicfalc09 · « **Reply #4 on:** November 02, 2006, 06:52:00 AM »

I have the ms25 and I did the update already. So i should go with 3.3 correct?

PhatheadWRX · « **Reply #5 on:** November 02, 2006, 06:53:00 AM »

I would stick with 3.3 its ms25 based so no apparent upgrade of the drive.

I think that is the safest bet.

bartje006 · « **Reply #6 on:** November 02, 2006, 07:21:00 AM »

Ok.

I probably have a Samsung ms28.

So update before flashing?

bartje006 · « **Reply #7 on:** November 03, 2006, 01:21:00 AM »

admiraljdn · « **Reply #8 on:** November 03, 2006, 07:08:00 AM »

I just bought a brand new 360 (9-25-2006 manf date SWEET!) and it had an ms28. My instinct told me to update the live thing BEFORE i did any flashing. I did the live update then I put 4.2a on and it works perfectly. I swear this console is FIX'D so much since the oringinal launch consoles.

So get the thing up to date and running on live and THEN mess around with firmware.

vicfalc09 · « **Reply #9 on:** November 03, 2006, 07:18:00 AM »

I updated on my new console first the flashed to 4.2b and had no problem and my drive was an ms25. So i dont get why everyone is saying to go 3.3 with this drive.

ZakMcRofl · « **Reply #10 on:** November 03, 2006, 07:23:00 AM »

QUOTE(vicfalc09 @ Nov 3 2006, 02:49 PM)

I updated on my new console first the flashed to 4.2b and had no problem and my drive was an ms25. So i dont get why everyone is saying to go 3.3 with this drive.

Because, if M$ has a clue when (with which serial number) they changed from MS25 to MS28, they can find out that the firmware was flashed.

On the other hand, if the new update stores some information about the firmware (checksum, return values, version) then it may make more sense to flash before the upgrade.

Since it certainly can't hurt to flash before, I would recommend that. I'll be in that position shortly and I will flash first, then update.

Kramer987 · « **Reply #11 on:** November 03, 2006, 07:32:00 AM »

to be completely honest, as long as you use 4.2 with that fix (changing the hex identifier thingy) it will work fine. i think the new sam360 program or whatever even modifies everything for you perfectly, so you can just use that. no need to stick with fw 3.3. if firmguard was made it must have been made for a reason so you may as well use it. u'll have to waste a DL disc on the 0800 dvd tho so you can flash in the future, but its most likely for the best.

arrush · « **Reply #12 on:** November 03, 2006, 07:34:00 AM »

Little off topic here, but before updating from 3.2 to 4.2 do i need to first flash with orig.bin or can i just flash from the old to the new version. I'm pretty sure i read somewhere that you should always flash back to your original bin before doing any updates but i cant seem to find the thread.

thank you

Pres · « **Reply #13 on:** November 03, 2006, 07:46:00 AM »

Got a question!

I have a premium manufactured in May 2006 which originally came with a TS-H943 ms25 Ver.A.
I never modified the FW only dumped it as a precaution when the tools became available. The drive started to act up after the warranty was no longer. (go figure) It slowly started not reading disks and eventually quit reading disks. (again as I said never modified) So I aquired a Hitachi 3120 46 DG put my key in and ran OPA 2.1 all is fine. Never planned on modifying my drive but was a little ticked that my 360 lasted 4 months so to speak it was my way of saying f*** you too MS. I have been using the Hitachi for awhile now and never no probs. I do not go on live with it nor have I ever with it. (did with original ms25) I dont care to update my dash but I know it will be released on a game disk in the future and I will be forced into it. What would seem like my best option to get the update when that time comes. The ms25 still registers in the 360 just wont read, so should I place the ms25 in it update then switch back to the Hitachi or update with Hitachi?

Just wanted to get some opinions and wondered if anyone else has a similar situation and was succesful or unsuccesful. Please share!

Kramer987 · « **Reply #14 on:** November 03, 2006, 07:53:00 AM »

pres, i actually think that is a very smart move on your part heh. clearly putting your original drive back will cause zero problems when updating. only thing i am unsure of is what will happen when you put your hitachi back in. i am guessing nothing should happen. but it might just error on you. nothin to be worried about tho. i'm sure by then we'll have more than enough info to figure out what to do regarding all this update business.

Author Topic: Unflashed Console Flash Flash After Or Before Update (Read 95 times)