Jump to content
RealModScene

Pawel Posytek

Members
  • Content Count

    1
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Pawel Posytek

  • Rank
    RMS Freshman
  1. Update to Dashlaunch 3.09 and look in the settings if updating is blocked. If it's blocked the 360 is looking for update files in $$systemupdate instead of $systemupdate. your memorystick should be fat or fat32 and not NTFS. You should use update 2.0.16.202.0. If you use anything newer your jtag will become an ordinary 360 without the possibility to Jtag it again since the update burn E Fuses, so be careful with updating your 360. There is a newer update however you should install a freeboot Before you ever update your 360. Freeboot emulate how many EFuses are burned so the update don't burn any more of them. Always use the same system update as your freeboot used and never update if your not sure what it is. It's most likely why they turned of the update feature with dashlaunch so you don't brick your jtagged 360. Don't forget to turn it of again when you are finished so your family members or friends can't update your 360 when they try any new games. New games have a $systemupdate folder and if it's newer then yours it will ask you if you would like to update. it's safer when it's turned of since kids or Girls often update the 360 by mistake. I know atlest 3-4 people that their kids or girlfriend broke their 360 by updating it. Your only option then is to buy a new one. What kind of 360 is it? an old one or a slim? how is it modded? JTAG or Glitch? Nand X CYGNOS or something else? you can update the freeboot diffrently depending on how it*s modded. When you know what you have got just google it and find out how..... Oki, never mind if you solved it, however remmember this it you try to update...
×
×
  • Create New...