Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About flash70

  • Rank
    RMS Freshman

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That's weird... I followed the guide to the letter including all changes required for 4G corona, flashed the nand, no errors, but after reboot the kernel version did not change like nothing happend. What could be the problem? 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... <removed> Successfully wrote 0x3000000 bytes from game:\updflash.bin to Flash! Completed after 70.00 seconds Shutting down in 5....4....3....2....1....BYE!
  2. Thanks for your answer. As I mentioned, this is part of a bigger issue... I got Lego Dimensions and wanted to use it with my console but it won't recognize the Toy Pad. I saw some discussions where people solved this by upgrading the kernel. When I tried upgrading the kernel remotely using the updserver feature of DashLaunch, it got to the point of flashing the console and that happened: ------ flashing console ------ sending flash data to console... file sent OK, awaiting result...timeout waiting for data, 0 failed! So I thought maybe a DashLaunch upgrade will solve this, but now I see it might be a HW problem. Is there a test I can do to verify it's a bad NAND problem? BTW My console has a corona board and kernel v. 2.0.16747
  3. Hi all, The DashLaunch issue is part of a bigger story, but let's take it one at a time... I have a slim 360 with RGH. The DashLaunch version is 3.12. When I run the newest DashLaunch (3.18) from a USB drive it detects the older version and suggest an update, but if I press the update button everything freezes. I don't know if it's related, but a while back I had a crash of the internal storage space, and it appears on the console as unformatted storage device (any attempt to format it simply fails). I had to re-create the player profiles and use part of the USB HDD as XBOX storage to keep save files, but it holds and the console is usable. Any ideas what's causing the DashLaunch to freeze? Any other way to update the version?
  • Create New...