DO NOT USE INTERNAL MEMORY ON A BIG BLOCK JASPER!

[Neptune]

I have been going back and forth with some people on this. I hope someone will sticky it and lock this for now.

[30:01:10:13:23] <Redline99> because xbr_3 screwed up the block numbers
[30:01:10:13:23] <mastag21> i just trash the MU partition
[30:01:10:13:23] <Redline99> its difficult to explain
[30:01:10:13:23] <mastag21> i always delete MU partition
[30:01:10:13:23] <mastag21> too many people's systems been getting fubar
[30:01:10:13:23] <Redline99> but I will release a new bbm when a new xbr is released
[30:01:10:13:23] <Redline99> MU is not usable, using it at all screws up flash

Straight from Redline99 =)

For your information, to delete the MU partition using multiple methods:

nandpro lpt: -e256 1001
nandpro lpt: -r512 1001

in UsbJtagNT do a:

flshdct 0
"erase 4200000 1ce00000" for 512MB




flshdct 0
"erase 4200000 e700000" for 256MB

[sandungas]

Yes, there was lot of comments about MU thats reduces their size... corruption, etc...
Is not usable, but if you erase it.... you are missing your bad blocks (bad blocks in MU area... in the case there was any)

Im not sure if there is another way to find them after erasing (can be detected with a full re-write of the MU, but this is long)

[Neptune]

You would have to read it anyway to find out where the bad blocks are...

When/If that issue is fixed, you could build a temp image or something and flash with the 360Flash tool and read it back to find them.

Honestly, none of us should have any use for internal MU anyway. None of the tools can access it yet (AFAIK) XeXMenu, etc. So if you crippled your content you would have a hell of a time fixing it, etc.

[sectorseven]

Does this warning apply to game saves as well?

[bidomo]

Does this warning apply to game saves as well?

if they're inside a big block jasper MU (which stands for Memory Unit???

If your answer is yes, CONGRATS! You should learn to read!
If answer is no, you should learn to understand what you read.

So...

If you have a external Memory unit or hard disk (does not matter if you hard wired it to the mobo), this warning does not apply.

[nknave]

the most common time to currupt the NAND is when we update to install the Avatars system, it will look to use MU if it's formatted, than corruption will occur.

The best thing to do is not format internal MU after XBR Flash, and use HDD all the time till we get XBR v4 fixing this issue.



Cheers.

[Lush]

thanks for the info... looking forward to an updated xbr and bbm...

[Arakon]

hmm.. maybe that would be a nice feature to add by redline, for his flash360.. an option to wipe just that block. Cause I don't really fancy the thought of taking apart the whole console again to attach my flasher just to wipe that one block.

[dtrmad2004]

Does the corruption only happen to BB japsers that have bad blocks?

I just did a 512 Jasper for someone last night and now the MU is showing up as 256!

[Arakon]

no, all big block jaspers.

[dtrmad2004]

Ok, Thanks. Will ask the owner what they want to do.

[jelle2503]

i can confirm do not use it.. it does work to some extent as i have put Xexmenu on the MU, but mess with it too much and it will brick... neither your XBR or Xell with boot afterwards, meaning you're forced to reflash with LPT/USB < which sucks

I had this issue.. went back to flash with LPT, nandpro errored out on me bigtime for some weird reason, but did flash a few blocks in the beginning... It got XBR to boot (with weird ROL issues), after that I just used Flash360.. worked fine

[Redline99]

[30:01:10:13:23] <Redline99> because xbr_3 screwed up the block numbers
[30:01:10:13:23] <mastag21> i just trash the MU partition
[30:01:10:13:23] <Redline99> its difficult to explain
[30:01:10:13:23] <mastag21> i always delete MU partition
[30:01:10:13:23] <mastag21> too many people's systems been getting fubar
[30:01:10:13:23] <Redline99> but I will release a new bbm when a new xbr is released
[30:01:10:13:23] <Redline99> MU is not usable, using it at all screws up flash

Straight from Redline99 =)

To clarify, the xbr_3 for large block is a hybrid image meaning it has some parts from a small block and some parts from a large block.  The block numbering issue is not directly related to the MU issue. It causes issues with apps such as bad block mover. The MU corrupting thing something else.  The nand is not an easy structure to mess with and it is a long learning curve for everyone.  So just be patient and I'm sure issues will be addressed as quickly as possible. 

I will re-release bad block mover for large block when a new xbr for large block is released that is not a hybrid.  The issue is that it cannot remap blocks from the "hybrid" section reliably because the block ids are not valid. So even if they are remapped it seems that they cannot be located without metadata fixes.  This can be done, but its better to just wait for a new xbr that isn't a hybrid.

[crimpshrine]

hmm.. maybe that would be a nice feature to add by redline, for his flash360.. an option to wipe just that block. Cause I don't really fancy the thought of taking apart the whole console again to attach my flasher just to wipe that one block.

No need to attach the flasher..

All you have to do is bootup Gentoo Linux under xell and use xbrflash to erase everything after 64 megs.

./xbrflash -ep

[doveman]

Is there any way I can extract my game saves and profiles from the 512MB NAND before I flash it?

I realize now I should have just copied them from my Internal Memory to my HD using the normal dashboard, but I've wired up the JTAG points now and really don't fancy risking bodging things up by desoldering them again.

I could backup the entire NAND over USB, but I'm not aware of any way to then extract the stuff I want from that to copy to the HD.

[Arakon]

You don't need to desolder anything. Fire it up and copy them to a HDD.

[doveman]

Nice one. That was easy

I thought I'd read that the MS dash wouldn't work with the JTAG wired up but I must have got my wires crossed (not those ones hopefully!) and it's that XBR won't boot without doing the JTAG.

[ReverseAffect]

[30:01:10:13:23] <Redline99> because xbr_3 screwed up the block numbers
[30:01:10:13:23] <mastag21> i just trash the MU partition
[30:01:10:13:23] <Redline99> its difficult to explain
[30:01:10:13:23] <mastag21> i always delete MU partition
[30:01:10:13:23] <mastag21> too many people's systems been getting fubar
[30:01:10:13:23] <Redline99> but I will release a new bbm when a new xbr is released
[30:01:10:13:23] <Redline99> MU is not usable, using it at all screws up flash

Straight from Redline99 =)

To clarify, the xbr_3 for large block is a hybrid image meaning it has some parts from a small block and some parts from a large block.  The block numbering issue is not directly related to the MU issue. It causes issues with apps such as bad block mover. The MU corrupting thing something else.  The nand is not an easy structure to mess with and it is a long learning curve for everyone.  So just be patient and I'm sure issues will be addressed as quickly as possible.  

I will re-release bad block mover for large block when a new xbr for large block is released that is not a hybrid.  The issue is that it cannot remap blocks from the "hybrid" section reliably because the block ids are not valid. So even if they are remapped it seems that they cannot be located without metadata fixes.  This can be done, but its better to just wait for a new xbr that isn't a hybrid.

well that's good to know your on it, after they update it, you can then do your magic
can you call them on the phone and tell them to kinda hurry up....this 256 bb jasper is a waiting...lol

question?
you stated,
The MU corrupting thing something else.
could this be due to something in the image or user input causing the nand to write to a block, thinking it's the extra memory area?
block ids are not valid .......is this the issue and mapped someway to the extra space area? instead of the valid area(s)?
or is it just the answer of ,because it's using the hybrid image...

[Redline99]

I don't know really. We just need to be patient while it is worked out.

[ReverseAffect]

I don't know really. We just need to be patient while it is worked out.

will do...thanks