Print

[garus]

It can't be a test point. It's between other traces coming from GPU to RAM, I checked different pictures of other motherboards and there are no testpoints (it's also covered by GPU sink so can't be).

Right now LPT cables are not soldered to motherboard. And I don't think JTAG cables have anything to do with it, error is the same with or without wiring).

[Looouky]

I had forgotten, that you had started testing without the jtag wires. I agree with your conclusion, I guess you now need to test for connectivity with a multimeter.

[n1tro]

I have done several 256mb jasper but so far have tried 2 512mb jaspers using this method and after flashing all i get is black screen and after about 30 seconds it gets RROD...if i flash back the original 2mb nand it works stock perfectly.

i have tried several methods like booting from wired controller...different combinations of flashing free60 then kv then xell-1f etc and still no go..There is another 6 page thread with another person with similar issue and he has also not had success

[garus]

Mine seems tricky, because it doesn't work with stock nand :/ Guess I have to invest in USB flasher to not waste whole day on one flash :/

Is there a tool to check big block 512MB nand backups for bad blocks or corruption yet?

[Looouky]

n1tro,

where you able to get XeLL working? If so try flashing with xbrflash. If not then it might be an issue with free60.bin file for bb nands, maybe the south bridge controller is a little different on the 512 you guys have. If so  then what may work is if you download xbr3 for your console and backup the first 50 blocks from xbr3.bin and flash that instead. Xell should be bootable from the eject button, a dvd drive would be required.

so the commands would be something like this.


nandpro xbr.bin: -r512 xbrxell.bin 0 50
nandpro lpt: -w512 xbrxell.bin 0
nandpro lpt: -w512 kv.bin 1 1

please make sure you use nandpro 2.0b.

Please let me known how it works out for you.

This post has been edited by Looouky: Mar 25 2010, 03:42 PM

[n1tro]

QUOTE(Looouky @ Mar 25 2010, 03:24 PM)

n1tro,

where you able to get XeLL working? If so try flashing with xbrflash. If not then it might be an issue with free60.bin file for bb nands, maybe the south bridge controller is a little different on the 512 you guys have. If so  then what may work is if you download xbr3 for your console and backup the first 50 blocks from xbr3.bin and flash that instead. Xell should be bootable from the eject button, a dvd drive would be required.

so the commands would be something like this.
nandpro xbr.bin: -r512 xbrxell.bin 0 50
nandpro lpt: -w512 xbrxell.bin 0
nandpro lpt: -w512 kv.bin 1 1

please make sure you use nandpro 2.0b.

Please let me known how it works out for you.

thanks I will give this a try! been using the cygnos rev f now on 256mb since they fixed their toolbox to read hynix nand....it reads 66mb in 2-3 minutes...once they fix 512mb hopefully i wont need to use this method anymore!

[luckycool]

hi
   i have  A XENON BOARD WITH  CB id
43 42 07 83 00 00 00 00 00 00 03 C0 00 00 9D

when i convert it
here

it tells me 7 131 0 0


is it exploitable ?

[Looouky]

take a screen shot of your cb line, beacuse i believe you have the wrong line. I need to be able to see what address you picked the line from.

This post has been edited by Looouky: Mar 31 2010, 06:51 PM

[luckycool]

here is

(IMG:http://img704.imageshack.us/img704/8616/cbkey.jpg)

This post has been edited by luckycool: Mar 31 2010, 07:18 PM

[luckycool]

QUOTE(Looouky @ Mar 31 2010, 06:51 PM)

take a screen shot of your cb line, beacuse i believe you have the wrong line. I need to be able to see what address you picked the line from.

hi did you have a look at it mate ?

[Spegs12]

QUOTE(luckycool @ Mar 31 2010, 02:17 PM)

here is

(IMG:http://img704.imageshack.us/img704/8616/cbkey.jpg)

Looks like CB:1923. Not exploitable.

This post has been edited by Spegs12: Yesterday, 12:22 AM

[n1tro]

QUOTE(n1tro @ Mar 25 2010, 09:22 PM)

thanks I will give this a try! been using the cygnos rev f now on 256mb since they fixed their toolbox to read hynix nand....it reads 66mb in 2-3 minutes...once they fix 512mb hopefully i wont need to use this method anymore!

hey sorry for late reply but I was away on vacation. I could not get XELL to load so I couldnt use xbrflash. I even tried using the cygnos revf which did a full dump of nand and then i read the kv and config and put that in the xbr image and when I flash back using cygnos I also get the same problem where it powers on fine but get no audio/video and after 30 seconds I get 3 red lights..I am curious how many people have actually flashed 512mb units using this method and if those nands were hynix or samsung

nandpro dump.bin: -R16 rawkv.bin 1 1

nandpro dump.bin: -R512 rawconfig.bin ef7 2

Looouky do you know the command to get SMC off of original nand? perhaps I need to flash that to the xbr image as well

This post has been edited by n1tro: Yesterday, 04:53 PM

[Looouky]

Does your xbox have an hdmi port, what is your flash config, because from your screen shot it says it is cb 1923 which means not exploitable and also means that your xbox is xenon which well known to give 3rrod.

[cardboardbox]

nevermind.  I used 360 Flash Dump Tool .92 and then cut the first 16 bytes off.  CONSigner likes it now but still doesnt solve my problem.

[domoe]

hi. nice tutorial. i followed instructions in page 1 and get a working xellous but E72 (sometimes E71) error while booting into NXE. any ideas? thank you