FIXED Falcon being difficult, getting E79 error, a little help please!!

[zerocool420]

Console Type: Falcon
NAND size: 16
Dashboard version: 2.016537
CB version: 5774
Screenshot of NAND details from J-Runner:
(attach an image to your post)
J-Runner log:
POST output from J-Runner (either POST_OUT monitor or RATER output):
(2 cycles is enough)
updflash.bin log (if applicable):
Image of R-JTAG board:
Images of close-up soldering to motherboard:
http://s1347.photobucket.com/user/Heath_Hoppes/library/

Description of problem: This is my first rjtag and I'm frustrated and stuck. I got my ultimate kit, soldered all the qsb's in, read my nand, compared them, wrote xell to the box and tried to boot it. I tried to boot this box trying every combination for approx. 6 hours and all it would do is red ring except with the 1.2v soldered, dips 4 & 7 on, aud clam with 1-3 soldered, 3 way switch in the middle and other switch on and then it would go to the E79 screen. I have checked all my solder joints for bridges and continuity on both sides of the board and everything seems fine. If I re-flash my stock nand and un solder the 5v from the board, it will boot and play normally. So where do I go from here? I would like to thank everyone in advance for their time and effort in helping me with this problem, I really appreciate it!! Have a great day!

Was the console working before you started: Y

 

[Martin C]

It looks like you're booting ok.

"XeLL file created Successfully falcon.bin"

You're using AUD_CLAMP, so you need to make sure you tick AUD_CLAMP BEFORE creating Xell.

It should say "XeLL file created Successfully falcon_aud_clamp.bin"

Once written, remove the PSU for at least 20 secs then reconnect.

 

[HoggFace]

OP as your 1st post can I just say well done how you have compiled your post! This is exactly how a help post should look. Every info needed to get full support. Wish more people would follow this when posting for help.

 

[zerocool420]

awesome, re writting the nand with aud clamp in xell and unplugging and waiting 20 sec worked, it boots into xell now. Now, when it boots, it loads and gets to a point where it says trying and it just keeps looping dvd:, sda:, uds: amd tftp and never goes any farther. What the next step i should take now?

 

[DreamZ]

Grab your CPU key, and make a freeboot image using jrunner

Flash to the console and freeboot should load up.
Make sure you tick aud clamp ofc if using audclamp

 

[zerocool420]

ok i let it run and i got my cpu key but it still just hangs where it was. no if i go to jrunner and insert my cpu key and try to create xebuild image, it wants to know my dash board. Now im confused because when i checked my dash with the original nand it was 2.0167 but i dont see that, am i missing something or do i need to add that to it and then create the image?

 

[zerocool420]

i dont see an option for freeboot in jrunner, just xebuild.

 

[AllyNerd]

Huh? Your saying you dont know how to create a freeboot image in jrunner? You read the manual by any chance

- - - Updated - - -

Huh? Your saying you dont know how to create a freeboot image in jrunner? You read the manual by any chance

 

[zerocool420]

yes i have the manual open right now, im just confused on where im at at the moment. im at the part in the manual where it tells to build a xebuild image. i have it set with the right dash now but when i push create image it says ini's are missing??

 

[Martin C]

You need to enable filechecks in settings and then restart J-Runner.

 

[zerocool420]

its checked and when i restart jrunner in the box it says cannot connect to the remote server.

 

[zerocool420]

ok, noob mistake, i didnt have the folders from the other jrunner file copied to the jrunner so now it let me build an image and now im writting the nand, well see how this goes!!

 

[zerocool420]

AWESOME it boots!!! Cool, now it will boot to the dashboard but it seems like it take 5-8 sec to do it. i thought it was suppost to be instant, whats the best way to go about adjusting it? im asking because i could only find one setting that would even allow me to boot up the console, any other dip settings or what not will not let it boot up.

 

[Martin C]

no console instantly boots, not even retail units. If it takes 5-8 seconds then it's classed as instaboots.

I worry about some people and expectation. When you turn on your TV do you get a picture immediately or do you need to wait for it to 'boot'?

 

[zerocool420]

you are totally correct and I'm just an amature. I used the rater and changed between open, 1.2v and 1.8 v and found that with 1.2v after 4 cycles it would rate a 9.25 so im happy. I want to thank all you guys who chimed in and helped me figure this one out. Like I said, im a noob, but now I have a much better understanding of whats going on so im sure the next one will not be as bad. THANKS AGAIN EVERYONE!!!!!!