endure_blackout 0 Posted August 28, 2018 Glitch/Nand Reader Product(s) used: CR3 I believe.Console Type: CoronaNAND size: 4GBDashboard version: 2.0.17489CB version: 13121Screenshot of NAND details from J-Runner/Xebuild GUI: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/AImages of close-up soldering to motherboard:N/ADescription 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)/NDo you get a green debug light appear on the RGH chip every 4-5 seconds: N/AHow long is the light on for each time: N/A Quote Share this post Link to post Share on other sites
gavin_darkglider 1562 Posted August 28, 2018 How are you flashing the image? Quote Share this post Link to post Share on other sites
felida 1653 Posted August 28, 2018 37 minutes ago, endure_blackout said: Glitch/Nand Reader Product(s) used: CR3 I believe.Console Type: CoronaNAND size: 4GBDashboard version: 2.0.17489CB version: 13121Screenshot of NAND details from J-Runner/Xebuild GUI: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/AImages of close-up soldering to motherboard:N/ADescription 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 Quote Share this post Link to post Share on other sites
endure_blackout 0 Posted August 28, 2018 I am flashing using simple 360 nand flasher Quote Share this post Link to post Share on other sites
Neocazen 27 Posted August 28, 2018 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 Quote Share this post Link to post Share on other sites
felida 1653 Posted August 29, 2018 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 Quote Share this post Link to post Share on other sites
endure_blackout 0 Posted August 30, 2018 Simple 360 NAND Flasher.log no problems from what I can see Quote Share this post Link to post Share on other sites
gavin_darkglider 1562 Posted August 31, 2018 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. Quote Share this post Link to post Share on other sites