Jump to content
RealModScene

thundermonkey

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thundermonkey

  • Rank
    RMS Freshman
  1. Thank you for this tool. I used a different NAND flasher while updating a kernel just now and encountered problems. Switched to this one and everything went fine.
  2. I recently updated a RGH Falcon from 17511 to 17526 with no problems, but have run into trouble trying to do the same thing on a RGH Trinity. I am getting E71 errors like S0m, so I will reply here rather than start a new topic. I updated the Falcon and Trinity using xeBuild_Gui2.098 to 17526. After the Trinity update, the Aurora and FSD dashboards loaded, but when I tried to run the default Xbox dash I got an E71 error. I used dashlaunch to check the kernel and determined that it had been updated to 17526. I flashed back to 17511, and found that the default dash still produces E71 errors. (!) I then went back to 17526. Since the working dashes are on my hard drive, I am currently in the same position as s0m of requiring the hard drive to boot. I have been careful to unplug the console after the flashing. I've also tried hacked images created with and without the FCRT.bin check, and found no difference. Any ideas on how I can get the Xbox dash to run again? UPDATE: I did the kernel update again, this time using Swizzy's Simple 360 NAND Flasher, and the problem with the default dash went away. For the record, the flasher I was originally using was NAND Flasher 360 v1.2.
×
×
  • Create New...