Lévai �dám 2 Posted May 25, 2016 Hello everyoneI upgraded to the Dashboard, an error occurred.I tried to write original nand was, Rawflash v4 were posted, but it does not work.All he writes that no signal input.I apologize for my bad english please help me console type: Slim Cronona V2 4GB 1 Quote Share this post Link to post Share on other sites
salah.rgh2 162 Posted May 26, 2016 Possible you make a mistake you must follow the correct way in the update http://forum.homebrew-connection.org/index.php?topic=144.0 Quote Share this post Link to post Share on other sites
felida 1653 Posted May 26, 2016 Hello everyone I upgraded to the Dashboard, an error occurred. I tried to write original nand was, Rawflash v4 were posted, but it does not work. All he writes that no signal input. I apologize for my bad english please help me console type: Slim Cronona V2 4GB Can you make a mistake during the update Did you try naming Rawflash to updflash To restore the file Follow update correct way http://forum.homebrew-connection.org/index.php?topic=144.0 xell/rawflash dont work on 4gb consoles.. you have to use swizzy's simple nand flasher for 4gb consoles.. but.. since it doesn't boot anymore, he has to use a 4gb r/w kit to re-do the nand.. Quote Share this post Link to post Share on other sites
salah.rgh2 162 Posted May 26, 2016 xell/rawflash dont work on 4gb consoles.. you have to use swizzy's simple nand flasher for 4gb consoles.. but.. since it doesn't boot anymore, he has to use a 4gb r/w kit to re-do the nand.. It can be a mistake in the update incorrectly I followed the right way and every good thing I have a xbox 360 4GB Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted May 26, 2016 E79 indicates an error within xam.xex, on NAND consoles (any console except for 4GB Corona/Winchester) this usually indicates a unhandled badblock (or one that was handled incorrectly) I've thus far never seen E79 on a MMC console, but it's a indicator that the write went wrong, most likely caused by a bad USB memory or similar (could also be something on your computer messing with the data, such as bad antivirus or even a piece of malware) Quote Share this post Link to post Share on other sites
Lévai �dám 2 Posted May 26, 2016 likely caused by a bad memory stick error"Dumping Your NANDUsing Xell (works on all consoles as of Xella-v0.992 Reloaded) "I read this:flashdmp.binkeyvault_raw.binfuses (CPU key, key DVD)rawflash 4gb model does not workswizzy's simple nand flasher I can not start from Xell menuXell: looking for files on local media and TFTP ... 1 Quote Share this post Link to post Share on other sites
felida 1653 Posted May 26, 2016 likely caused by a bad memory stick error "Dumping Your NAND Using Xell (works on all consoles as of Xella-v0.992 Reloaded) " I read this: flashdmp.bin keyvault_raw.bin fuses (CPU key, key DVD) rawflash 4gb model does not work swizzy's simple nand flasher I can not start from Xell menu Xell: looking for files on local media and TFTP ... You cant flash your nand via xell.. if you console no longer boots, you need the 4gb r/w kit installed.. period.. swizzy's app can flash once the console is running normally.. you need to take notice the 4gb corona have extra steps needed to be handled properly 2 Quote Share this post Link to post Share on other sites
Lévai �dám 2 Posted May 27, 2016 Thank you Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 2, 2016 Hello Guys again J-Runner error code : J-Runner v0.3 Beta (8) Started It's advised to run in administrator mode on Windows 8 Connection Error Checking Files Connection Error Failed to get DiskGeometry. TX Corona 4GB Nand reader qsb kit Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted December 2, 2016 You must run J-Runner as admin Sent from my SM-G903F Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 3, 2016 does not work Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted December 3, 2016 does not work Are you sure your console is a 4GB MMC Corona? if not, you installed the wrong hardware to read/write it Seeing as you're getting E79 it's highly unlikely to be a MMC Corona (they shouldn't be able to get that as they don't have badblocks) Another thing to know is that the kit needs a MMC compatible SD Card Reader... if you don't have that, then it won't work anyways... Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 3, 2016 Corona V2 4GB http://www.kepfeltoltes.eu/view.php?filename=8021.png http://www.kepfeltoltes.eu/view.php?filename=4352.png http://www.kepfeltoltes.eu/view.php?filename=31520161203_125337.jpg Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted December 3, 2016 Corona V2 4GB http://www.kepfeltoltes.eu/view.php?filename=8021.png http://www.kepfeltoltes.eu/view.php?filename=4352.png http://www.kepfeltoltes.eu/view.php?filename=31520161203_125337.jpg I can see that by the last image, the first 2 are useless... Did you provide power to your console? (connect the power cable, don't power it on) Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 3, 2016 yes see (PhysicalDrive2) Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted December 3, 2016 yes see (PhysicalDrive2)That's just the cardreader...Does windows ask you to format when you connect the kit? If not - the reader probably isn't mmc compatible or there is a connection problem somewhere... Sent from my SM-G903F Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 3, 2016 does not ask me to shape it, I Try MMC compatible reader thanks for the reply Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 12, 2016 I bought a card reader,but it does not work ( hama usb 2.0 card reader 35 in 1) "Failed to get DiskGeometry" Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 13, 2016 I could read checksum.md5 image_0000000.ecc nanddump1.bin (3.5GB) nanddump2.bin(3.5GB) nanddump3.bin(3.5GB) nanddump4.bin(3.5GB) nanddump1.bin(48,0MB) What more should I do? Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted December 13, 2016 I could read checksum.md5 image_0000000.ecc nanddump1.bin (3.5GB) nanddump2.bin(3.5GB) nanddump3.bin(3.5GB) nanddump4.bin(3.5GB) nanddump1.bin(48,0MB) What more should I do? What's that you're saying? I don't understand...Sent from my SM-G903F Quote Share this post Link to post Share on other sites
�dám Lévai 0 Posted December 13, 2016 http://www.kepfeltoltes.eu/view.php?filename=192realmodscene.png Quote Share this post Link to post Share on other sites
Swizzy 2084 Posted December 13, 2016 Next step now would be to rebuild the nand and flash it back i guess? Quote Share this post Link to post Share on other sites