Print

[Poopmonkey]

I just solved the exact same problem by only inject the kv without the config file.

[s3phir0th115]

QUOTE(Poopmonkey @ Feb 24 2010, 01:37 AM)

I just solved the exact same problem by only inject the kv without the config file.

I already tried it, a few times too.

I get XBR, inject the raw keyvault, flash result to nand with Xellous, wait 30 with the power unplugged, 360 RROD's again.

I'd like to try to load Linux, but none of that works either.

I wish I knew what to do with this thing.  It doesn't look like anything wants to work.

[Treadstone]

QUOTE(s3phir0th115 @ Feb 24 2010, 07:07 AM)

I already tried it, a few times too.

I get XBR, inject the raw keyvault, flash result to nand with Xellous, wait 30 with the power unplugged, 360 RROD's again.

I'd like to try to load Linux, but none of that works either.

I wish I knew what to do with this thing.  It doesn't look like anything wants to work.

When you say you've tried it a few times with and without the config files are you using a fresh xbr image each time or just using the same one? I would start afresh unrar the xbr image, move any bad blocks, inject the kv file
rename file stick it on usb and use xellous to flash

[cubancigaro]

QUOTE(Treadstone @ Feb 24 2010, 03:47 AM)

When you say you've tried it a few times with and without the config files are you using a fresh xbr image each time or just using the same one? I would start afresh unrar the xbr image, move any bad blocks, inject the kv file
rename file stick it on usb and use xellous to flash

Ok so i tried everything ive seen all over the web.
My nand dump opens in 360flash tool and all the info is there.
i inject the raw kv into xbr and flash it to my 360 every way possible
i still no matter what i do can't get this to work.
xmas lights every time.
what else can i try.  

[Treadstone]

QUOTE(cubancigaro @ Feb 24 2010, 05:33 PM)

Ok so i tried everything ive seen all over the web.
My nand dump opens in 360flash tool and all the info is there.
i inject the raw kv into xbr and flash it to my 360 every way possible
i still no matter what i do can't get this to work.
xmas lights every time.
what else can i try.  

Only time i've had xmas lights is when I've flashed a box with the config files.I don't even bother with them now, I would redownload XBR_Falcon_8955_3a.zip do a fresh read of your kv from your nand dump and do a fresh write, you have moved any bad blocks haven't you?

[s3phir0th115]

QUOTE(Treadstone @ Feb 24 2010, 04:47 AM)

When you say you've tried it a few times with and without the config files are you using a fresh xbr image each time or just using the same one? I would start afresh unrar the xbr image, move any bad blocks, inject the kv file
rename file stick it on usb and use xellous to flash

I try fresh ones each time.  Although I didn't think you were suppose to bother with any bad blocks since Xellous is suppose to manage that.

[thwack]

You'll also get christmas lights if the pairing data/LDV values are wrong for the console. What values do you have for these in 360 Flash Tool?

[s3phir0th115]

QUOTE(thwack @ Feb 24 2010, 04:05 PM)

You'll also get christmas lights if the pairing data/LDV values are wrong for the console. What values do you have for these in 360 Flash Tool?

Well, in the flash dump I modified by flashing the original 3 MB backup I made over, the CX section looks like..

CX Sections
CB: 1902   Pairing:0x8E5B9C   LDV:0
CD: 1888   Patch 0:5766      LDV:5
CE: 1888   Patch 1:5787      LDV:6

However, both the XBReboot and the original backup image from Xellous show up as this:

CX Sections
CB: 1921   Pairing:0x000000   LDV:0
CD: 1921   Patch 0:4532      LDV:0
CE: 1888   Patch 1: 0*      LDV:0*
*=section value indicated is shown, but is greyed out.

I'm not sure if that means they are wrong or not, because Xell/Xellous still start with that value.

[thwack]

No - that's correct for XBR......

You could try a 330ohm resistor then instead of the jumper for the JTAG wiring?

[Darth Soap]

QUOTE(thwack @ Feb 25 2010, 09:23 AM)

No - that's correct for XBR......

You could try a 330ohm resistor then instead of the jumper for the JTAG wiring?

Yes i would try the 330ohm resistors. Also have you tried flashing xbr over just with LPT? and then flashed the kv.bin + config.bin over after you've flashed xbr?

I also find that erasing the nand after a bad flash usually fixes the problem: nandpro lpt: -e16

This post has been edited by Darth Soap: Feb 24 2010, 11:55 PM

[s3phir0th115]

QUOTE(thwack @ Feb 24 2010, 05:23 PM)

No - that's correct for XBR......

You could try a 330ohm resistor then instead of the jumper for the JTAG wiring?

If it boots into Xell, wouldn't that mean that the jtag wiring is correct?

Not to say it wouldn't work, but I'm a bit skeptical.

QUOTE(Darth Soap @ Feb 24 2010, 05:54 PM)

Yes i would try the 330ohm resistors. Also have you tried flashing xbr over just with LPT? and then flashed the kv.bin + config.bin over after you've flashed xbr?

I also find that erasing the nand after a bad flash usually fixes the problem: nandpro lpt: -e16

Yeah, I've attempted that with XBR, the result is the same.

I'll attempt the 330 ohm resistor then.

[s3phir0th115]

Well, I replaced the wire with a 330 ohm resistor, and the system still boots up into Xellous ok.

I was hoping it would fix Linux stuff, but it looks like it still hangs.  I was hoping to just do a Linux flashing method this time so I'd leave it less to chance, but I'm not sure if that's an option.

Has swapping to jumper wire with a 330 ohm resistor really been known to fix xbreboot issues?  Because the original method booted Xell/Xellous fine, and it seems to boot Xell/Xellous the same with the jumper wire replaced with a 330 ohm resistor.

[s3phir0th115]

Well, as an update, I tried a different install method, and that didn't turn out well either.

I got my 3 MB image backup, and flashed it over the front of the full image from Xellous, and then opened in Degraded.

Then I got the XBR image, injected my keyvault in, remapped all of the remapped bad blocks Degraded pointed out with nandpro, and then proceeded to install via LPT.  It still results in an error 0022.

This is just flat out nonsensical.  I can't find any reason for this to be happening still.

Nor can I find a reason for Xell/Xellous to not Linux or even any libxenon homebrew I've tried.  It just hangs on everything.

Are there any potential causes for these problems?  I'm running out of options here.

[s3phir0th115]

Got it.  

Apparently the issue was related to nand corruption.  So I erased the nand with nandpro, flashed on the XBR image, read it out twice to make sure it was ok, put my keyvault in, and checked it too, then the 360 booted up.

Naturally I'm quite thrilled.