Post by: Faluke on November 18, 2010, 01:48:00 PM
I've done this on 3 other systems and it worked perfectly.
This is a Jasper 512mb now running freeboot 12611.
Things I've tried:
MULTIPLE flash drives. I've got the $systemupdate folder sitting on the root of the usb. When I plug it in nothing happens. When I reboot nothing happens.
I've burned the update to a CD and also to a DVD and tried booting with it in the drive and nothing happens. The dashboard shows it as a "mixed meda disc"
Help please!
This post has been edited by Faluke: Nov 18 2010, 09:56 PM
Post by: Faluke on November 18, 2010, 02:31:00 PM
I browsed to the internal memory and saw that it was unformatted. I formatted it and now it took the update.
Post by: syntaxerror329 on November 18, 2010, 04:18:00 PM
QUOTE(Faluke @ Nov 18 2010, 04:31 PM) 
Okay so after process of elimination (I asked myself, "Self, what is different about this xbox than my other ones". It was Jasper and others were xenons. So whats different? Internal memory)
I browsed to the internal memory and saw that it was unformatted. I formatted it and now it took the update.
Good job, i was about to follow your thread to see what the solution was, thanks for sharing!
Post by: AZImmortal on November 18, 2010, 08:29:00 PM
Post by: cardboardbox on November 19, 2010, 11:13:00 AM
Post by: AZImmortal on November 19, 2010, 11:21:00 AM
QUOTE(cardboardbox @ Nov 19 2010, 10:13 AM)
just to confirm, after flashing through xellous or flash360 to get our 360 updated to 12611, we still need to download the update from microsoft, put it on a usb drive, and let the 360 run the update?
Yes, you need the system update files installed on a storage device in order to have things like Kinect functionality and avatar editing.
Post by: cardboardbox on November 19, 2010, 11:53:00 AM
Post by: Faluke on November 19, 2010, 02:09:00 PM
Post by: AZImmortal on November 19, 2010, 02:54:00 PM
Post by: Faluke on November 22, 2010, 09:24:00 AM
I have a 1TB Fat32 drive plugged in and no MS HD. That's it.
I even hooked up a MS HD just to see.
No matter what I had hooked up to it it wouldn't install the 12611 update until I formatted the internal 512MU using the MS dashboard.
Post by: doveman007 on April 03, 2011, 07:25:00 AM
I've also got a BB Jasper with an unformatted MU. I'm not willing to format it as I've got some peculiar badblocks on my NAND which required remapping and I don't want to screw that up by using the MU.
Is there any other way of installing the Avatars. The only game I've had trouble with without them is Toy Soldiers, but I would like to play that (IMG:style_emoticons/default/smile.gif)
EDIT: I thought I might have found the problem in Dashlaunch, and added
noupdater = false
to my launch.ini, but it still didn't work. I only need the $systemupdate folder on my USB stick and not the default.xex don't I? Should it matter if there's other files on the USB stick?
This post has been edited by doveman007: Apr 3 2011, 02:37 PM
Post by: AZImmortal on April 04, 2011, 09:25:00 AM
Regarding your bad blocks, I'm pretty sure that the 360 itself will take care of any bad blocks when you format the memory unit.
Post by: doveman007 on April 04, 2011, 09:48:00 AM
As I recall, the reason why it was advised NOT to format the MU is because writing to it could screw up the flash and stop the box working. I've got the tools needed to flash it again if that happened, but it's a major pain to hook them all up, install them, etc and then I'd be back to square one with an unformatted, unusable MU and no systemupdate, so I don't want to format or use the MU.
Post by: highonxbox on April 04, 2011, 10:53:00 AM
Post by: doveman007 on April 04, 2011, 04:39:00 PM
QUOTE(highonxbox @ Apr 4 2011, 04:53 PM)
Dude thats old school mentality. With latest dashlaunch it doesn't corrupt your mem when you format it. Just give it a try, format the internal MU and see if the update will take. It won't hurt to try.
It certainly could hurt to try if you're wrong.
Until I read something authoritative that says that I can use the MU without messing up my flash I think I'll play it safe.
Post by: boflc on April 04, 2011, 04:52:00 PM
Post by: tk_saturn on April 04, 2011, 06:06:00 PM
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.
Post by: doveman007 on April 04, 2011, 08:39:00 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.
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?
Post by: tk_saturn on April 04, 2011, 08:47:00 PM
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
26/02/2011 06:22
26/02/2011 06:22
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
26/02/2011 06:22
26/02/2011 06:22
1 File(s) 6,100 bytes
Directory of Y:\Content
26/02/2011 06:22
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000
26/02/2011 06:22
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000\FFFE07DF
26/02/2011 06:22
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
Post by: doveman007 on April 05, 2011, 05:08:00 AM
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.
Post by: AZImmortal on April 05, 2011, 09:15:00 AM
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.
Post by: doveman007 on April 05, 2011, 11:53:00 AM
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.
Post by: doveman007 on April 05, 2011, 01:02:00 PM
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?
Post by: highonxbox on April 05, 2011, 01:05:00 PM
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.
Post by: doveman007 on April 05, 2011, 01:17:00 PM
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.
Post by: AZImmortal on April 05, 2011, 07:54:00 PM
Post by: doveman007 on April 05, 2011, 11:50:00 PM
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.
Post by: AZImmortal on April 06, 2011, 08:38:00 AM
Post by: doveman007 on February 04, 2020, 10:11:00 AM
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.
Post by: highonxbox on April 06, 2011, 02:56:00 PM
There, is that clear enough for you?
Post by: budtoka420 on April 06, 2011, 04:04:00 PM
rename $SystemUpdate to $$ystemUpdate on you pen driv
this version of dash launch contains an update blocker that is enabled by default. There are two ways around this if you wish to install the bits and pieces used by the dash for kinect and avatars
1 - place the updater that matches this version on removable media, and rename the folder from $SystemUpdate to $$ystemUpdate
----OR----
2 - place an ini where dash launch can find it and set the noupdater option to false - noupdater = false
number 1 worked perfect for me I had trouble getting the avatar update to install I renamed the system update file and it asked me for an update on boot up
credit to http://www.elitemods...nect-dashboard/ and wabashman for this
Post by: doveman007 on April 06, 2011, 04:25:00 PM
It seems clear that the problem is that my Xbox is not currently recognising USB sticks and it's not going to be able to install the systemupdate if it can't even see the files on it, so I'll have to try and work out what's happened. Probably the easiest thing for me to try is to downgrade to an earlier dashlaunch and see if that makes any difference.
Post by: budtoka420 on April 06, 2011, 04:27:00 PM
Post by: doveman007 on April 06, 2011, 04:29:00 PM
QUOTE(highonxbox @ Apr 6 2011, 08:56 PM)
FORMAT YOUR BLOODY INTERNAL MU. IT SHOULD WORK AFTER THAT.
There, is that clear enough for you?
You're a rather angry little man aren't you. If you'd care to read my post above yours, you'd see that my Xbox isn't currently able to see my USB sticks, so formatting my MU isn't going to make any difference.
Post by: highonxbox on April 06, 2011, 04:51:00 PM
QUOTE(doveman007 @ Apr 6 2011, 04:29 PM)
You're a rather angry little man aren't you. If you'd care to read my post above yours, you'd see that my Xbox isn't currently able to see my USB sticks, so formatting my MU isn't going to make any difference.
No not angry, its just frustrating when someone asks for help, you give them a suggestion and they say, "I don't want to try your suggestion because it may not work" and then after that posts three more pages of runaround.
Post by: doveman007 on April 06, 2011, 05:46:00 PM
QUOTE(highonxbox @ Apr 6 2011, 10:51 PM)
So my follow up question is going to remain the same.
How many more posts are you going to make before you take my original suggestion and even ATTEMPT to format your MU.
You've been given plenty of reassurances that there is no risk in this so why haven't you even tried it yet?
I'm just waiting for you final post that says something like, "I formatted my internal MU and it worked after that... weird. Who would have thought"
No not angry, its just frustrating when someone asks for help, you give them a suggestion and they say, "I don't want to try your suggestion because it may not work" and then after that posts three more pages of runaround.
Well the mature thing to do when someone doesn't want to try your suggestion is to walk away, not get wound up with them and keep insisting that they do so.
Your suggestion made no sense to me as the systemupdates certainly never used to get installed on the MU and I don't believe that's changed (particularly as some 360s don't even have an internal MU), so I didn't see why I should need to format the MU. I'm not in the habit of blinding following suggestions that I can't see any sense in.
Anyway, I've managed to install the update now. I downgraded to DL2.09 and re-formatted my USB stick, but it might have just been coincidence that it worked after doing those. Toy Soldiers is working again, I can now see SysExt in the FSD2 File Manager and SMB access is working too.
There's still the problem that I can't access my USB stick in FSD2 or XexMenu, although it's clear now that this is separate from the systemupdate problem. I certainly used to be able to do so in the latter. I can't recall if I've tried from FSD2 but I think it was working there as well.
Do enjoy your wait for that ego-boosting post you were hoping for from me
Post by: turfster on April 06, 2011, 06:31:00 PM
QUOTE(budtoka420 @ Apr 6 2011, 06:27 PM)
no do this place the update that matches this version on removable media, and rename the folder from $SystemUpdate to $$ystemUpdate otherwise it won't recognize it
That worked. I just did a zephyr that way. Up all night trying to figure out why it wouldn't update. Thanks for the tip.
Post by: highonxbox on April 06, 2011, 09:34:00 PM
Glad you got it working.
Post by: doveman007 on April 07, 2011, 05:26:00 AM
Post by: highonxbox on April 07, 2011, 01:05:00 PM
Post by: doveman007 on April 07, 2011, 07:14:00 PM
The fact that I've now successfully installed the systemupdate without formatting the MU proves that it being unformatted obviously has no effect on installing systemupdates, so why would you think that formatting it would have been a solution?
If I'd followed your suggestion, I'd now have an unwanted formatted MU and I'd have had to flash my NAND again to remove it.
Post by: highonxbox on April 08, 2011, 10:39:00 AM
http://www.youtube.c...feature=related
Post by: Aldanga on April 08, 2011, 12:22:00 PM