cant get xenon board to boot up with xell

[-=Dado=-]

btw, hi all its my first post here

I'm think i need some advice.
I was reading through forum and trying for 2 days to get boot xell on my full jtagable xenon board....

But its my first try for jtag, soo maybe its me....

So i will try to explain everything what i doo, maybe someone could advice me, is it me or the board, or maybe something else?!

Its a xenon board that i updated to 7371 just before i try the jtag.
CB is 1903, I buy that x360 with a problem, distorted picture in some cases, and i fixed it with xclamp metode.
I'm using NAND-X, and have average soldering experience.
Tryed already to resolder every point to be sure its not a soldering problem.

First i tryed with JTAG Tool V2.00, dumped the nand with 1 error,
after i dumped 5 times, and compared every dump, they was all same 0 non-matching blocks, but they all have the same bad block
Block ID 0x02F3, so after i readed that in some cases it might be ok I proceed with write xell through JTAG Tool. After I tryed to boot up X360 i was ending without powering up, no green light, absolute nothing.

Was already scared

After I reconnect NAND-X i clicked on Remove xell and choose the dumped nand, tryed to power up the x360, and it was evrything fine, like before writing xell to nand.

So i searched through forum and found some other ways to do the same,
Got NandProd20d and dumped the nand,with same 1 bad block and i tryed 3 different ways to flash with XBR_Xenon_8955_3.

Flash Config: 0x01198010

First scenario:
dumped nand with 1 same error
nandpro orig.bin: -r16 rawkv.bin 1 1
nandpro orig.bin: -r16 rawconfig.bin 3de 2
nandpro xbr.bin: -w16 rawkv.bin 1 1
nandpro xbr.bin: -w16 rawconfig.bin 3de 2
nandpro usb: -w16 xbr.bin

writing is finishing but with Error: 202 Programming block 2F3

after powering up with eject or power button on console i got just initial setup language and etc... the system settings says the dashboard is 8955

Then I reconnect console with NAND-X and flash the nand with original dump nandpro usb: -w16 orig.bin

booted to old 7371 without problems

Second scenario:
dumped nand with 1 same error
nandpro orig.bin: -r16 rawkv.bin 1 1
nandpro orig.bin: -r16 rawconfig.bin 3de 2
nandpro xbr.bin: -w16 rawkv.bin 1 1
nandpro xbr.bin: -w16 rawconfig.bin 3de 2

then i remapped bad block:
nandpro xbr.bin: -r16 2f3.bin 2F3 1
nandpro xbr.bin: -w16 2f3.bin 3FF 1

nandpro usb: -w16 xbr.bin

booted up (tryed eject and power button)
got the same initial setup, languages, etc... and the system settings says its 8955.

Then I reconnect console with NAND-X and flash the nand with original dump nandpro usb: -w16 orig.bin

booted to old 7371 without problems

Third scenario:
dumped nand with 1 same error
nandpro orig.bin: -r16 rawkv.bin 1 1
nandpro orig.bin: -r16 rawconfig.bin 3de 2
nandpro xbr.bin: -w16 rawkv.bin 1 1
nandpro xbr.bin: -w16 rawconfig.bin 3de 2

then i remapped bad block:
nandpro xbr.bin: -r16 2f3.bin 2F3 1
nandpro xbr.bin: -w16 2f3.bin 3FF 1
nandpro usb: -w16 xbr.bin

and i remapped bad block directly in nand:
nandpro usb: -w16 2f3.bin 3FF 1

and i finished with same result:
booted up (tryed eject and power button)
got the same initial setup, languages, etc... and the system settings says its 8955.

So i now flash the original nand and waiting for some advice....

I got every time the same read block error and programming block error!
Error: 250 reading block 2F3
Error: 202 Programming block 2F3

after all:
Is it enogh just to boot up x360 with eject button pressed or keep pressed while booting to get xell boot up?
I leave NAND-X connected, and didnt reconnect DVDRom while trying boot to xell.
I tryed J2D2 with 0, 330 and 470 resistor settings.

So I don't have a clue what to try anymore!

 

[manwithoutname]

Those who install XBR and still can't get xell to boot were told to update xell to xellous. Yet I have my doubts about this as few people including me sill couldn't get xellous to boot even after doing the upgrade.

At this point there is no need to dump any more images of your NAND. You have already done that enough number of times. As long you got 1 or 2 of the initial dumps then keep those in a safe place.

Try downgrading to the older version of Jtag tool and then writing xell again, or just get the xell.bin for xenon from the older version of jtag tool and flash it manually via nandpro.

Of course you can also download xell from xbins, but I mentioned the previous version of jtag tool because I know it works (that's just me).

 

[-=Dado=-]

Thanx for helping me out, it worked with xellious.