I have a Halo 4 Limited console (Corona v3) and tried to read the NAND using NAND-X and the Corona QSB.
This is my first time using the NAND-X, so I installed the drivers from the official thread here. J-Runner saw the NAND-X (logo appeared), but when clicked on "Read NAND", nothing happened. I tried uninstalling and re-installing the drivers a few times, but it did not help. I then tried using the drivers from the J-Runner/common/drivers folder, but received a message from Windows that this driver was not supported on my version of Windows
.
Finally, I uninstalled the drivers, making sure to tell the system to delete the drivers, then removed these files:
Restarted J-Runner and the NAND-X was picked up fine and was able to read my NAND!
The moral of the story is the best drivers to use the first time are probably the ones provided by J-Runner.
NOTE 1: Rather than searching a folder for the driver automatically ("Update Driver" -> "Browse for a Driver" -> select folder), I used the manual install method ("Update Driver" -> "Browse for a Driver" -> "Let me Pick the Driver" -> "All devices" -> "Have Disk" -> select the driver)
NOTE 2: Do NOT have fluctuating EM fields nearby when reading NAND! After the first NAND read I started music playback via Bluetooth about 10 ft away (without MB in cage), and got NAND read errors all of a sudden. Since then I have read other posts where subwoofers and even turning a soldering iron on/off caused NAND read errors.
This is my first time using the NAND-X, so I installed the drivers from the official thread here. J-Runner saw the NAND-X (logo appeared), but when clicked on "Read NAND", nothing happened. I tried uninstalling and re-installing the drivers a few times, but it did not help. I then tried using the drivers from the J-Runner/common/drivers folder, but received a message from Windows that this driver was not supported on my version of Windows
.Finally, I uninstalled the drivers, making sure to tell the system to delete the drivers, then removed these files:
- C:\Windows\System32\drivers\PTLIBUSB0.SYS
- C:\Windows\System32\PTLIBUSB0.DLL
- C:\Windows\SYSWOW64\PTLIBUSB0.DLL
Restarted J-Runner and the NAND-X was picked up fine and was able to read my NAND!
The moral of the story is the best drivers to use the first time are probably the ones provided by J-Runner.
NOTE 1: Rather than searching a folder for the driver automatically ("Update Driver" -> "Browse for a Driver" -> select folder), I used the manual install method ("Update Driver" -> "Browse for a Driver" -> "Let me Pick the Driver" -> "All devices" -> "Have Disk" -> select the driver)
NOTE 2: Do NOT have fluctuating EM fields nearby when reading NAND! After the first NAND read I started music playback via Bluetooth about 10 ft away (without MB in cage), and got NAND read errors all of a sudden. Since then I have read other posts where subwoofers and even turning a soldering iron on/off caused NAND read errors.
