View Single Post
Old 09-08-2012   #7
jamesnesc709
Member
 
jamesnesc709's Avatar
 
Join Date: Dec 2009
Location: usa fla
Posts: 642
Likes: 100
Liked 41 Times in 39 Posts
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Question

Originally Posted by Bigbones87 View Post
You are correct about the e3 flasher. It is for nor consoles, unless you solder the e3 linker in. I think you can use the e3 linker on NAND, but I am not 100% sure. That site you linked to me in the pm said that he changed the power supply for this issue and it usually works. It doesn't make sense that the console just shuts itself off if you use a different hard drive. The firmware is stored on the NAND 100%, so it shouldn't be a problem. Ideally it should finish the update just checking to make sure there is a hard drive, and then after the update it would come up and say this hard drive needs to be formatted. It could be the 3.56 bug, but that was caused by changing hard drives or fully formatting the original hard drive while on 3.56. I will try and help you by looking around for things it could be. I have hit a bump.
yea i might have to use like a Progskeet flashing the nand but i want to do that with my last resort can Progskeet can fix the red screen of death on a nand system . because it almost the same as e3 flasher ?
edit
I also been trying find ways to fix the for at least 2 months now . I had no choice to ask here .
__________________

Last edited by jamesnesc709; 09-08-2012 at 12:26 AM. Reason: add
jamesnesc709 is offline   Reply With Quote