Jump to content


Photo

Error Reading Block With Lpt


  • Please log in to reply
6 replies to this topic

#1 fabiosuper14

fabiosuper14

    X-S Enthusiast

  • Members
  • 6 posts

Posted 13 July 2012 - 06:28 PM

Hi all. I have a problem with the reading of a falcon with NAND device db25 (LPT).
I made ​​a lot of image (nandpro30a) and I've only ever encountered an error: error: 250 Reading block 195.
I tried to resolder (with wires as short and wide) and soldering a diode but does not work.
I tried with another computer, changing BIOS settings, with another version of nandpro, but does not work.
How can I fix? Thanks ^ ^

#2 Aldanga

Aldanga

    X-S Hacker

  • Head Moderators
  • PipPipPipPipPipPip
  • 2,721 posts
  • Gender:Male
  • Interests:Hardware,software,coding,algorithms, troubleshooting, tinkering with anything I can get my hands on.
  • Xbox Version:none
  • 360 version:v5.0 (360S - trinity)

Posted 14 July 2012 - 12:52 AM

Is this the first TSOP you've tried dumping with this particular LPT flasher?

#3 fabiosuper14

fabiosuper14

    X-S Enthusiast

  • Members
  • 6 posts

Posted 14 July 2012 - 01:32 AM

QUOTE(Aldanga @ Jul 13 2012, 11:52 PM) View Post

Is this the first TSOP you've tried dumping with this particular LPT flasher?

Yeah, I've solved a lot of errors remained just that and I can not fix it

Edited by fabiosuper14, 14 July 2012 - 01:33 AM.


#4 Aldanga

Aldanga

    X-S Hacker

  • Head Moderators
  • PipPipPipPipPipPip
  • 2,721 posts
  • Gender:Male
  • Interests:Hardware,software,coding,algorithms, troubleshooting, tinkering with anything I can get my hands on.
  • Xbox Version:none
  • 360 version:v5.0 (360S - trinity)

Posted 14 July 2012 - 01:33 AM

I do not know what you just said.

#5 finalman

finalman

    X-S Senior Member

  • Members
  • PipPip
  • 202 posts
  • Xbox Version:v1.6b
  • 360 version:v4.0 (jasper)

Posted 14 July 2012 - 02:13 AM

If the error is always at that block no matter what computer you use or how many times you resolder then that means that block is bad and cannot be read. The 360 will have already remapped that block to the end of the nandchip data area.

#6 fabiosuper14

fabiosuper14

    X-S Enthusiast

  • Members
  • 6 posts

Posted 14 July 2012 - 03:34 AM

QUOTE(finalman @ Jul 14 2012, 01:13 AM) View Post

If the error is always at that block no matter what computer you use or how many times you resolder then that means that block is bad and cannot be read. The 360 will have already remapped that block to the end of the nandchip data area.

Ok. I do not remap the dump, but proceed with the creation of the files ECC
(with the badlock). Correctly?

flash dump tool: Block ID 0x0195 found @ 0x03FF

#7 finalman

finalman

    X-S Senior Member

  • Members
  • PipPip
  • 202 posts
  • Xbox Version:v1.6b
  • 360 version:v4.0 (jasper)

Posted 14 July 2012 - 06:26 AM

As long as the error isn't in the first 50 blocks, up to block 4F no you won't need to remap your ECC blocks which yours isn't.

As long as you have 2 matching nand dumps you you are good to create and program your ECC.

Once you get xell up and running use it in combination with you hacked nand update image (nandflash.bin) to update your nand as xell scans and auto remaps bad blocks.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users