Print

[boflc]

memunitint is safe to use.

[tk_saturn]

If in doubt, simply do a full back up of the NAND through Xellous etc beforehand. If you then encounter an issue you can just flash it back. Xellous will do a full 256MB/ 512MB dump including the MU.

Bad blocks are not an issue, most BB Jaspers will have a atleast one because the NANDs are much larger. Your console can also develop additional bad blocks at any time just through normal use. Your badblocks are remapped to where they are, the MU is outside of that area and so using the MU won't change where they are remapped to.

No, you can't copy the update from any device to the HDD. A HDD normally keeps a copy of the systemupdate it it's root, but that's just incase you put that HDD onto another console which hasn't had the dashboard updated. I believe the update the console is using is located in partition 0.

No I don't intentionally use the MU as I prefer to use a 2TB drive for games and 4GB memory stick for saves/ profiles. Some games have saved data to the BB MU though, probably from me selecting the wrong memory device.

[doveman007]

Yeah, that's a good idea to do a full NAND backup, which will cover the remapped blocks wherever they are.

I can't remember exactly what the issue was, but there must have been a problem with use of the MU overwriting the NAND/remapped blocks or else there wouldn't have been the advice to leave it unformatted to prevent it being used. Perhaps that's been sorted now, or maybe the problem only manifests once certain parts of the MU are written to, so it might not happen if only a small amount of data has been written to it.

I still don't get why I can't manually copy the update to the HD (from USB or FTP it over). If, as you say, an un-updated console gets the systemupdate from the HD root and writes it to partition0 (which is on the HD), then surely putting the update on the HD would work. Or are you saying that the copy is stored in partition0 and it gets installed to somewhere from there?

[tk_saturn]

CODE

 Volume in drive Y is SysExt
 Volume Serial Number is 0B30-0A45

 Directory of Y:\

09/11/2000  17:15              .
26/02/2011  06:22             6,100 system.manifest
26/02/2011  06:22              Content
26/02/2011  06:22              20314300
26/02/2011  06:22              32000100
               1 File(s)          6,100 bytes
               4 Dir(s)     122,863,616 bytes free

Y:\>dir /a/s
 Volume in drive Y is SysExt
 Volume Serial Number is 0B30-0A45

 Directory of Y:\

26/02/2011  06:22              .
26/02/2011  06:22             6,100 system.manifest
26/02/2011  06:22              Content
26/02/2011  06:22              20314300
26/02/2011  06:22              32000100
               1 File(s)          6,100 bytes

 Directory of Y:\Content

26/02/2011  06:22              0000000000000000
               0 File(s)              0 bytes

 Directory of Y:\Content\0000000000000000

26/02/2011  06:22              FFFE07DF
               0 File(s)              0 bytes

 Directory of Y:\Content\0000000000000000\FFFE07DF

26/02/2011  06:22              00008000
               0 File(s)              0 bytes

 Directory of Y:\Content\0000000000000000\FFFE07DF\00008000

26/02/2011  06:21        15,048,704 FFFE07DF00000002
26/02/2011  06:21        10,170,368 FFFE07DF00000006
26/02/2011  06:21        33,116,160 FFFE07DF00000008
26/02/2011  06:21           978,944 FFFE07DF00000001
               4 File(s)     59,314,176 bytes

 Directory of Y:\20314300

26/02/2011  06:21        15,503,360 AvatarEditor.xex
26/02/2011  06:21         4,345,856 BiometricSetup.xex
26/02/2011  06:21           114,688 Dash.AttractionScreen.xex
26/02/2011  06:21           835,584 dash.ExtraAVCodecs.xex
26/02/2011  06:21           421,888 Dash.FieldCalibration.lex
26/02/2011  06:21         1,736,704 dash.firstuse.xex
26/02/2011  06:21           466,944 Dash.MP.Offline.lex
26/02/2011  06:21           434,176 dash.natalpregame.xex
26/02/2011  06:21         1,458,176 dash.NuiFirstUse.xex
26/02/2011  06:21           278,528 dash.nuihub.xex
26/02/2011  06:21         1,454,080 Dash.NuiTroubleshooter.lex
26/02/2011  06:21         1,404,928 dashnui.xex
26/02/2011  06:21           413,696 Guide.AvatarMiniCreator.xex
26/02/2011  06:21           249,856 Guide.NuiTroubleshooter.xex
26/02/2011  06:21         2,756,608 livepack.xex
26/02/2011  06:21            11,485 mediasite.xzp
26/02/2011  06:21            16,384 natalsu.xex
26/02/2011  06:21            24,576 nuihud.xex
26/02/2011  06:21           126,976 Xam.Community.xex
26/02/2011  06:21            81,920 Xam.LiveMessenger.xex
26/02/2011  06:21            20,480 Xam.WordRegister.xex
26/02/2011  06:21           573,440 XimeDic.xex
26/02/2011  06:21            69,632 XimeDicCh.xex
26/02/2011  06:21           368,640 ximedicex.xex
              24 File(s)     33,168,605 bytes

 Directory of Y:\32000100

26/02/2011  06:21           512,000 Xna_TitleLauncher.xex
               1 File(s)        512,000 bytes

     Total Files Listed:
              30 File(s)     93,000,881 bytes
               7 Dir(s)     122,863,616 bytes free

[doveman007]

QUOTE(tk_saturn @ Apr 5 2011, 02:47 AM)

Copying the systemupdate folder to the root of partition3 of your HDD would be no different than having it in the root of a USB stick/ CD/ DVD. If it's not working from the root of a USB stick, I can't see how it would work from the root of the HDD.

I assume you've already tried it, but try clearing the systemcache in the dashboard. I also assume you're using teh correct dashboard update http://download.micr...e_12625_USB.zip

You could also check out the contents of the SysExt device in FSD2, which on mine is:

OK, I'll try clearing the systemcache. I'm running 12611, so that's the wrong update for me. I've already got the right one thanks.

I'll have a look at the SysExt contents as well to compare with yours.

[AZImmortal]

QUOTE(doveman007 @ Apr 4 2011, 06:39 PM)

I can't remember exactly what the issue was, but there must have been a problem with use of the MU overwriting the NAND/remapped blocks or else there wouldn't have been the advice to leave it unformatted to prevent it being used. Perhaps that's been sorted now, or maybe the problem only manifests once certain parts of the MU are written to, so it might not happen if only a small amount of data has been written to it.

The problem that you're referring to was resolved a long time ago, and if you're on 12611 now, then you have nothing to worry about.  Saving to the internal memory unit on older versions of the JTAG hack would cause it to write beyond the memory unit partition if you filled it up past a certain point.

[doveman007]

QUOTE(AZImmortal @ Apr 5 2011, 03:15 PM)

The problem that you're referring to was resolved a long time ago, and if you're on 12611 now, then you have nothing to worry about.  Saving to the internal memory unit on older versions of the JTAG hack would cause it to write beyond the memory unit partition if you filled it up past a certain point.

Cheers for the info. I'll just format the MU then.

[doveman007]

Err, can you educate me as to what SysExt actually is, as I don't see it in my FSD2 File Manager  

SMB access isn't working for me either and the 360 doesn't show up in my XP Workgroup (which is named Workgroup, same as with FSD2). My firewall (Ashampoo Free) is set Allow All on the LAN/local connections, so that's not the problem. With "SMB in File Manager" enabled in FSD2, it just freezes for a few seconds when I select SMB and no files get displayed. Does the 360 have a name or should I be able to access it with "\\192.168.1.5" from XPs Start - Run box?

[highonxbox]

QUOTE(doveman007 @ Apr 5 2011, 11:53 AM)

Cheers for the info. I'll just format the MU then.

Thats what I have been saying all along, its cool, don't sweat it, just format the MU.

[doveman007]

I will if necessary, but I prefer to have it unformatted so that I don't accidentally save to it as I prefer everything to be on the HD.

It's never been necessary to use the MU for systemupdates in the past, so I want to try other approaches first. Of course, if there's some definite info that says it's now required to use the MU for systemupdates I'll stop wasting my time, but I'd be surprised if that was the case and that they're not actually copied from the MU to be installed elsewhere, in case the MU is formatted again later, which would wipe the systemupdates if they're installed on the MU.

Perhaps someone who's installed the Avatar updates and is not using their MU for anything else (or could copy any saves from there to the HD), could try formatting the MU and see if that causes them to lose the updates.

[AZImmortal]

I might have overlooked this info, but did you mention what happens exactly when you try to update?

[doveman007]

Nothing happens at all!

However, I tried to access my USB stick in XexMenu earlier and it didn't show up. It's the same stick that's worked previously, I haven't re-formatted it or anything and I can see on the stick that it's got a connection to the Xbox, so I don't know what's going there. I haven't tried it in the rear socket yet, so I'll give that a go.

[AZImmortal]

Did you download the update directly from Microsoft?  If not, try this: http://download.micr...Update12611.zip

[doveman007]

I hadn't been able to find it on MS' site, so thanks for that.

Still didn't work though. I've just tried another FAT32 formatted USB stick and XexMenu isn't picking that up either, so there seems to be something about DashLaunch 2.11, FSD2 or Freeboot/Dash12611 that's stopping USB sticks being recognised.

[highonxbox]

FORMAT YOUR BLOODY INTERNAL MU. IT SHOULD WORK AFTER THAT.

There, is that clear enough for you?