Jump to content
RealModScene
Sign in to follow this  
endure_blackout

Corona 4gb help updating

Recommended Posts

Glitch/Nand Reader Product(s) used: CR3 I believe.
Console Type: Corona
NAND size: 4GB
Dashboard version: 2.0.17489
CB version: 13121
Screenshot of NAND details from J-Runner/Xebuild GUI:
nandInfo.PNG.727b43334ca25bd98cf1c2f90ecf3bf4.PNG
J-Runner/Xebuild Gui log:

Tuesday, August 28, 2018 1:41:38 AM

J-Runner v0.3 Beta (8) Started


Connection Error
Filechecks disabled - No Filechecks carried out
Getting info from ip 10.0.0.27...
LockDownValue is 2
Initializing flashdmp.bin..
Corona 4GB
Glitch2 Selected
Nand Initialization Finished
Initializing flashdmp.bin..
Corona 4GB
Nand Initialization Finished
Load Files Initiliazation Finished
17526
Started Creation of the 17526 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.15.709
---------------------------------------------------------------
base path changed to D:\Jtag stuff\J-Runner v3 17526\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Jake\Desktop\J-Runner v3 (5) Core Pack\027110324743\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17526.0
Console   : Corona
NAND size : 48MiB MMC (system only)
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 027110324743
ConsoleId : 030749489868
MoboSerial: 7501061232012465
Mfg Date  : 11/20/2012
CPU Key   : E5F2FECD8D58B84E84809B346EE86357
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : D6E9D75F8627572648D933E8CAF8C1AB
CF LDV    : 2
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Jake\Desktop\J-Runner v3 (5) Core Pack\027110324743
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Corona 4GB Manually Selected

 


updflash.bin log (if applicable):

updflash(280820181218).bin.log


Image of Glitch Chip: N/A
Images of close-up soldering to motherboard:
N/A

Description of problem:

I have been on dash 17489 for a while trying to update however, when I attempt to update to 17526 it says that it flashes successfully but it still remains on 17489.


Was the console working before you started: (Y)/N

Do you get a green debug light appear on the RGH chip every 4-5 seconds: N/A

How long is the light on for each time: N/A

Share this post


Link to post
Share on other sites
37 minutes ago, endure_blackout said:

Glitch/Nand Reader Product(s) used: CR3 I believe.
Console Type: Corona
NAND size: 4GB
Dashboard version: 2.0.17489
CB version: 13121
Screenshot of NAND details from J-Runner/Xebuild GUI:
nandInfo.PNG.727b43334ca25bd98cf1c2f90ecf3bf4.PNG
J-Runner/Xebuild Gui log:

Tuesday, August 28, 2018 1:41:38 AM

J-Runner v0.3 Beta (8) Started


Connection Error
Filechecks disabled - No Filechecks carried out
Getting info from ip 10.0.0.27...
LockDownValue is 2
Initializing flashdmp.bin..
Corona 4GB
Glitch2 Selected
Nand Initialization Finished
Initializing flashdmp.bin..
Corona 4GB
Nand Initialization Finished
Load Files Initiliazation Finished
17526
Started Creation of the 17526 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.15.709
---------------------------------------------------------------
base path changed to D:\Jtag stuff\J-Runner v3 17526\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Jake\Desktop\J-Runner v3 (5) Core Pack\027110324743\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17526.0
Console   : Corona
NAND size : 48MiB MMC (system only)
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 027110324743
ConsoleId : 030749489868
MoboSerial: 7501061232012465
Mfg Date  : 11/20/2012
CPU Key   : E5F2FECD8D58B84E84809B346EE86357
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : D6E9D75F8627572648D933E8CAF8C1AB
CF LDV    : 2
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Jake\Desktop\J-Runner v3 (5) Core Pack\027110324743
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Corona 4GB Manually Selected

 


updflash.bin log (if applicable):

updflash(280820181218).bin.log


Image of Glitch Chip: N/A
Images of close-up soldering to motherboard:
N/A

Description of problem:

I have been on dash 17489 for a while trying to update however, when I attempt to update to 17526 it says that it flashes successfully but it still remains on 17489.

How are u flashing? Like Gavin said.. lol.. a jrunner snippet only shows us that u can build an image.. nothing to do with anything else

Share this post


Link to post
Share on other sites

Nand's in trouble. Read but not write. There's no way.
    This happens a lot with 48MB Nand. Here in Brazil they exchange for Nand of 16MB.
    Leave it as it is, there are no
 one Kernel to another.

I've had two video games of my friends with this problem. The Nand reading is perfect without any errors the new kernel is added in updflash. it usually writes the video game reboots and stays with the old kernel. it could be some blockage or something.

in Brazil the Nand chip is exchanged and the modified plate is clear

Share this post


Link to post
Share on other sites
6 hours ago, endure_blackout said:

I am flashing using simple 360 nand flasher

Is there an error code? You might need to bridge the resistors, but that might just be for using a nand reader, also, are you using version 1.4? Did you press A then start like it tells you to?? I don't know if simple nand flasher produces a log.. I can check n see myself.. but if it does, post that log

3 hours ago, Neocazen said:

Nand's in trouble. Read but not write. There's no way.
    This happens a lot with 48MB Nand. Here in Brazil they exchange for Nand of 16MB.
    Leave it as it is, there are no
 one Kernel to another.

The op has no logs of the actual flashing.. jrunner logs mean nothing when it is not used to write to the nand.. 

 

 

edit:

simple nand flasher DOES produce a log, so i am going to need that

Share this post


Link to post
Share on other sites

I dont see any problems either. I know I have had issues if I didnt unplug the console after writing the nand, but this is usually when writing 16mb nands with a hardware flasher, mainly because the SMC doesnt reload, after nand write. Chances are though, that you are experiencing the Read only issue with the 4GB MMC nands in corona big block consoles, and the only way to fix that is to remove the nand that is there, install a new 16 mb nand, and move a bunch of resistors,  Then once that is done, you need to create a new 16mb image using the files you have. Lucky for you this doesnt hurt retail, as Microsoft doesnt look for nand swaps usually, so you could also convert your retail image if you wanted as well. All that being said, it is not an easy repair, so I would find someone to do it for you, if you arent comfortable with that.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×