FIXED Can I proceed with RGH? (Log included)

Status
Not open for further replies.
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
I have a Jasper 16MB - Dash: 12625 - CB: 6750

Powered it on to make sure it still worked after I soldered the wires. When it booted I wrote down the Dash and CB. Connected up and below is the log I have. On the last Read of the nand I decided to choose the 256MB for Jasper just to humor myself, and I was finally able to see a bad block but not sure if that really matters cause I have a 16MB Jasper. I'm still kinda noob so here are some pictures as well.

Pictures:



Log.txt
----------------------------------------------------


===================================================
Friday, January 25, 2013 9:35:27 PM

J-Runner v0.2 Beta (284) Started



Checking Files
Downloaded *common/xell/xell-2f.bin
Creating Directory C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\common\CoronaXell
Downloaded *common/CoronaXell/xell-2f.bin
Downloaded *common/CoronaXell/xell-gggggg.bin
Downloaded *common/DGX/CORONA_4GB_DGXv2.ecc
Downloaded *common/DGX/CORONA_16MB_DGXv2.ecc
Downloaded *common/xsvf/corona.0_2_en.xsvf
Downloaded *common/xsvf/corona.1_2_en.xsvf
Downloaded *common/xsvf/corona.1_3_en.xsvf
Downloaded *common/xsvf/corona.2_2_en.xsvf
Downloaded *common/xsvf/corona.2_3_en.xsvf
Downloaded *common/xsvf/corona.3_1_en.xsvf
Downloaded *common/xsvf/corona.3_2_en.xsvf
Downloaded *common/xsvf/corona.3_3_en.xsvf
Downloaded *common/xsvf/corona.4_2_en.xsvf
Downloaded *common/xsvf/corona.4_3_en.xsvf
Downloaded *common/xsvf/corona.5_2_en.xsvf
Downloaded *common/drivers/nand-x-upd-64.sys
Downloaded *common/drivers/nand-x-upd.sys
Downloaded *common/drivers/nand-x-upd.inf
Downloaded *common/drivers/nand-x-upd.cat
Downloaded *common/Pics/dgx_wires.jpg
Downloaded *xeBuild/launch.xex
Downloaded *xeBuild/lhelper.xex
Finished Checking Files
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.
Version: 00
Wrong Version.
System.NullReferenceException: Object reference not set to an instance of an object.
at JRunner.xml.end()
at JRunner.MainForm.savesettings()
at JRunner.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at JRunner.MainForm.WndProc(Message& m)
System.NullReferenceException: Object reference not set to an instance of an object.
at JRunner.xml.end()
at JRunner.MainForm.savesettings()
at JRunner.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at JRunner.MainForm.WndProc(Message& m)
System.NullReferenceException: Object reference not set to an instance of an object.
at JRunner.xml.end()
at JRunner.MainForm.savesettings()
at JRunner.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at JRunner.MainForm.WndProc(Message& m)
System.NullReferenceException: Object reference not set to an instance of an object.
at JRunner.xml.end()
at JRunner.MainForm.savesettings()
at JRunner.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at JRunner.MainForm.WndProc(Message& m)
System.NullReferenceException: Object reference not set to an instance of an object.
at JRunner.xml.end()
at JRunner.MainForm.savesettings()
at JRunner.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at JRunner.MainForm.WndProc(Message& m)
Version: 00
Wrong Version.
Version: 00
Wrong Version.
Checking Console..
Version: 00
Wrong Version.
Can not continue
Version: 20
Wrong Version.
Version: 01
Flash Config: 0x00000001
IoTimedOut

IoTimedOut:No more bytes!
Version: 00
Wrong Version.
Version: 00
Wrong Version.
Checking Console..
Version: 00
Wrong Version.
Can not continue
Version: 00
Wrong Version.
Version: 00
Wrong Version.
System.NullReferenceException: Object reference not set to an instance of an object.
at JRunner.xml.end()
at JRunner.MainForm.savesettings()
at JRunner.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at JRunner.MainForm.WndProc(Message& m)
Version: 00
Wrong Version.
Version: 00
Wrong Version.
Version: 00
Wrong Version.
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 3:27 min:sec

Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Nand Initialization Finished
Reading Nand
Done!
in 3:27 min:sec

Comparing...
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Nands are the same
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Cancelled
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 3:27 min:sec

Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Nand Initialization Finished
Reading Nand
Done!
in 3:28 min:sec

Comparing...
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Nands are the same
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 3:27 min:sec

Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Nand Initialization Finished
Reading Nand
Done!
in 3:27 min:sec

Comparing...
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Nands are the same
Checking Console..
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Reading Nand
Error: 250 reading block FF0
Done!
in 13:49 min:sec

Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Nand Initialization Finished
Reading Nand
Error: 250 reading block FF0
Done!
in 13:49 min:sec

Comparing...Takes a while on big nands
Bad Block ID @ 0x01FE [Offset: 0x41BE000]
Bad Block ID @ 0x01FE [Offset: 0x41BE000]
Nands are the same
------------------------------------------------------------------
 
L

LoneWolf913

From looking at the provided photos, you do NOT have a 16mb console. I see a Samsung NAND chip, which last I checked is only on big-block Jaspers. Did you miss all the "Bad Block 0xXX" errors you got on the first two dumps, or what? Re-dump two MATCHING 64mb dumps and post your new log.

FYI: "Flash Config: 0x00AA3020" means you have a big-block console.
 
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
Saturday, January 26, 2013 12:49:38 AM

J-Runner v0.2 Beta (284) Started


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


Checking Files
Finished Checking Files
Version: 01
Flash Config: 0x00AA3020
CB Version: 6750
Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Reading Nand
Error: 250 reading block FF0
Done!
in 13:23 min:sec

Reading Nand to C:\Users\Nick\Downloads\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Nand Initialization Finished
Reading Nand
Error: 250 reading block FF0
Done!
in 13:23 min:sec

Comparing...Takes a while on big nands
Bad Block ID @ 0x01FE [Offset: 0x41BE000]
Bad Block ID @ 0x01FE [Offset: 0x41BE000]
Nands are the same
 
L

LoneWolf913

Much better. You should be good to go, I don't see it having found that bad block remapped anywhere, but that far into the filesystem I don't think anything is actually stored there.. You have two matching dumps either way, so go ahead and create your ECC and write it to the console to retrieve your CPU key.
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
In instances where you see bad blocks not remapped (especially error 250), when you build your RGH image, go to xebuild advanced options and select 'noremap'.

Then go to Custom NAND/CR functions and select Erase/64 and choose run.

Then use the Advanced/Write Fusion option in J-Runner. If there are any blocks detected as bad, it'll remap for you.
 
  • Like
Reactions: keith6625 and akawtu
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
I appreciate the help guys. This is where I am at now.

Coolrunner wiring is attached too.

I must have a small block jasper because no onboard memory when looking under the memory tab on xbox 360.

Chose to use the 16MB dump I already had which showed no bad blocks in 360 Flash Tool.

Created .ecc image and wrote it to the nand

Connected the power, av, fan n shroud, made sure coolrunner switched to nor, ethernet cable, and powered on.

Coolrunner red light stayed on and green light flashing

Xell Reloaded showed and i was able to save my cpukey.txt, fuses.txt (with cpu key/dvd key), and keyvault

can i proceed with the 16MB nand dump or what? not sure as told I have a big block jasper
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
NO!!!!

You've just totally disregarded EVERYTHING in this thread.

you do NOT have a 16MB Jasper:

Flash Config: 0x00AA3020

J-Runner would have asked you whether you had a 256MB or 512MB console.

I really hope you still have that original 64MB Dump.

If you don't understand any of this, or still clueless after reading the guides then this sh*t is not for you.

We can help, but only if you actually listen.
 
oO Elite Oo

oO Elite Oo

VIP Member
Sep 3, 2011
1,837
0
In your Nand
bad soldering...you need to use google for your jasper nand size. from there on out you select what time of jasper you have or use the flash config code to identifty your mobo. each nand has different config code and use that to google it.
 
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
My config is in the log posted.

after I created an image with 360 multi builder, it created a 16MB dump out of my 64MB dump.

When I try to power on to xell again. Everything seems to go as normal, but xell never shows on screen

I have tried to use an hdmi cable as well as av cables and still no go

Both cables work on any other xbox

Not sure if I have to resolder the coolrunner again or not, but if so let me know.

Lights on it are still solid red when plugged and flashing green when powered on.

N E suggestions? Again I appreciate the help a lot.
 
T

talby71

VIP Member
Nov 24, 2010
3,463
0
Near Melbourne , Australia
didnt you already get your CPU key etc.. why you still trying to boot xell

why keep changing programs , stick with JRunner, using your 64mb dumps and build an image
 
Last edited:
  • Like
Reactions: nickmoses05
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
I tried to create an image but this is what i get

===================================================
Saturday, January 26, 2013 5:12:51 PM

J-Runner v0.2 Beta (285) Started


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


Filechecks disabled - No Filechecks carried out
Initializing officialnand1.bin..
Nand Initialization Finished
Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch 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!
****************************************************



**** could not read cb_6750.bin (-1) ****

******* ERROR: critical bootloader files are missing, cannot proceed!



***** FATAL BUILD ERROR: -1 unable to complete NAND image

---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Failed
 
T

talby71

VIP Member
Nov 24, 2010
3,463
0
Near Melbourne , Australia
said he's got his cpu key here 7

hope he hasnt mixed up his nand dumps, with all the stuffing around
 
  • Like
Reactions: nickmoses05
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
I have my cpu key and I know which nands are which. I named them specifically. I did have the CPUKEY when I tried that. I am not going to write a nand unless I am 100% sure. Im just trying to get a image created with j runner app. I got an image with 360 builder (updflash.bin), but I dont want to write that one because I want to do the whole procedure in j runner app. So I am still trying to figure out why I am getting this error?
 
oO Elite Oo

oO Elite Oo

VIP Member
Sep 3, 2011
1,837
0
In your Nand
okay restart jr app, put your stock nand as source and put your CPU key in (JR will probly already put the cpu key in automatically if in data base) then select 16202 dashboard and hit create image. if you select show working folder you will see a file called "updflash.bin" thats your new nand image ready to be written. You can use Xell, nand x or jr programmer to write that .bin file. you should now get a booting console. If not then check your wiring and have correct jumper settings..

PM me your nand dump (the one that booted Xell...im confused with your nand dump story here) and provide me your CPU key. Ill make a image for you.
 
Last edited:
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
So you decided to not take advice and just carry on regardless.

Well done. I'd now find someone who actually reads guides to fix this for you.

You have no idea how frustrating it is trying to support people when they won't even read before jumping in.

---------- Post added at 01:42 ---------- Previous post was at 01:39 ----------
nickmoses05 said:
Of course I got everything saved and i just redid the whole process again with the 64MB dumps.

I will report back when finished
Click to expand...
This is where you f*cked up.

Nowhere did I suggest to re-dump anything.

You already had a 64MB NAND dump but because you don't understand what you're doing, you thought it would be a good idea to re-dump it AGAIN (after writing SB NAND format to it).

Multibuilder threw a fit because you f*cked up.

Get your FIRST GOOD 64MB NAND DUMP.

This is what you need to work with.

Open it with J-Runner and insert the CPU key.

DO NOT USE ANY DUMPS YOU MADE AFTER WRITING THE ECC TO YOUR CONSOLE.

I hope that's clear enough.
 
  • Like
Reactions: talby71
nickmoses05

nickmoses05

Full Member
Apr 8, 2009
66
8
Tinley Park, IL
Martin I dont think u understand what I posted. I never wrote anything and I still have all my dumps. You dont have to be an ass about it. Its discouraging when thats done to people like me. I was able to make it as far as I did without breaking anything so thats good enough to ask for a little direction. I have already PM'd elite for a good dump that he has provided me. Now I am going to write this nand. I should be good to go. I will post if any problems. Even though I'm kinda hesistant now.

FYI: I never redumped my nand or redid the .ecc That is all the same . I only have 2 sets of dumps. a small block 16MB and a BB 64MB. Im not using the small block because my config specified that im using a big block. Now I know I have a 512MB. And I dont wanna sound like an ass either but its hard not too when i get responses like that
 
Last edited:
I

inode1

Full Member
Feb 4, 2012
47
0
Washington
nickmoses05 said:
Martin I dont think u understand what I posted. I never wrote anything and I still have all my dumps. You dont have to be an ass about it. Its discouraging when thats done to people like me. I was able to make it as far as I did without breaking anything so thats good enough to ask for a little direction. I have already PM'd elite for a good dump that he has provided me. Now I am going to write this nand. I should be good to go. I will post if any problems. Even though I'm kinda hesistant now.
Click to expand...
While it is discouraging to receive feedback like this, you have to look at it from Martin's perspective... Day in and day out this is what he deals with, and while you appear to have things sorted out now, 99% of people who post with problems do not read the guides. By the way you posted your steps it appeared you re-dumped your NAND after writing the ecc to it, next time clarify the order of what you have done and this could be avoided.. Now if everything is working then good job and have fun.
 
Status
Not open for further replies.