bad blocks wont remap

[fersy]

ok well either way it didnt work.

i took a fresh untouched original nand dump

ran i through multibuilder selected falcon, reset glitch and no dashlaunch patches (i just decided to try none to see if it made a difference)

anyway it made the nandflash.bin,
i stuck it on a usb pen with rawflash 4, booted into xell let it do its thing got the same bad blocks error messages as before but this time it said "image written"

shutdown the console, pulled the plug out the back for a minute plugged it back in and tried it but just the same thing no lights on the front and straight to the dash with no intro.

 

[DayvG]

Ok, well that's what I'd expect to see with rawflash after the flash. As for your booting issue that's beyond me bro. Maybe one I the more seasoned guys on here can help. Does the console function as normal one it's at the dash?

 

[fersy]

it seems to but ive not tested it extensively as i just assumed it was due to the bad blocks.

just wondering, i was comparing my nands there in total commander and they are not the same there are like 8 and 10 differences between them, is that normal when you have bad blocks or should they all be the same because the bad blocks were all in the same place?

was thinking of trying to write the original nand back and see if it boots but will it work if it has bad blocks?

 

[Martin C]

flash your original, UNTOUCHED NAND back to the console and make sure it boots.

We'll go from there.

 

[DayvG]

Did you compare all of your original NAND dumps that you first made? If you did you should have a minimum of 2 matching dumps before you do ANYTHING else. If the original dumps were matching and now they're not then you've fcucked them up yourself dude. The original dumps should never be used directly. If you're gonna play with them, make a copy and use that. The fact that your "original" dumps now have differences brings me back to Martins post. Mess with the original dumps at your peril. I wanna give you some advice buddy, but I don't have any.

 

[Martin C]

I'll give advice - don't F*ck with your original NAND dump unless it's absolutely necessary or you know what you're doing.

 

[DayvG]

flash your original, UNTOUCHED NAND back to the console and make sure it boots.

We'll go from there.

Question is, does he have any?

 

[fersy]

flash your original, UNTOUCHED NAND back to the console and make sure it boots.

We'll go from there.

Did you compare all of your original NAND dumps that you first made? If you did you should have a minimum of 2 matching dumps before you do ANYTHING else. If the original dumps were matching and now they're not then you've fcucked them up yourself dude. The original dumps should never be used directly. If you're gonna play with them, make a copy and use that. The fact that your "original" dumps now have differences brings me back to Martins post. Mess with the original dumps at your peril. I wanna give you some advice buddy, but I don't have any.

ok i tried flashing the original image back. it boots as far as the swirly xbox slpash screen then e71.

i havent touched the original nands as i put them in a folder then made a copy of that folder and work with those nands. im starting to think the original dumps were not good they didnt match when i compared them originally but i put it down to the bad blocks because they were always in the same place even after resoldering everything and dumping more nands so i thought the bad blocks were why i was getting slight differences in the compare stage. especially due to the fact since ive started to use this nandx a few months back ive never had 1 miscompare or bad read ever.

which brings me back to my question if the nands have bad blocks should they still compare as identical?

 

[DayvG]

You shouldn't have gone any further until the dumps matched. Even with bad blocks they should match.

 

[noobnotforlong]

Nands with bad blocks compare without errors your soldering was prob bad to your nand x

Sent from my HTC Desire Z using Tapatalk

 

[Martin C]

upload one of your NANDs and PM me the CPU key.

 

[DayvG]

upload one of your NANDs and PM me the CPU key.

You can't get better help than that.

 

[fersy]

ok martin will do that now. they have definitely not been altered since they were created because i checked the properties in windows and it would have a different time if modified.

anyway i will do that now.

ps i really dont think it was my soldering as i did it twice and my soldering skills are good and i actually sink the wires into the solder in the holes to ensure a good connection.

anyway i will upload that file

---------- Post added at 17:21 ---------- Previous post was at 17:12 ----------

ok heres a nand

http://www.mediafire.com/?53cn56v0d377udc

and the cpu key will be in your pm's. thanks a lot

 

[fersy]

ok as requested by martin here are my install/wiring pics. bear in mind the nand x wiring is still connected in case you are wondering what the extra wires are at the top and the green blue and yellow cable havent been tidied down with tape yet at the topside of the board as i unsoldered them from the coolrunner once or twice to get the best position for them. also in case you are wondering why the blue wire is through a different hole its because when i run the green and blue together underneath the board they seem to interfere with each other and i get just a flashing green light in the middle of the rol and no boot or green light on coolrunner.

also bear in mind this is glitching to xell on the first cycle every single time

those were the best pics i could get

 

[Martin C]

What bothers me is the amount of exposed wire you have on your NAND cables.

If you're booting to XeLL, remove your NAND-x wires for now and do all flashing from Rawflash v4. Also, if you're booting to XeLL, there's nothing wrong with your CR wiring.

Try the image I built for you again and tell me what rawflash says once finished.

 

[Acton1]

well did it work mate ?

 

[fersy]

only back from shop. will do it again now. thats not bare wire as such on the nand cable its the stems from a few old resistors i had laying about because it makes it easier to sink them right into the holes which i feel no only gives me a better connection but also make it easier to see that nothings touching in the group of 5 wires beside each other

 

[Acton1]

wire's look ok to me mate

What kernel is it on ?

 

[Martin C]

only back from shop. will do it again now. thats not bare wire as such on the nand cable its the stems from a few old resistors i had laying about because it makes it easier to sink them right into the holes which i feel no only gives me a better connection but also make it easier to see that nothings touching in the group of 5 wires beside each other

It's non-insulated connections which can be affecting by electrical interference/inductance. They're data/SPI lines so will affect your ability to read/write correctly. Long and short of it is you shouldn't have that amount of wire exposed.

 

[Acton1]

i would like to have a try if you can pm me your cpu key

As i have had 3 xbox's like this and now they work. But need to know your kernel version first