darknezz19 5 Posted June 17, 2017 I have a Corona 4Gb that I'm trying to update to 17511 with the dumped nand from simple nand flasher. I enable advance mode, disable failsafe, check enable command line edit, select corona mobo and rgh2, then on the command change -c corona to -c corona4g. Doesn't boot, led turns red after about 30 secs on 360. Also tried to add -o patchsmc output.bin but that didn't help either. If I flash the backup nand back it boots still. Kinda at a loss on this one. Any help is appreciated, thank you. Quote Share this post Link to post Share on other sites
salah.rgh2 162 Posted June 17, 2017 Here you'll find a correct way to update CORONA 4G http://forum.homebrew-connection.org/index.php?topic=144.0 Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 Hi salah. I fallowed Swizzy's guide to the t. even tried to write the nand back with simple flasher instead of sd qsb, same result. Quote Share this post Link to post Share on other sites
Dr.Gonzo 392 Posted June 17, 2017 Any Error or Bad Block Messages in flashing & XeBuild GUI log ? Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 Simple 360 NAND Flasher by Swizzy v1.2 Detecting NAND Type... * Detected MMC NAND device! * Entering MMC/Corona v2 [4GB] Mode... Press A if you want to flash your nand with Rawflash4G v1 Press B if you want to safeflash your nand with Rawflash4G v1 (Dump + Write) Press X if you want to dump your nand with Rawdump4G v1 If you press anything else the application will close... Press Start to flash your nand or press anything else to exit! WARNING! DO NOT TOUCH YOUR CONSOLE OR CONTROLLER DURING THE FLASH PROCESS!! The console will power off when it's done! Checking game:\updflash.bin for spare data... No spare data detected! * rawflash4g v1 started (by Swizzy) Getting NAND Size... * Size: 3000000 (48.00 MB) * Reading in Image to Memory... * Writing image to Flash... Processed 0x80000 bytes of 0x3000000 (1.04 ) Processed 0x100000 bytes of 0x3000000 (2.08 ) Processed 0x180000 bytes of 0x3000000 (3.13 ) Processed 0x200000 bytes of 0x3000000 (4.17 ) Processed 0x280000 bytes of 0x3000000 (5.21 ) Processed 0x300000 bytes of 0x3000000 (6.25 ) Processed 0x380000 bytes of 0x3000000 (7.29 ) Processed 0x400000 bytes of 0x3000000 (8.33 ) Processed 0x480000 bytes of 0x3000000 (9.38 ) Processed 0x500000 bytes of 0x3000000 (10.42 ) Processed 0x580000 bytes of 0x3000000 (11.46 ) Processed 0x600000 bytes of 0x3000000 (12.50 ) Processed 0x680000 bytes of 0x3000000 (13.54 ) Processed 0x700000 bytes of 0x3000000 (14.58 ) Processed 0x780000 bytes of 0x3000000 (15.63 ) Processed 0x800000 bytes of 0x3000000 (16.67 ) Processed 0x880000 bytes of 0x3000000 (17.71 ) Processed 0x900000 bytes of 0x3000000 (18.75 ) Processed 0x980000 bytes of 0x3000000 (19.79 ) Processed 0xA00000 bytes of 0x3000000 (20.83 ) Processed 0xA80000 bytes of 0x3000000 (21.88 ) Processed 0xB00000 bytes of 0x3000000 (22.92 ) Processed 0xB80000 bytes of 0x3000000 (23.96 ) Processed 0xC00000 bytes of 0x3000000 (25.00 ) Processed 0xC80000 bytes of 0x3000000 (26.04 ) Processed 0xD00000 bytes of 0x3000000 (27.08 ) Processed 0xD80000 bytes of 0x3000000 (28.13 ) Processed 0xE00000 bytes of 0x3000000 (29.17 ) Processed 0xE80000 bytes of 0x3000000 (30.21 ) Processed 0xF00000 bytes of 0x3000000 (31.25 ) Processed 0xF80000 bytes of 0x3000000 (32.29 ) Processed 0x1000000 bytes of 0x3000000 (33.33 ) Processed 0x1080000 bytes of 0x3000000 (34.38 ) Processed 0x1100000 bytes of 0x3000000 (35.42 ) Processed 0x1180000 bytes of 0x3000000 (36.46 ) Processed 0x1200000 bytes of 0x3000000 (37.50 ) Processed 0x1280000 bytes of 0x3000000 (38.54 ) Processed 0x1300000 bytes of 0x3000000 (39.58 ) Processed 0x1380000 bytes of 0x3000000 (40.63 ) Processed 0x1400000 bytes of 0x3000000 (41.67 ) Processed 0x1480000 bytes of 0x3000000 (42.71 ) Processed 0x1500000 bytes of 0x3000000 (43.75 ) Processed 0x1580000 bytes of 0x3000000 (44.79 ) Processed 0x1600000 bytes of 0x3000000 (45.83 ) Processed 0x1680000 bytes of 0x3000000 (46.88 ) Processed 0x1700000 bytes of 0x3000000 (47.92 ) Processed 0x1780000 bytes of 0x3000000 (48.96 ) Processed 0x1800000 bytes of 0x3000000 (50.00 ) Processed 0x1880000 bytes of 0x3000000 (51.04 ) Processed 0x1900000 bytes of 0x3000000 (52.08 ) Processed 0x1980000 bytes of 0x3000000 (53.13 ) Processed 0x1A00000 bytes of 0x3000000 (54.17 ) Processed 0x1A80000 bytes of 0x3000000 (55.21 ) Processed 0x1B00000 bytes of 0x3000000 (56.25 ) Processed 0x1B80000 bytes of 0x3000000 (57.29 ) Processed 0x1C00000 bytes of 0x3000000 (58.33 ) Processed 0x1C80000 bytes of 0x3000000 (59.38 ) Processed 0x1D00000 bytes of 0x3000000 (60.42 ) Processed 0x1D80000 bytes of 0x3000000 (61.46 ) Processed 0x1E00000 bytes of 0x3000000 (62.50 ) Processed 0x1E80000 bytes of 0x3000000 (63.54 ) Processed 0x1F00000 bytes of 0x3000000 (64.58 ) Processed 0x1F80000 bytes of 0x3000000 (65.63 ) Processed 0x2000000 bytes of 0x3000000 (66.67 ) Processed 0x2080000 bytes of 0x3000000 (67.71 ) Processed 0x2100000 bytes of 0x3000000 (68.75 ) Processed 0x2180000 bytes of 0x3000000 (69.79 ) Processed 0x2200000 bytes of 0x3000000 (70.83 ) Processed 0x2280000 bytes of 0x3000000 (71.88 ) Processed 0x2300000 bytes of 0x3000000 (72.92 ) Processed 0x2380000 bytes of 0x3000000 (73.96 ) Processed 0x2400000 bytes of 0x3000000 (75.00 ) Processed 0x2480000 bytes of 0x3000000 (76.04 ) Processed 0x2500000 bytes of 0x3000000 (77.08 ) Processed 0x2580000 bytes of 0x3000000 (78.13 ) Processed 0x2600000 bytes of 0x3000000 (79.17 ) Processed 0x2680000 bytes of 0x3000000 (80.21 ) Processed 0x2700000 bytes of 0x3000000 (81.25 ) Processed 0x2780000 bytes of 0x3000000 (82.29 ) Processed 0x2800000 bytes of 0x3000000 (83.33 ) Processed 0x2880000 bytes of 0x3000000 (84.38 ) Processed 0x2900000 bytes of 0x3000000 (85.42 ) Processed 0x2980000 bytes of 0x3000000 (86.46 ) Processed 0x2A00000 bytes of 0x3000000 (87.50 ) Processed 0x2A80000 bytes of 0x3000000 (88.54 ) Processed 0x2B00000 bytes of 0x3000000 (89.58 ) Processed 0x2B80000 bytes of 0x3000000 (90.63 ) Processed 0x2C00000 bytes of 0x3000000 (91.67 ) Processed 0x2C80000 bytes of 0x3000000 (92.71 ) Processed 0x2D00000 bytes of 0x3000000 (93.75 ) Processed 0x2D80000 bytes of 0x3000000 (94.79 ) Processed 0x2E00000 bytes of 0x3000000 (95.83 ) Processed 0x2E80000 bytes of 0x3000000 (96.88 ) Processed 0x2F00000 bytes of 0x3000000 (97.92 ) Processed 0x2F80000 bytes of 0x3000000 (98.96 ) Successfully wrote 0x3000000 bytes from game:\updflash.bin to Flash! Completed after 16.00 seconds Shutting down in 5....4....3....2....1....BYE! Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 Not that I can see. The kernel and dash it is on now is 17349 is that makes any difference. Sorry for double post it wouldn't let me edit the one above. Quote Share this post Link to post Share on other sites
Dr.Gonzo 392 Posted June 17, 2017 Bad Blocks on MMC lol....sorry. Your XeBuild Log could be helpful too Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 How can you tell Gonzo? Is this type of scenario still able to update the dash? Quote Share this post Link to post Share on other sites
Dr.Gonzo 392 Posted June 17, 2017 If you are not able to boot in 360 Dashboard, you cant update your 360 again with a Software solution, like swizzys SImple Nand Flasher. In your case you need a Hardware Flasher (mmc writer) to flash you last running Dashboard back to your Coronna v2 to fix this issue. Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 Have a sd adapter and can write the nand backup to the corona and it still boots, it's then on kernel and dash 17349. Quote Share this post Link to post Share on other sites
Dr.Gonzo 392 Posted June 17, 2017 It would be nice, if we can take a look into your XeBuild log.Maybe you have chosen a wrong Setting. Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 ================================== Swizzy's xeBuild GUI version 2.099 Log Started: Saturday 6/17/2017 1:46:52 PM ================================== *** Some console information *** CB Version: 0 ERROR: Unable to decrypt KV using specified CPUKey! This means the log will NOT contain information from your keyvault, it can be caused by etheir badkey or badblock/corrupt keyvault Using xell-reloaded for Glitch hack Including dashlaunch... Done! Including custom dashlaunch settings (launch.ini)... Done! Copying nand to data directory, this may take a while... Done! Checking if SMC is Glitch or Retail... Dumping current SMC... Done! Checking SMC... SMC is Glitch patched! it will be used the way it is... Parameters sent to xeBuild: -noenter -t glitch2 -c corona4g -d data -f 17511 -b XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -p XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX output.bin Building nand using xeBuild (this may take a while): --------------------------------------------------------------- xeBuild v1.18.800 --------------------------------------------------------------- base path changed to C:\Users\matpc\Desktop\MODS\J-Runner v3 (5) Core Pack\xebuild 2.99 unofficial\files ---- { Image Build Mode } ---- building glitch2 image done! fsroot found ok! --------------------------------------------------------------- output.bin image built, info: --------------------------------------------------------------- Kernel : 2.0.17511.0 Console : Corona NAND size : 48MiB MMC (system only) Build : Glitch (v2) Xell : power on console with console eject button Serial : XXXXXXXXXXXX ConsoleId : XXXXXXXXXXXX MoboSerial: XXXXXXXXXXXXXXXX Mfg Date : 10/16/2013 CPU Key : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 1BL Key : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX DVD Key : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX CF LDV : 7 KV type : type2 (hashed - unchecked, master key not available) --------------------------------------------------------------- xeBuild Finished. Have a nice day. --------------------------------------------------------------- Moving output to your destination directory... Done! Cleaning data and temporary directories... Done! ****** The app has now finished! ****** Quote Share this post Link to post Share on other sites
Dr.Gonzo 392 Posted June 17, 2017 XeBuild log looks good. Something went wrong (transmission of Data or whatever) in flashing process. Quote Share this post Link to post Share on other sites
darknezz19 5 Posted June 17, 2017 I've tried SD adapter to write and simple nand flasher to write. Maybe something is wrong with the nand image to begin with. Edit: Built image using glitch2m and it booted. Guess whoever modded this thing originally used a glitch2m image for whatever reason. 1 Quote Share this post Link to post Share on other sites
Dr.Gonzo 392 Posted June 18, 2017 Glitch2m can be useful, on Trinity & Corona Consoles, where fuses are have been blown up, because consoles with Glitch2m Images are booting with virtual fuses. Quote Share this post Link to post Share on other sites