Jtagged jasper black screen

[iloveme28]

My mate jtagged my jasper but is having problems

read the nand 3 times {Using nand x} and 2 matched so made a freeboot image and got no errors

When the xbox is turn on normally it just gets a black screen, but when i press the eject button xellous boots up fine so its not the jtag wires as if it was xellous wouldnt boot

I have never had problems before with xenons or falcons always seems to be bloody jasper which be come a pain

My mate hasnt tried putting the original nand back on yet but has tried updating the dash with the freeboot image with xellous but still nothing

Anyone else has this problem and solved it ???

 

[rocket8080]

How has he done the jtag wiring?

How did he make the freeboot image?

Any bad blocks in the nand?

 

[iloveme28]

How has he done the jtag wiring?

He soldered it, the jtag wiring is fine as if it wasnt xellous wouldnt boot

How did he make the freeboot image?

using the latest freeboot which he has used at 10-15 times before

Any bad blocks in the nand?

yes 1 but he said it had already been reallocated and it only showed up when reading the nand in dos and not in freeboot or nand healer

 

[rocket8080]

How has he done the jtag wiring?

What I mean is he using qsbs or direct wire method? If using the qsb's have you tried the different resistor settings?

Are you using Alternative smc points or db1f1 point?

It may be a possibility that the first two nand dumps has a error. Ive had this twice where ive made three dumps and two matched. Used one of the two dumps to make a freeboot image and got a black screen on boot. I then used the reconstruct button in nandcompare using all three dumps and made a image from that and the black screen was no more.

 

[sebastian79hl]

It may be a possibility that the first two nand dumps has a error. Ive had this twice where ive made three dumps and two matched. Used one of the two dumps to make a freeboot image and got a black screen on boot. I then used the reconstruct button in nandcompare using all three dumps and made a image from that and the black screen was no more.

Yep had the too sometimes.

Since then always make 4 Dumps

Have you tried flashing back the Orig. Image?

Does it work?

 

[iloveme28]

Yep had the too sometimes.

Since then always make 4 Dumps

will try this next time

Have you tried flashing back the Orig. Image?

no

Does it work?

not tried it but my mate used xbr instead {8955 dash} and it works which is very confusing

 

[iloveme28]

What I mean is he using qsbs or direct wire method? If using the qsb's have you tried the different resistor settings?

Are you using Alternative smc points or db1f1 point?

It may be a possibility that the first two nand dumps has a error. Ive had this twice where ive made three dumps and two matched. Used one of the two dumps to make a freeboot image and got a black screen on boot. I then used the reconstruct button in nandcompare using all three dumps and made a image from that and the black screen was no more.

he is using db1f1 point

He has already tried remapping nand image and didnt work and has already tried using nand compare and always comes back with saying there is 1 error

Xbr works fine though but i have been told freeboot can be picky

The only issue with using xbr is it is an old dash and and when i put the likes of newer games in it asks for an update which will screw the jtag up and the only way round it is to use xex loader which is a pain

 

[ando2k9]

i'm the one with the problem

it's a ecc block error at 35D

it's unrecoverable using nandcompare using all 3 images

i've had ecc error blocks before but as there remapped by the nand and aren't fixable i never bothered

i've reamapped the 35d to 3ff and remade a freeboot image and i still get a black screen

xbr works fine though which is puzzling as for the wiring i know it's not the wiring as it's the same wiring i've used on many many jtags

 

[iloveme28]

good i dont have to try and explain it any more nice one ando

 

[manwithoutname]

You need to remap the bad blocks after you compiled freeboot image not before.

 

[ando2k9]

You need to remap the bad blocks after you compiled freeboot image not before.

right so my bad block is at 35d

any chance you talking me through it to make sure im doing it right

 

[rocket8080]

My mate hasnt tried putting the original nand back on yet but has tried updating the dash with the freeboot image with xellous but still nothing

I thought xellous would automatically remapped the freeboot image for him? Or is this not the case?

 

[ando2k9]

I thought xellous would automatically remapped the freeboot image for him? Or is this not the case?

it does mention that it has remapped a block it flashes the updflash.bin fine but still black screens on reboot

 

[manwithoutname]

As far as I know it's not always the case rocket8080. Or at least if it had done it, it won't be where the console expect to find it.

ando2k9, in theory remap the bad block on the freeboot.bin image the same way you done with the original NAND. I'm assuming you are using nandpro to do the remapping manually?

Details of the bad block and where it is located would be useful !

 

[ando2k9]

As far as I know it's not always the case rocket8080. Or at least if it had done it, it won't be where the console expect to find it.

ando2k9, in theory remap the bad block on the freeboot.bin image the same way you done with the original NAND. I'm assuming you are using nandpro to do the remapping manually?

Details of the bad block and where it is located would be useful !

ye i'm remapping it manually

using the following

nandpro freeboot.bin: -r16 35d.bin 35d 1
nandpro freeboot.bin: -w16 35d.bin 3ff 1

heres a screenshot inside 360 flash tool of the original nand

 

[manwithoutname]

Yes, that's the right. Has it worked or not then?

 

[ando2k9]

Yes, that's the right. Has it worked or not then?

pretty sure i tried it last night but i'll try it again in a little while

 

[ando2k9]

still the same after remapping the bad block after creating freeboot

i just don't know what else to do

this has me very puzzled

opened the image in degraded just to check it and it reports that block 0x5d00 is remapped to 0x3ff

but as far as i'm aware 0x5d00 doesn't exist

 

[manwithoutname]

I take it you have verified the CPU key? Also I'm guessing you used the first original dump (non remapped or modified in anyway) to create freeboot which you then remapped after creation?

 

[ando2k9]

I take it you have verified the CPU key? Also I'm guessing you used the first original dump (non remapped or modified in anyway) to create freeboot which you then remapped after creation?

not to be rude mate but i know the cpu key is fine as i can still boot to xell after flashing the freeboot image using the eject button, which then displays the cpu key

also when i flash xbr that boots without a problem

all 3 of my dumps have the same ecc error block therefore there matching dumps and ecc error blocks aren't fixable

tried with all 3 images created freeboot then remapped the bad block, still no difference

just to test my files i got a donor 16mb jasper nand error free, inserted my encrypted kv and config block, made another freeboot image flashed that and still the same.

also remapped the block after i made the freeboot from the donor nand with my kv etc inserted still the same

i've come to the conlcusion that this jasper does not like freeboot in any way shape or form

seems xbr is the only route