Print

[infidelity]

Ok, I previously had the first XBR for 512MB Jasper installed into my NAND, and I it functioned properly. along with Xell.

So I obtained the latest XBR today, and I flashed my raw.kv and my rawconfig.bin to xbr.bin

Now, after the flash was complete, I turned on my 360, and right away, my fan was really loud, and I was shorty presented with the E72 error code. I then tried to power on my 360 from the back USB port, and was given the same result.

So, I changed my rawconfig.bin dump from "EF7 2" to "3DE 2" and reflashed xbr

I turned on my 360, and it turned on, and XBR is working. I was able to load Perfect Dark Zero, and Halo 3 with no crashes (only tested 3 minutes worth)

But my problem now is, I have no Xell?

I boot from the rear USB port, my 360 turns on, but I'm only presented with a black screen?

Is Xell not in this latest xbr build, or should I reflash without the "rawconfig.bin" like my previous version of the first xbr release had?

EDIT Ooooohhhh! You press Eject to boot Xell now! Ok, sorry for the post everyone. (IMG:style_emoticons/default/tongue.gif)

This post has been edited by infidelity: Jan 7 2010, 11:44 PM

[Morning Call]

QUOTE(infidelity @ Jan 7 2010, 05:29 PM)

So, I changed my rawconfig.bin dump from "EF7 2" to "3DE 2" and reflashed xbr

EDIT Ooooohhhh! You press Eject to boot Xell now! Ok, sorry for the post everyone. (IMG:style_emoticons/default/tongue.gif)

your config is not flashed. the reason it gave you %100 fans is because the config was obviously not right to begin with or its corrupted.
the only reason it worked at 3de is because it is now remapped.

i'd suggest getting it to work at ef7 cuz you may have overwrote some important data at 3de which could cause issue.

[infidelity]

well where in hex is EF7 2?

cause i've been doing reads of my 2mb dumps of my 512 nand, to extract the config.

so could someone tell me the exact address in hex?

I made dumps of 2mb for Xell when I first started out

[infidelity]

bump

[UberDeev]

I'm having this same issue. I've started a topic about it on XboxHacker here.

[Looouky]

EF7 is a block, blocks are 4200 address long in hex, so that means

Begins at address 3DBAE00 in hex, or 64728576 in decimal which is at about  61 MBs into the nand. The 2 at the end of the command tells it to read for 2 blocks, 2 blocks is not even close to being 1MB.

Anyhow hope that clears things up for you.

to read a config at EF7 you would do the following

nandpro lpt: -r256 config.bin EF7 2

which tells nandpro to read how ever many megs (which really doesn't matter), but to start at block EF7 and read for 2 blocks(which is why the 256 doesn't really matter) and to write it to config.bin

This post has been edited by Looouky: Jan 27 2010, 10:18 PM