xboxscene.org forums

Pages: [1] 2

Author Topic: Halo2 Theorys  (Read 178 times)

mkjones

  • Archived User
  • Hero Member
  • *
  • Posts: 810
Halo2 Theorys
« on: September 28, 2004, 03:06:00 AM »

QUOTE (kieronh @ Sep 28 2004, 11:00 AM)
ok, im reading a lot about the potentail for Autodash updates in Halo2.

Can anyone clear up the risks? i ran that Starwars DVD in my mates Modchipped box and saw the autoupdate, panicked and reset. although afterwards I realised as it had a chip i was ok.

i then tried to install the demo on my own Softmodded xboxs HDD. but couldnt get it to run (ive read up as to why).

What are the potential risks from the `halo2` issue? if i run it on chipped boxs it should be ok? then FTP it to mine and delete Dashupdate.xbe?

what are the odds of Default.xbe having a autodash updater built?

i dont have Live and probably never will do.

Bascially what id like to know is am i just being paranoid, or is this a serious risk, and what ways can i minimise the risk to my xbox?

The best bet is to boot your exploit first and then play the game, this would block any updates as far as I can see smile.gif
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Halo2 Theorys
« Reply #1 on: September 28, 2004, 03:11:00 AM »

QUOTE (kieronh @ Sep 28 2004, 11:12 AM)
how do you mean? sorry! can you explain that in more detail?

Don't boot the game DVD - Boot to Evox, then select the "Launch DVD" option (is I think what mkjones was suggesting).

While this may make little difference now, it's a good habit to get into.  And should a HALO2 proof BFM BIOS be required/produced you'll be familiar with the procedure.

My advice would be to wait until others to have posted success in these forums. smile.gif
Logged

mkjones

  • Archived User
  • Hero Member
  • *
  • Posts: 810
Halo2 Theorys
« Reply #2 on: September 28, 2004, 04:02:00 AM »

QUOTE (kieronh @ Sep 28 2004, 11:17 AM)
ahhh! ok , yeah. so that would stop even a autodash update, or one what has hardcoded into default.xbe? i use XBMC as my dash, but have Evox installed too. i guess it would run ok from there too? (i have autorun off)

I doubt they would "hard code" it as you describe.

XBMC should boot the game as soon as you place the DVD in if you have it set up as default smile.gif
Logged

mkjones

  • Archived User
  • Hero Member
  • *
  • Posts: 810
Halo2 Theorys
« Reply #3 on: September 28, 2004, 04:37:00 AM »

QUOTE (kieronh @ Sep 28 2004, 12:18 PM)
i have autorun turned off on XBMC, and then just select Deflault.xbe from the DVD.

someone in another thread suggested that MS could incorporate the dashupdate into default.xbe. i dont see why this isnt possible?

Then you should be fine, just do as you always do and leave the updatedash files alone smile.gif

As for embeding the updates, could happen, but I doubt it. tongue.gif
Logged

total_ass

  • Archived User
  • Hero Member
  • *
  • Posts: 1201
Halo2 Theorys
« Reply #4 on: September 28, 2004, 08:57:00 AM »

are any NTSC users here planning to get the game the day it comes out? it's just that i live in UK and we get it two days after i believe. it would be nice to see if it works before i buy it.
Logged

eh.

  • Archived User
  • Hero Member
  • *
  • Posts: 529
Halo2 Theorys
« Reply #5 on: September 28, 2004, 10:08:00 AM »

(@total_ass: I'd guess the majority here are planning to do both eh! jester.gif)
Logged

JimmyGoon

  • Archived User
  • Full Member
  • *
  • Posts: 210
Halo2 Theorys
« Reply #6 on: September 28, 2004, 02:35:00 PM »

so as long as my friends let Dash load THEN boot Halo 2 they are safe!?

WOW! Sweet! I was really worried I would be spending November 10th hotswapping 6 xboxes  tongue.gif
Logged

manobano

  • Archived User
  • Full Member
  • *
  • Posts: 174
Halo2 Theorys
« Reply #7 on: September 28, 2004, 03:32:00 PM »

I live in the U.S. and I rented Star Wars Battlefront (SWBF) a few days after it came out to play it on Xbox Live. I have been running the audio exploit on my modded 80 GB hdd upgraded Xbox for a while.....When live 2.0 came out I did the audio exploit fix so that I could still use live.  It worked flawlessly with every live game I played, I just never accessed the Live dashboard itself and never had to update my dashboard.  Anytime I wanted to play a live game I just went straight to the games' log on option for Xbox live and I never had any problems.....until today with SWBF.  When I first rented it and logged onto Xbox Live it worked fine.  Then today when I tried to log on it gave me a prompt saying there was a required update available for Xbox Live and that I MUST download it to be able to play on Xbox Live.  DAMN!  Freaking sucks, I cant get on Live with my audio exploit anymore.....Im assuming I now need to get a modchip with a enable/disable switch so that I can play on live again and in the future. ('cough' Halo2 'cough) If im using a modchip will I be ok for live when Halo2 comes out or will I get any problems logging on similar to what happened to me today with SWBF? Or will I have problems with Halo2 like kieronh is talking about??
Logged

triggernum5

  • Archived User
  • Hero Member
  • *
  • Posts: 896
Halo2 Theorys
« Reply #8 on: September 28, 2004, 03:39:00 PM »

Hardcoding an update directly into the default.xbe would be senseless..  There are more efficient paths they could take to acomplish the same thing.  I could see a special bios being needed to play it if they are really on the ball..  Problem with that is they are required to make it playable on all retail bioses, so they would need to incorporate a hell of alot of resources into something that would be guaranteed to be circumvented within the week.  
I'm guessing MS is pretty wary of putting any xbes out which will read fonts off of D: (For fear of giving Rhenmal the necessary signature for the Utopia Disk:) )  That would be devastating to them..  
MS understands that nothing they can do at the software level will effectively prevent softmodding..  They can only hope that newer machines don't have more exploitable holes..  Its not profitable to play cat and mouse with hackers.  Basically it boils down to depreciating the potential profits based on the number of exploitable boxes on the market, and moving on with production of more secure systems.
They know damn well that if they upgrade a dash that can be redowngraded that that is most likely what is going to happen..  
Logged

total_ass

  • Archived User
  • Hero Member
  • *
  • Posts: 1201
Halo2 Theorys
« Reply #9 on: September 29, 2004, 01:02:00 AM »

heh heh pond.
Logged

triggernum5

  • Archived User
  • Hero Member
  • *
  • Posts: 896
Halo2 Theorys
« Reply #10 on: September 29, 2004, 01:19:00 AM »

Well I wouldn't want to be the first person to pop it into a box with a write enabled eeprom..  And I suppose they could wipe the eeprom on a box with mods detected rather than just banning it if it connects to Live..  But I'd be willing to wager that their legal team advised them against that..  Besides, they lose money when they sell up an xbox..  Screwing one up semi-permanently doesn't sell any more games..
Off the top of my head, the only permanent damage they could do is lock the hdd with a random code..  Doesn't do them any good though, and there are ways to protect yourself against that with a Master password anyways.
Unless they got something so crafty the damage would be worth witnessing the feat of engineering, I'm guessing they'll just do what they always do any whip out a new kernel..
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Halo2 Theorys
« Reply #11 on: September 29, 2004, 02:01:00 AM »

This late in the XBOX 1's life, and with XBOX Xenon in development, I don't expect to see much movement from M$ re: XBOX 1 HW upgrades (such as new Kernels for machines in production, etc.).
Logged

Midri

  • Archived User
  • Newbie
  • *
  • Posts: 14
Halo2 Theorys
« Reply #12 on: September 29, 2004, 02:27:00 AM »

MS won't do it, but they are totaly in their legal right to screw you totaly over when it comes to any changes to you xbox... if you read your agreement that comes with it, you don't own your xbox you "license" it from MS. Meaning they can change anything they want at anytime they want...  They could destroy your eeprom if they wanted, they could wipe your hard drive, but they more then likly won't because its more trouble then its worth.
Logged

mkjones

  • Archived User
  • Hero Member
  • *
  • Posts: 810
Halo2 Theorys
« Reply #13 on: September 29, 2004, 03:34:00 AM »

QUOTE (manobano @ Sep 28 2004, 11:35 PM)
I live in the U.S. and I rented Star Wars Battlefront (SWBF) a few days after it came out to play it on Xbox Live. I have been running the audio exploit on my modded 80 GB hdd upgraded Xbox for a while.....When live 2.0 came out I did the audio exploit fix so that I could still use live.  It worked flawlessly with every live game I played, I just never accessed the Live dashboard itself and never had to update my dashboard.  Anytime I wanted to play a live game I just went straight to the games' log on option for Xbox live and I never had any problems.....until today with SWBF.  When I first rented it and logged onto Xbox Live it worked fine.  Then today when I tried to log on it gave me a prompt saying there was a required update available for Xbox Live and that I MUST download it to be able to play on Xbox Live.  DAMN!  Freaking sucks, I cant get on Live with my audio exploit anymore.....Im assuming I now need to get a modchip with a enable/disable switch so that I can play on live again and in the future. ('cough' Halo2 'cough) If im using a modchip will I be ok for live when Halo2 comes out or will I get any problems logging on similar to what happened to me today with SWBF? Or will I have problems with Halo2 like kieronh is talking about??

Dude if you upgrade to UDE you should be ok smile.gif as its non-dash specific wink.gif

Also, remember you can use Live games with UDE game DVDs bypass the "xboxdash.xbe" on the C drive and boot direct from the disk, meaning you load at a retail state smile.gif

QUOTE
Its not profitable to play cat and mouse with hackers. Basically it boils down to depreciating the potential profits based on the number of exploitable boxes on the market, and moving on with production of more secure systems.


Very good point, I belive M$ are pretty sick of fixing the holes in Xbox 1 they have done ALL they can IMO with the 1.6 the new kernals that stop downgrades and live! updates all over the place.

Theyl be using all the experince we have given them and ploughing it into the Xbox 2 OS development smile.gif

QUOTE
Meaning they can change anything they want at anytime they want... They could destroy your eeprom if they wanted, they could wipe your hard drive, but they more then likly won't because its more trouble then its worth.


They would never do that, it would give them too much bad press. I very much doubt they would ever break an xbox on purpose. Or an xbox 2.

Most they would do IMO is a dash upgrade that looked for unsigned xbes on the HD and delete them.
Logged

Australian Rat

  • Archived User
  • Full Member
  • *
  • Posts: 139
Halo2 Theorys
« Reply #14 on: September 29, 2004, 04:42:00 AM »

tongue.gif
Logged
Pages: [1] 2