ANSWERED Bad Block Error

[MeAnRG]

ok i am reading my nand an during the read i get Error 250 Reading Block 2B0 but it finishes with 03FF what dose this mean an what should i do..:facepalm:

 

[Hackerjac]

what you should do ?
well try using the search function

 

[Goldensavage]

Post the actual text.

You can copy and paste or do a screen log.

Also, load the nand up in 360 flash tool and it should show you any real errors and you can see where they are.

Also there are several threads with people who had the same problem. So a search would have been a start. see here for Martins guide http://team-xecuter.com/forums/showthread.php?t=76014&highlight=error+250

 

[MeAnRG]

what you should do ?
well try using the search function

Post the actual text.

You can copy and paste or do a screen log.

Also, load the nand up in 360 flash tool and it should show you any real errors and you can see where they are.

Also there are several threads with people who had the same problem. So a search would have been a start. see here for Martins guide http://team-xecuter.com/forums/showthread.php?t=76014&highlight=error+250

Thank you an BTW i did a search an i found that exact same link so thank you for pointing that out. an thanks for the info on 360 flash tool i'll post a log.....thanks:facepalm:

 

[hodgie]

what you should do ?
well try using the search function

Lose the attitude. read the rules for the noob forum. it specifaclly says NOT to do this.

 

[Goldensavage]

As an edit. I had one bad block around the same are, went into 360 flashtool, and the error did not show up and the address was not keeping anything important, so i glitched away and everything worked fine.

Some addresses are just not used.

Also as a side not, the nand was perfect on 13604 but had the bad block on 14699

 

[MeAnRG]

Lose the attitude. read the rules for the noob forum. it specifaclly says NOT to do this.

Thanks its cool bro

NandPro v3.0a by Tiros
Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: Nand.bin
Reading
Error: 250 reading block 2B0
03FF
 
Note: Bad Block ID 0x02b0 [Offset 0x00B16000]
-> Block ID 0x02B0 found @ 0x3FF [Offset: 0x0107BE00]
===Analyzed Successfully==================================================

ok so read the tut on remapping but lost cause when i run multi builder i get no errors when it make the ecc file???????or are i not going to get any ???

Just a question on top of this but can i just remapp the bad block with nandhealer an bulid my ecc files then flash or will i get an error???

 

[Goldensavage]

You should be fine that far in.

If 360 flash tool, doesn't throw up any errors then you should be fine

 

[MeAnRG]

You should be fine that far in.

If 360 flash tool, doesn't throw up any errors then you should be fine

Well 360 flash tool in the bad block tab this was in it as above

Note: Bad Block ID 0x02b0 [Offset 0x00B16000]
-> Block ID 0x02B0 found @ 0x3FF [Offset: 0x0107BE00]
===Analyzed Successfully==================================================

so what do you mean by error like this or another i don't want to see LOLZ:facepalm::facepalm: An thanks

 

[hodgie]

If you flash your freeboot with rawflash, that should remap it with no issues. It's not in your .ecc area. You should be good.
That is the error he's asking for.

 

[Gears123]

http://www.team-xecuter.com/forums/showthread.php?t=76014&highlight=bad+block

look at that

 

[MeAnRG]

If you flash your freeboot with rawflash, that should remap it with no issues. It's not in your .ecc area. You should be good.
That is the error he's asking for.

Thanks for that i saw that in nand healer that there were no bad block in my Ecc so that's good this is just the first time i hit the badblock
so i guess i can say 1 out of 25 consoles lol so hanks again

---------- Post added at 15:13 ---------- Previous post was at 15:12 ----------

http://www.team-xecuter.com/forums/showthread.php?t=76014&highlight=bad+block

look at that

TThank you if you have read i have been to that link but thank you for the help....

 

[hodgie]

Bad blocks are a pain in the ecc area, but with rawflash, out of the ecc area OS not.much of a concern. I'm pretty new to dealing with as well. I had a couple hiccups with them.

 

[Martin C]

Good advice given chaps, well done.

Bottom line is this - remapped bad blocks are NOT a problem or error. You just need to know how to deal with them.

Multi_builder/rawflash etc will remap them for you. However as already said, if the bad block is in the first 50 blocks (hex), you may need to manually remap to open in 360 Flash Dump Tool, or after ecc write has finished, or both.

 

[digant]

Hi

I read the post about the need to manually remap a block in case a read error is in range 0x00..0x4F (area used by xell reloaded).
My case seems to be never occurred to anyone.
I have a Jasper Arcade (thus without any HDD) 512MB with CB6751 and I installed TX CoolRunner with the 68nF capacitor between GND and A. Before starting with the dump I verified all the solderings were ok (using multimeters etc...). Everything was ok, so I started to dump the nand.
Below you can see the errors I got in all the dumps I made (I made 8 dumps and they were all the same in a binary comparison).

Block Size: 128KB Block Linits: 0x000000..0x000FFF
File: nand_dump_1.bin
Reading
Error: 250 reading block 188
Error: 210 reading block 189
Error: 210 reading block 18A
Error: 210 reading block 18B
Error: 210 reading block 18C
Error: 210 reading block 18D
Error: 210 reading block 18E
Error: 210 reading block 18F
Error: 250 reading block C58
Error: 210 reading block C59
Error: 210 reading block C5A
Error: 210 reading block C5B
Error: 210 reading block C5C
Error: 210 reading block C5D
Error: 210 reading block C5E
Error: 210 reading block C5F
0FFF

As you can see below, using 360 Flash Tool I saw instead that block 0x0031 and 0x018B were remapped to 0x01FF and 0x01FE.

Note: Bad Block ID 0x0031 [Offset: 0x00651000]
Note: Bad Block ID 0x018B [Offset: 0x032EB000]
-> Block ID 0x018B found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0031 found @ 0x1FF [Offset: 0x041DF000]
=== Analyzed successfully =================================

So 360 Flash Tool reported an error on block 0x0031 although I didn't have any read error on that block. No error was instead reported fot block 0x0C58.

I decided to restore the original nand and I got errors writing on blocks 0x0188 and 0x0C58 (the two blocks where I had read errors). The error code reported by nandpro was 202.
After that, with jtag tool I created and flashed xell. As expected I didn't get any error writing block 0x0031, but xell didn't boot (the green led on coolrunner was flashing all the time every 5 seconds). I decided to use Multi Builder 0.7 (as reported by many users). During creation, It reported to me that CB6751 was not supported for RGH and thus a donor CB6750 was used instead. I flashed xell, and this time it started just in few seconds.
Once retrieved the CPU key, I used again Multi Builder 0.7 to create a retail image. I flashed the image using rawflash (it automatically remapped blocks 0x0031 and 0x018B. I verified that the console booted only using the CR while it didn't boot without CR (when the switch is on PRG).

I kindly ask you (in particular Martin C, the author of many posts in this forum) if:
1) is it possible that block 0x0031 was reported by 360 flash tool as remapped while no read error was encountered on that block? Furthermore that block was mapped on block 0x01FF. According to Martin's post, the first usable block should be 0x0FF8 on a Jasper 512MB.
2) is it ok that block 0x018B is remapped while I got a read error on block 0x0188 (I mean the first error occurred in 0x0188 and not in 0x018B)?
3) is it possible (thus the final RGH image is OK) that you get a read error on a block (in my case 0x0C58) that is not reported by 360 flash tool and thus not remapped during flashing of retail image?
4) is it ok that the retail image boots only with CR?
5) is it possible to restore the original nand only writing the original .bin file (thus obtaining write error on blocks 0x0188 and 0x0C58) or maybe something else has to be performed in order the original dash boots without any problem? I tried to restore the original nand but on boot I got error E79 (thus a problem with HDD or fyle system corruption)
6) to create the RGH image I dumped the nand after flashing the retail image. Is it correct or could it be created with Multi Builder just providing as "nanddump.bin" the retail image file instead of the original nand dump file?

I hope you can provide me an answer even for only one question

thanks

 

[Martin C]

I suggest you read the rules again in relation to thread hijacking...

Infraction given.

 

[wutup]

thanks

 

[xbox360 hacker]

thanks

8 out of your 10 post count are thanks in random threads i believe this to be a way to get your post count up shame on you. Reported