Jump to content


Photo

Freeboot 0032 - Dont Use Mu! Same Corruption Problem As Xbr3!


  • Please log in to reply
7 replies to this topic

#1 Pacotera

Pacotera

    X-S Member

  • XS-BANNED
  • Pip
  • 108 posts
  • Xbox Version:unk
  • 360 version:unknown

Posted 03 May 2010 - 07:22 PM

http://www.xboxhacke...p?topic=15039.0

A contacted a friend with a BB jasper here in Brazil and he had the same problem. Was playing normally with freeboot and after a few saves when he turned off and turned on only the green light blinking.

Jester always said that freeboot didnt have the same problem of MU corruption that XBR did but i guess this is not the case sad.gif



#2 NaughtyTester

NaughtyTester

    X-S Member

  • Members
  • Pip
  • 81 posts
  • Location:Texas the only place to be BITCHES !!!!
  • Interests:Anything I like.
  • Xbox Version:v1.1
  • 360 version:v4.0 (jasper)

Posted 03 May 2010 - 08:52 PM

I'm having same problem sad.gif

#3 Maximize

Maximize

    X-S X-perience

  • Members
  • PipPip
  • 334 posts

Posted 04 May 2010 - 04:59 PM

when you say MU are we talking about the memory cards? or any memory including hdd?

#4 Pacotera

Pacotera

    X-S Member

  • XS-BANNED
  • Pip
  • 108 posts
  • Xbox Version:unk
  • 360 version:unknown

Posted 04 May 2010 - 05:29 PM

QUOTE(Maximize @ May 4 2010, 04:59 PM) View Post

when you say MU are we talking about the memory cards? or any memory including hdd?


internal memory used on 256mb and 512mb arcade editions

#5 brandogg

brandogg

    X-S Messiah

  • Members
  • PipPipPipPipPipPipPip
  • 3,091 posts
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 04 May 2010 - 09:39 PM

Erase the NAND with "-e" in Nandpro, then flash the 360 again. The solution is to *never* format the MU, then you can never accidentally write to it.

#6 Maximize

Maximize

    X-S X-perience

  • Members
  • PipPip
  • 334 posts

Posted 05 May 2010 - 02:24 AM

so if you save to hdd strictly will you corrupt it? when it does get corrupted is it just the "free" space the space that isnt for the firmware?

#7 moja

moja

    X-S Young Member

  • Members
  • Pip
  • 59 posts
  • Xbox Version:v1.4
  • 360 version:v4.0 (jasper)

Posted 05 May 2010 - 04:02 AM

QUOTE(brandogg @ May 4 2010, 09:39 PM) View Post

Erase the NAND with "-e" in Nandpro, then flash the 360 again. The solution is to *never* format the MU, then you can never accidentally write to it.



I think the point is we were all kinda hoping that the internal memory corruption was fixed by now. I for one am affected and let down by this.

Edited by moja, 05 May 2010 - 04:05 AM.


#8 brandogg

brandogg

    X-S Messiah

  • Members
  • PipPipPipPipPipPipPip
  • 3,091 posts
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 05 May 2010 - 04:37 AM

I had the issue too - but it forced me to go ahead and re-JTAG my console instead of sending it off, and now I've done 3 of them as a result. It sucks, but if you have a way to run the hack on your PC, it's worth learning how to do it yourself.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users