Print

[atulb]

OK so, i have been reading for a few days all around the forums. I am having similar problem that much of the people attempting the JTAG exploit. I have rewired my points a few times, but it appears that my points are perfectly correct. I even used multimeter to verify this. OK so i started out by dumping my nand, 1st attempt i got 3 bad block, attempt 2,3,4 i got no bad blocks and all dumps identical. Did the jtag exploit, and flashed Xell and i got Black screen of death with no red lights.

I flash back to original and took the mobo out of the case, and it booted without any hiccups. Flashed Xell once again and booted, i got christmas lights and then i attempted to boot Xell by plugging by controller on the back USB and still just black screen and occasional Red lights. Went back to stock and it booted correctly. After rewiring the Jtag, i decided to instead flash XBR with rawkv.bin and booted it up i was happy to see something on the screen it was E71. I was so sure that i had been very careful in Jtag wires. read around and found that E71 indicated bad flash.

So what i did was read the XBRflash off the nand and then compared it to the XBr flash on the computer, which technically should be the same. Ran them on nandcompare and i was kind of hoping for it too, i got 14 non matching blocks.They are as follows:
1024 block(s) in nand image
14 non-matching block(s) found
197
198
21C
3A6
3A7
3A8
3A9
3AA
3AB
3AC
3AD
3AE
3AF
3DE

I am guess my jtag wires are correct, but why does nandpro never able to write Xell/XBR kernel properly but able to write the orig.bin perfectly. I never got any nandpro read or wrie error Could it be a problem with LPT wires?

Edit:
I remember reading about writing to nand in small block for example 2 mb at a time and then rechecking (before i got my exploitable box). Can anyone guide me through a command that will allow me to specifically rewrite the bad blocks only, so i do not have to flash whole nand and pray.

[atulb]

Partial solution: I erased Nand and i followed by injecting xbr without KV or config. Following this i injected KV directly into the Nand, got XBR to boot but still no xell.

[atulb]

QUOTE(locvez @ Feb 15 2010, 09:09 PM)

Assuming you flashed XBR3, have you tried booting xell using the eject button to power on?

They changed it instead of needing the wired controller in the rear usb port.

Yes boss i have tired that already,  cd ejects and it just boots to modified 8955 dash no matter what. If i try booting from rear usb i get RLOD. I even tried reflashing XBR through Flash360 app. Still no xell. I inspected my flash through Xexmenu/loader and i did not see any xell.bin i dunno if i suppose to. My main goal was XBR, but i am just stumpted as to why i cannot boot Xell.

[atulb]

QUOTE(locvez @ Feb 16 2010, 08:57 AM)

That's weird cause XBR, from the "usual" places anyway, already has xell in it, all it needs is kv + config injected and away you go.....

Are you connecting via hdmi? iirc, xell only supports component (may be wrong) try using that?

Someone in another forum also suggested HOLDing the eject button untill xell boots, worth a shot maybe...

Goodluck!

Also thought the same thing, since i do not have component. However, since re flashing i no longer get black screen of death like previously, it stays black for may be 3-5 secs and then boots to dash. So i know xell is not there at all and that makes no sense.

[atulb]

Still need help, my dvd drive seems to be dead i cannot read the key. I obtained a Compsite/Component cable and updated my xell through flash 360. I still cannot get Xell to boot with eject, it simply boots XBR dash. At one point i even got 2 flashing red lights, but it booted perfectly normal how weird?

Its driving me nuts, as i cannot play any of my original games on the disk. They only option would be to backup on my spare drive and then tx it to the HD, but that is kinda annoying since i have alot of games on dsks.