Hello,
I recently recieved an xbox from a kid who's Network ICS was damaged during a bad storm. I sent it to Ultimate360 to get the ICS replaced and he succeeded in doing so (thanks Ultimate360). Except after he fixed the chip it wouldn't obtain an Ip Address, I put the thread he created below:
http://team-xecuter.com/forums/show...in-IP-address-after-ICS-replacement-on-Jasper
I dumped the Nand and it appears it has some bad blocks. I think it might have to do with the thunderstorm because the only thing that appears to be affected is the Ethernet port. I installed a CR4 with the RGH2 method and it boots to the dash no problem. Only thing is it still won't obtain an IP (either dynamically or statically). I used XNandHealer to re-map the bad blocks and wrote the updflash.bin via xell. That seemed to help a little bit (before, in the dash, the ethernet would cut in and out erratically), now it stays checked in the dash it just won't pull an IP Address. Xell did spit me out some errors when writing the repaired updflash.bin though.
Here's the xell errors I recieved:
And here's my Jrunner log:
I de-soldered my jr-programmer cable, so if you want pictures of that I'd have to update this post a little later. I was just wondering if anyone had any ideas on how I can get this nand in working order and successfully flashed onto the motherboard again?
I recently recieved an xbox from a kid who's Network ICS was damaged during a bad storm. I sent it to Ultimate360 to get the ICS replaced and he succeeded in doing so (thanks Ultimate360). Except after he fixed the chip it wouldn't obtain an Ip Address, I put the thread he created below:
http://team-xecuter.com/forums/show...in-IP-address-after-ICS-replacement-on-Jasper
I dumped the Nand and it appears it has some bad blocks. I think it might have to do with the thunderstorm because the only thing that appears to be affected is the Ethernet port. I installed a CR4 with the RGH2 method and it boots to the dash no problem. Only thing is it still won't obtain an IP (either dynamically or statically). I used XNandHealer to re-map the bad blocks and wrote the updflash.bin via xell. That seemed to help a little bit (before, in the dash, the ethernet would cut in and out erratically), now it stays checked in the dash it just won't pull an IP Address. Xell did spit me out some errors when writing the repaired updflash.bin though.
Here's the xell errors I recieved:
And here's my Jrunner log:
Code:
J-Runner v0.3 Beta (7) Started
Happy Holidays Everyone!
Checking Files
Finished Checking Files
Glitch2 Selected
CR4 Selected
Version: 10
Flash Config: 0x008A3020
008A3020
Jasper 256MB
CB Version: 6754
Jasper 256MB Manually Selected
Reading Nand to C:\Documents and Settings\John\Desktop\BAD JASPER\output\nanddump1.bin
Reading Nand
Error: 250 reading block 7B0
Error: 210 reading block 7B1
Error: 210 reading block 7B2
Error: 210 reading block 7B3
Error: 210 reading block 7B4
Error: 210 reading block 7B5
Error: 210 reading block 7B6
Error: 210 reading block 7B7
Error: 300 reading block 862
Error: 300 reading block 863
Error: 300 reading block 864
Error: 301 reading block 865
Error: 300 reading block 866
Error: 300 reading block 867
Error: 300 reading block 868
Error: 300 reading block 869
Error: 300 reading block 86A
Error: 300 reading block 86B
Error: 300 reading block 86C
Error: 300 reading block 86D
Error: 300 reading block 86E
Error: 300 reading block 86F
Error: 300 reading block 870
Error: 300 reading block 871
===================================================
Tuesday, December 23, 2014 4:28:26 PM
J-Runner v0.3 Beta (7) Started
WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Happy Holidays Everyone!
Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Jasper BB
Jtag Selected
Nand Initialization Finished
Comparing...Takes a while on big nands
Bad Block ID 01C9 Found @ 0x01FE [Offset: 0x41BE000]
Block ID 01FE [Offset: 0x41BE000] remapped to Block ID 01C9 [Offset: 0x3AE9000]
Bad Blocks Remapped
Bad Block ID 01C9 Found @ 0x01FE [Offset: 0x41BE000]
Block ID 01FE [Offset: 0x41BE000] remapped to Block ID 01C9 [Offset: 0x3AE9000]
Bad Blocks Remapped
Nands are the same
Jasper 256MB Manually Selected
Initializing nanddump1.bin..
Jasper BB
Nand Initialization Finished
Comparing...Takes a while on big nands
Bad Block ID 01C9 Found @ 0x01FE [Offset: 0x41BE000]
Block ID 01FE [Offset: 0x41BE000] remapped to Block ID 01C9 [Offset: 0x3AE9000]
Bad Blocks Remapped
Bad Block ID 01C9 Found @ 0x01FE [Offset: 0x41BE000]
Block ID 01FE [Offset: 0x41BE000] remapped to Block ID 01C9 [Offset: 0x3AE9000]
Bad Blocks Remapped
Nands are the same
Glitch2 Selected
CR4 Selected
Jasper 256MB Manually Selected
ECC created
Jasper 256MB Manually Selected
Version: 10
Flash Config: 0x008A3020
Writing Nand
image_00000000.ecc
Done!
in 0:19 min:sec
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Jasper BB
Jtag Selected
Nand Initialization Finished
Glitch2 Selected
Load Files Initiliazation Finished
16767
Started Creation of the 16767 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.14.693
---------------------------------------------------------------
base path changed to C:\Documents and Settings\John\Desktop\Jrunner\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image
**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
---------------------------------------------------------------
C:\Documents and Settings\John\Desktop\BAD JASPER\056971784607\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16767.0
Console : Jasper (big block)
NAND size : 64MiB (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 056971784607
ConsoleId : 030054136169
MoboSerial: 8921741211858467
Mfg Date : 11/12/2008
CPU Key : 1056EF52D9D95D2167622E1C96438B3F
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : F0DC703A33079D49BD6DB92A9DBA9548
CF LDV : 21
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Documents and Settings\John\Desktop\BAD JASPER\056971784607
Image is Ready
Initializing updflash.bin..
Jasper BB
Nand Initialization Finished
Jasper 256MB Manually Selected
Version: 10
Flash Config: 0x008A3020
Writing Nand
updflash.bin
Error: 601 writing block 5D
Error: A02 writing block 5E
Error: E03 writing block 44A
Error: E02 writing block 44B
Error: 202 writing block 7B0
Error: 601 writing block A17
Error: E02 writing block DAF
Error: A00 writing block DB0
Error: 202 writing block E48
Done!
in 14:30 min:sec
