Jump to content


Photo

Ms21 And Spoofing?


  • Please log in to reply
7 replies to this topic

#1 vinomarky

vinomarky

    X-S X-perience

  • Members
  • PipPip
  • 349 posts
  • Location:Australia
  • Xbox Version:unk
  • 360 version:unknown

Posted 11 January 2007 - 12:51 PM

Hi all,

Flashed a friends' drive tonight. It was manufactured in Sept 2005, and had a MS25 sticker affixed over the original label. I extracted the firmware and loaded it in the firmware toolbox 3, which identified it as a MS21.....

I decided to simply go ahead and flash to 5.2 spoofing a MS25, but should I have manually hexedited the id tags in the firmware to reflect MS21?

Thoughts?

#2 jameswalter

jameswalter

    X-S Knowledgebase

  • Members
  • PipPipPipPipPipPipPipPip
  • 4,881 posts
  • Location:Camas, WA
  • Xbox Version:v1.0
  • 360 version:v2 (zephyr)

Posted 11 January 2007 - 04:19 PM

Does it work in his box? If the box has been updated lately, and it boots, you should be fine.

#3 vinomarky

vinomarky

    X-S X-perience

  • Members
  • PipPip
  • 349 posts
  • Location:Australia
  • Xbox Version:unk
  • 360 version:unknown

Posted 11 January 2007 - 09:01 PM

It had not been updated on Live, and we had not facility to do so while I was there....

I guess we'll just wait and see - I might as well make a custom firmware spoofing MS21 to be ready just in case...

#4 vinomarky

vinomarky

    X-S X-perience

  • Members
  • PipPip
  • 349 posts
  • Location:Australia
  • Xbox Version:unk
  • 360 version:unknown

Posted 12 January 2007 - 10:28 AM

**Update**

We managed to get it on XBL, and it DID get an E66 error, even after spoofing a MS25

I have hexedited the hacked firmware manually to spoof a MS21, and will try reflashing tomorrow.

This could be the cause of a few reports of people with E66 even after spoofing the correct model....



#5 lord^infamous

lord^infamous

    X-S X-perience

  • Members
  • PipPip
  • 301 posts
  • Location:CHI TOWN
  • Xbox Version:none
  • 360 version:v5.0 (360S - trinity)

Posted 12 January 2007 - 10:46 AM

I had a guy bring me a 360 that was sent to him by M$ and it also had the ms25 sticker over a ms21 firmware. Put 4.2 on it and it also got the e66. Went back to 3.3 and all was good.

#6 myfranco

myfranco

    X-S Genius

  • Members
  • PipPipPipPip
  • 820 posts
  • Location:Turkey-Istanbul
  • Xbox Version:v1.6
  • 360 version:v1 (xenon)

Posted 12 January 2007 - 10:46 AM

That's interesting.I have a ms25 samsung which is ms21 originally and i flashed with 3.3 and did all the live updates but no E66 error.I knew that MS married those drives to 360 after May 2006 not before.That's very strange.

#7 vinomarky

vinomarky

    X-S X-perience

  • Members
  • PipPip
  • 349 posts
  • Location:Australia
  • Xbox Version:unk
  • 360 version:unknown

Posted 12 January 2007 - 10:57 AM

QUOTE(myfranco @ Jan 12 2007, 10:53 AM) View Post

I knew that MS married those drives to 360 after May 2006 not before.That's very strange.


He actually bought is recently (last month or two) so I was very suprised to see the old manufacture date. One other item (per initial post) is that the fw identification of MS25 was actually a little sticker over top of the original label - perhaps they have manufacured a (relatively) new xbox unit with old drives that were available?

Anyhoo - just underlines the need to check your orig.bin files in firmware toolbox. Had I not, I would not know what was going on!

Edited by vinomarky, 12 January 2007 - 11:01 AM.


#8 vinomarky

vinomarky

    X-S X-perience

  • Members
  • PipPip
  • 349 posts
  • Location:Australia
  • Xbox Version:unk
  • 360 version:unknown

Posted 14 January 2007 - 01:38 AM

**Update 2 **

Reflashed with the manually hexedited firmware to spoof a MS21 (changes made at 0x2030 and 0x20D6) and it worked flawlessly

XBox now takes the updates and plays backups like a champ :-)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users