FIXED JRunner Crashes When i Write NAND

ScrubbaDubby

BANNED
Aug 10, 2012
272
0
Findlay, Ohio
I am done with everything! :D

I'm down to writing the NAND and JRunner crashes. Everytime!

I got cpu key, created image, done everything, installed CR obviously, but when trying to write the NAND JR just crashes

WHEN CRASHING IT MAKES THE DISCONNECT SOUND ON MY COMPUTER, like cable came unplugged
 
Last edited:

Krafter

VIP Member
Apr 17, 2011
3,737
118
Indiana
I take it you got another NAND-X? I don't understand how you could write the ecc but not the glitch image. Pics are needed of course to rule out install issues.

In the meantime, try reinstalling the drivers.
 

Krafter

VIP Member
Apr 17, 2011
3,737
118
Indiana
you don't need a nand-x on a demon.... :facepalm: but i am getting a new one asap im returning the old to xconsoles.

i dont think log is saving when it crashes, but here is when it crashes:
http://gyazo.com/ae594b4523bf19e44a854ce6ec85c3cb
Oops you didn't mention the demon in the your post and I didn't notice what section you posted in.

Did you try reinstalling the demon drivers then?

and DEMON is in XB mode and not PC mode right? It's usually the simple stuff that gets me.
 
Last edited:

ScrubbaDubby

BANNED
Aug 10, 2012
272
0
Findlay, Ohio
===================================================
Tuesday, September 04, 2012 11:04:28 PM

J-Runner v0.2 Beta (280) 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
Initializing Nand..
Nand Initialization Finished
Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.04.515
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
C:\Users\Zach\Desktop\J-Runner v02 (278) Core Pack\132113304308\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 132113304308
ConsoleId : 027807982205
MoboSerial: 9256579106090438
Mfg Date : 10/23/2010
CPU Key : DBD533EF83ACCE452D5958514858CA41
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 4AC0F2491AEDF15CAF586B666CB50CD3
CF LDV : 8
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\Zach\Desktop\J-Runner v02 (278) Core Pack\132113304308
Image is Ready








then hen i hit write nand it starts and then it crashes before it even writes

---------- Post added at 20:07 ---------- Previous post was at 20:06 ----------

and Blake i have tried writing several dash's, none are working atm
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Clear your "working directory" (back existing NAND dumps up first) and see if the issue remains.

Check the ribbon cable too as I mentioned in my previous post.

Does the same thing happen with the DemoN Toolbox?
 
Last edited:

Goldensavage

VIP Member
Jul 26, 2009
3,332
0
Essex, UK
you don't need a nand-x on a demon.... :facepalm: but i am getting a new one asap im returning the old to xconsoles.

i dont think log is saving when it crashes, but here is when it crashes:
http://gyazo.com/ae594b4523bf19e44a854ce6ec85c3cb
I hope you didn't con them into replacing the old one that you broke.

Also as Blakey said. Use Demon toolbox and see where that leads you.

Pics of your soldering would be nice
 

ScrubbaDubby

BANNED
Aug 10, 2012
272
0
Findlay, Ohio
i didn't con them into anything. it died 3 weeks aafter i got it so i opened a return ticket, it got accepted and im sending it tomoro for a replacement

---------- Post added at 03:41 ---------- Previous post was at 03:32 ----------

***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Loading image.
Remapping invalid blocks.
Erasing.
Marking invalid blocks.
Programming.
Programming completed successfully in 29 seconds!













i have wrote my original NAND in program flash and i get this on demon toolbox.

the RED dot doesn't come up for a half second after a flash, but when i turn on the xbox everytime after that its instant red dot
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
***** NAND-Flash Information *****

Manufacturer: Hynix
Device: HY27US08281A
Device Id: 0xAD73
Number of Blocks: 1024
Number of Pages per Block: 32
Page Size: 528 bytes
Number of Invalid Blocks: 0

Loading image.
Remapping invalid blocks.
Erasing.
Marking invalid blocks.
Programming.
Programming completed successfully in 29 seconds!


i have wrote my original NAND in program flash and i get this on demon toolbox.

the RED dot doesn't come up for a half second after a flash, but when i turn on the xbox everytime after that its instant red dot
It looks like programming went well.

Have you written the relevant EN timing file to your CoolRunner?

I suggest you post an image of CPU_RST - you will see a red dot if FT4R2 is damaged.
 
Last edited:

ScrubbaDubby

BANNED
Aug 10, 2012
272
0
Findlay, Ohio
CLK_STBY trace was partially off. when moving it, RED dot went away, so i just scraped the trace and soldered to the resistor. red dot is gone and i can write again.

Thanks everyone
 

Goldensavage

VIP Member
Jul 26, 2009
3,332
0
Essex, UK
i didn't con them into anything. it died 3 weeks aafter i got it so i opened a return ticket, it got accepted and im sending it tomoro for a replacement



I will quote Martin C from one of your many previous request for help threads.

http://team-xecuter.com/forums/showpost.php?p=653973&postcount=15

The problem here is the OP soldered the NAND-x to J2D2 by mistake in a previous attempt.

EPIC FAIL.

You've killed the NAND-x - instead of accepting this fact, this is the 2nd thread opened for the same problem.

Buy a new NAND-x and solder it properly.
 
  • Like
Reactions: Krafter