Jump to content
RealModScene
Sign in to follow this  
txhgaming

Jtag wont boot Xell

Recommended Posts

First of all thanks for looking, not sure why it wont boot. Soldering is sound. Error reading and writing block "D", figuring it might have something to do with this considering xell is first 50 block. Anyway here is my Jrunner Log. THank you,

Tuesday, December 12, 2017 7:03:58 PM

J-Runner v0.4 Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 1903
Xenon
Reading Nand to C:\Users\User\Desktop\JR Runner\output\nanddump1.bin
Reading Nand
Error: 250 reading block D
Error: 250 reading block 21F
Error: 250 reading block 26B
Done!
in 3:27 min:sec

Initializing nanddump1.bin..
Reading Nand to C:\Users\User\Desktop\JR Runner\output\nanddump2.bin
Xenon
Jtag Selected
Nand Initialization Finished
Reading Nand
Error: 250 reading block D
Error: 250 reading block 21F
Error: 250 reading block 26B
Done!
in 3:30 min:sec

Comparing...
Bad Block ID  000D Found @ 0x03FF [Offset: 0x107BE00]
Bad Block ID  021F Found @ 0x03FE [Offset: 0x1077C00]
Bad Block ID  026B Found @ 0x03FD [Offset: 0x1073A00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000D [Offset: 0x35A00]
Block ID 03FE [Offset: 0x1077C00] remapped to Block ID 021F [Offset: 0x8BFE00]
Block ID 03FD [Offset: 0x1073A00] remapped to Block ID 026B [Offset: 0x9F9600]
Bad Blocks Remapped
Bad Block ID  000D Found @ 0x03FF [Offset: 0x107BE00]
Bad Block ID  021F Found @ 0x03FE [Offset: 0x1077C00]
Bad Block ID  026B Found @ 0x03FD [Offset: 0x1073A00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000D [Offset: 0x35A00]
Block ID 03FE [Offset: 0x1077C00] remapped to Block ID 021F [Offset: 0x8BFE00]
Block ID 03FD [Offset: 0x1073A00] remapped to Block ID 026B [Offset: 0x9F9600]
Bad Blocks Remapped
Nands are the same
XeLL file created Successfully xenon.bin
Version: 10
Flash Config: 0x01198010
Writing Nand
xenon.bin
Error: 202 writing block D
Done!
in 0:18 min:sec

Share this post


Link to post
Share on other sites

Try writing the file with the advanced menus demon/fusion write option. Most ecc images are not created with the nand anymore, or since the 15574 update, so all that is done is the KV is injected into the bin file when you create the ecc. It doesnt remap the bad blocks. The demon/fusion write option forces remapping while flashing the image. Also, make sure your console has a jtaggable CB version. 

Share this post


Link to post
Share on other sites

yes sir thank you, never even crossed my mind to do thaht.

3 hours ago, gavin_darkglider said:

Try writing the file with the advanced menus demon/fusion write option. Most ecc images are not created with the nand anymore, or since the 15574 update, so all that is done is the KV is injected into the bin file when you create the ecc. It doesnt remap the bad blocks. The demon/fusion write option forces remapping while flashing the image. Also, make sure your console has a jtaggable CB version. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...