bad blocks wont remap

[fersy]

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.

i dont normally have those on i normally solder the wires straight down to the board but i did that specifically as i was getting the bad blocks and miscomparing nands to see if it would help

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

anyway i tried that one u sent me again martin and still the same no circling green lights or splash screen just 1 glitch cycle on the coolrunner then looks like its doing nothing for 5 secs then bam straight into the dash logon screen. i was wondering if totally erasing the nand and starting from scratch would help?

yes man certainly i will pm you my cpu key.

its on 13604 dash/kernel multibuilder is building a 14699 image but the actual proper dash i dumped my nand from was 13604

i will pm u the key now

---------- Post added at 21:39 ---------- Previous post was at 21:32 ----------

just remembered the console was banned on xbox live. would that make a difference. i didnt think so but just thought id better mention it

 

[Acton1]

i think that may be your prob mate trying to goto 14699 from retail 13604 image

 

[Acton1]

plz try this

http://www.mediafire.com/?7jzg2jl49g939s4



back in 20 mate just going to get some food

 

[Martin C]

i think that may be your prob mate trying to goto 14699 from retail 13604 image

It's NOT a problem. I built a 14699 retail image from his NAND and then created an RGH from there.

fersy - at any rate, you should be able to build a new retail NAND and flash this to your console and it should work.

 

[fersy]

plz try this

http://www.mediafire.com/?7jzg2jl49g939s4



back in 20 mate just going to get some food

cheers mate but still didnt work just straight into the dash (tho 13604 this time) and there was no writing anywhere on the dash even in the preferences tabs etc

It's NOT a problem. I built a 14699 retail image from his NAND and then created an RGH from there.

fersy - at any rate, you should be able to build a new retail NAND and flash this to your console and it should work.

how did you build a retail nand martin? in multibuilder just?

must go check that out now

 

[Martin C]

Yep, you can just use the retail NAND option.

You didn't say what messages you got on screen when using rawflash?

 

[fersy]

the basic gist of the messages is

block 0x53 seems bad
block 0x2e4 seems bad
block 0x3fe seems bad
block 0x3ff seems bad

image written shut down console

anyway i tried making a retail image whilst i was waiting on a response to my last post and flashed it turned off the coolrunner (set it to prog) and powered up the console. guess what same thing except no glitching cos the coolrunners off. no lights on the rol, no splash screen then after several seconds straight into the dash.

i made a 14699 retail image as thats what multibuilder made for me did it matter i think something else is wrong

 

[Acton1]

Now try this its on freeboot 14699 and remapped

http://www.mediafire.com/?lq83t3fc1wpo039

Just need to know when you flash it does it skip bad blocks and does the console boot

Just read through the hole post. A freeboot NXE dash look's the same as A MS retail dash do you know this

 

[Martin C]

Now try this its on freeboot 14699 and remapped

http://www.mediafire.com/?lq83t3fc1wpo039

Just need to know when you flash it does it skip bad blocks and does the console boot

Just read through the hole post. A freeboot NXE dash look's the same as A MS retail dash do you know this

Yes it does - it looks identical. What on earth are you talking about??

fersy - write the image I send you using nandpro instead. Let me know how you get on. If you get any error 202 messages, let me know.

 

[Acton1]

As he said the image i made on freeboot 13604 did boot

I don't think he know's that they look the same martin c what do you think mate

cheers mate but still didnt work just straight into the dash (tho 13604 this time) and there was no writing anywhere on the dash even in the preferences tabs etc

 

[fersy]

As he said the image i made on freeboot 13604 did boot

I don't think he know's that they look the same martin c what do you think mate

i do m8 ive done jtags and now glitches for about 3 years now. i dont do millions but ive done enough (easily over 50) to know that its just ive been lucky enough not to have this problem before.

i will try writing the image in nandpro as martin has suggested but first i think im going to erase the nand completely in nandpro and see if it gives me any errors.

will report back

 

[Acton1]

don't mean to dis you m8 just trying to help hope you get it sorted

i don't use jtag tools as i found a better prog for remapping nands

 

[fersy]

don't mean to dis you m8 just trying to help hope you get it sorted

i don't use jtag tools as i found a better prog for remapping nands

i know m8.

anyway i resoldered my wires (without the long stems martin) and using a command prompt erased the nand with nandpro and guess what, errors on the same blocks when erasing too.

does this mean my nand chip is screwed and if so how come it was able to update from 8199 to 13604 thru ms update if it had this problem as i was getting read errors at the same blocks before i applied the official update. i have a screenshot of the error messages from nandpro

 

[Acton1]

it will give errors as it is the nand chip not the software on it. I have seen bad block's like this on the wii you just need to remap the Hacked nand that you are going to flash to it

I have done 5 RGH and 2 Jtag's in the last 3 weeks and they had bad block's i just remapped the hacked nand and all are working i can not see where you are going wrong ?

 

[ball00]

Surely you'll always get errors on those same blocks if the error is due to a hardware fault in those blocks on the nand chip? As long as the errors are always those same blocks it just means your hardware has those as bad blocks and the information to be written will always have to be remapped elsewhere?

Action1 Types quicker than me apparently!!

 

[fersy]

ok guys thats what i thought but i really wasnt 100% on it. as i said ive been very lucky over the last couple of years in that ive rarely had to deal with bad blocks.
anyway i took martins advice and using nandpro flashed the image he had given me earlier back to the console. as you guys have said same error messages

anyway tried it and hell yeah 1 glitch cycle and booted right up. tried it about 15 times boots like a dream on the 1st glitch every time.
martin you are a legend thanks to you and all you other guys for all the help ive received all day its hugely appreciated.

just a couple of questions in the interest of learning for future reference.

martin, what did you do with the nand i sent to you? was it ok or did you have to fix it or remap it?

why do you guys think that flashing it with rawflash wasnt working and yet it worked with nandpro? could it be that i erased the nand completely before attempting to write it this time?

just wondering because if you dont learn from experiences like these you are doomed to repeat them

thanks again

 

[Acton1]

glad you got it sorted mate.

Plz martin give info on what you did

 

[ball00]

Never sure with rawflash and nandpro. Some people get bizarre results from one or the other. I know rawflash 0.3 is buggy and usually an upgrade to 0.4 fixes it.

Sometimes hardware flashing works and not software flashing and sometimes the other way round. I guess if we all had the same results this forum would be quieter.

Think Martin probably used Voodoo or his own form of black magic as usual. Once I see his namae in a thread I'm always pretty sure it will get resolved (or closed)

 

[Martin C]

fersy - glad you got it sorted. rawflash was obviously getting confused somewhere along the lines. NANDpro will just do what you tell it to and since the blocks were already remapped by xebuild, there was nothing else to do apart from flash it over.

I really don't know why people STILL don't understand about bad block management.

http://www.free60.org/NAND:Bad_Blocks

Yes, I was expecting you to get an error on those two blocks as they were marked as BAD. This is a good thing, since the data (as you already know) had been remapped elsewhere.

If you're working on consoles and it involves reading/writing to the NAND, I strongly suggest you read up on bad block management before touching another.

" and using a command prompt erased the nand with nandpro and guess what, errors on the same blocks when erasing too."

Go back to my first post in this thread and read the words I put in bold...!

 

[fersy]

actually it was in caps not bold

no seriously though the reason i said what i said was not because i didnt read that bit it was because i didnt understand fully the the bad blocks were hardware related i thought they were due to some sort of corruption in the actual nand flash.

i will be the wiser for it and yes i will be reading up more on bad blocks however my several nand dumps all had slight differences (about 8) and somebody on here said that bad blocks or not the nands should have been identical which is why i was asking you did you have to do some sort of repair on the nand i provided you or was it just a case of the 2 blocks being remapped?

you think im a pain in the ass now, what till my achi arrrives on tues