RGH BB Jasper Random e64

[thebomber]

so i rgh a bb jasper for a shop, and the console returned now with e64

boots xell, but e64 on dash, it made that before, but i bulit another image using multibulider and it went away, now it came back,

the original nand had 2-3 bad blocks, so my question is can i use a donor nand without Bad blocks and bulid a custom image with the cpu key, or not, and i need a 64mb nand right 16mb cant do it, or if i can use my original files how do i counter this e64 :facepalm:

first time i encounter it,

 

[Haygar]

As long as your bad blocks have been remapped properly at the end of your built image AND the original was read without errors it should be ok. Try reading the nand back and compare to see if you have other bad block problems.
Also, use J-Runner instead of multi-builder. It also has a nand compare feature.

As for a donor, you will want to get all the info from your original, kv, cb, ldv, smc_config and build up from there, J-runner can do this too in the latest builds: J-Runner 275 upwards>Advanced>Create image without nand

 

[WNYConsoles]

Any E64 with stock nand? Check the usual suspects (SATA Cable, DVD drive, etc). I find myself twisting the sata cable at times when bench testing a unit so I have seen a few go bad and cause this.

Check FW (If you RGH to 14719) but have a old LT+ 1.1, etc installed that would cause E64

EDIT: Thinking more about this I had this same issue not so long ago during a RGH bench test. System was on 12625 or something similar and I did the RGH successfully, installed the DVD drive and instant E64 as the FW did not match the dashboard.

Always good to update to the latest dashboard before RGH (except for 14719 of course).

 

[thebomber]

it was on 13599 dash, thats why i dont suspect the firmware issue, but might be the dvd drive, will crack it open tommorow and check, cause it made that before and i flashed the drive, and worked,

so if the same happenes again, should i return to stock nand, then update to 14699 then flash the image or what

 

[WNYConsoles]

That wouldn't be a bad idea. I always update them before RGH, just makes sense to me since 14699 is so close to the hacked dash which is 14719 atm.

 

[thebomber]

i replaced the sata cable with another and baam works without issues:biggrin:

 

[WNYConsoles]

I think they get brittle inside from the heat and such over time and once twisted or handled can cause issues.