Solved NAND won't flash

[eph]

I'm on 17349 trying to update. I've tried using JRunner and XeBuild GUI to create the updated nand dump and Simple 360 NAND Flasher to flash the updated nand dump.
I'm on a Corona4GB RGH2 w/ a Squirt360 chip inside to glitch.
XeBuild log:

===================================================
Friday, September 18, 2015 3:56:08 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


Filechecks disabled - No Filechecks carried out
Initializing flashdmp.bin..
Corona 4GB
Glitch2 Selected
Nand Initialization Finished
nofcrt Enabled
nofcrt Disabled
Use Edited Options Selected
Use Edited Options de-Selected
Load Files Initiliazation Finished
17489
Started Creation of the 17489 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.15.709
---------------------------------------------------------------
base path changed to C:\Users\FOXES\Downloads\J-Runner v32\J-Runner v3\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\FOXES\Downloads\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\238080724143\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17489.0
Console   : Corona
NAND size : 48MiB MMC (system only)
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : <removed>
ConsoleId : <removed>
MoboSerial: <removed>
Mfg Date  : 10/12/2012
CPU Key   :
<REMOVED>
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   :
<removed>
CF LDV    : 7
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\FOXES\Downloads\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\238080724143
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Use Edited Options Selected
nointmu Enabled
nointmu Enabled
nointmu Disabled

 

[HuskerHeaven]

Have you tried hardware flashing as I suggested? I'm pretty sure your 4GB chip is on it's last legs.

 

[eph]

Have you tried hardware flashing as I suggested? I'm pretty sure your 4GB chip is on it's last legs.

I would but I have literally no way to open the case. If my chip is actually on its last legs I'm gonna be pretty pissed since I got the console basically new only about 2-3 months ago and I've kept the fan speeds pretty high, my temps for case, mobo, etc. are usually below 55 degrees Celsius.
I was hoping maybe I could get some new suggestions or something because I'm pretty sure I won't be able to open the case anytime soon.

 

[HuskerHeaven]

I would but I have literally no way to open the case. If my chip is actually on its last legs I'm gonna be pretty pissed since I got the console basically new only about 2-3 months ago and I've kept the fan speeds pretty high, my temps for case, mobo, etc. are usually below 55 degrees Celsius.
I was hoping maybe I could get some new suggestions or something because I'm pretty sure I won't be able to open the case anytime soon.

4GB nand chips don't care about temp. They have no cooling nor care what you do to them. They just die when they want to die. I've seen retail 4GB's die just as often as reading the nand. No way to predict or prevent it. It just happens.

 

[eph]

4GB nand chips don't care about temp. They have no cooling nor care what you do to them. They just die when they want to die. I've seen retail 4GB's die just as often as reading the nand. No way to predict or prevent it. It just happens.

Welp, unless I have some way to hardware flash or it somehow magically works I'm ****ed.