R-jtag install complete, RROD when back in its case!

[Dark_Riku]

Ok done as instructed relocated it to the top of the dvd drive, even moved the d cpu_rst point to over the fans and quess what still doing same faults. It boots on 360 logo for 1 second then drops into rrod e79. It really must be me and luck i have done all you have said and followed it exactly to the guide and like hell it would work for me. It wouldnt have matter so much if it failed from just after installing the r-jtag board but i ooted perfect 40-50 times in 1 to 3 cycles. Yet as soon as i carefully lift it back into its case i breaks. Where is the fairness and logic into that? :mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2::mad2:

Have you tried making a new image? any bad blocks etc?

 

[Scrufdog]

Perhaps try changing the power mode. Some falcons are sensitive to that when you glitch them.

 

[Morgiee101]

Ok this is annoying, on last ditch attempt before i give up today or at all, i wiped the full demon nand and installed the stock nand image to the demon and along with the created xell reloaded image, and it glitches in 5 cycles to xell and stays on. Yes when switching the demon off and booting on normal nand it RROD immediately? really strange, here is a link to it again.

http://youtu.be/W3H04N5zoUc

 

[DreamZ]

May sound silly but have you tried loading xell , then immediately pressing the demon button then trying to boot? Does it boot like that?

Had a box I had a look at before do that

 

[Morgiee101]

Have you tried making a new image? any bad blocks etc?

Tried a new glitch image mate still no luck and no both stock nands have no bad blocks.

Perhaps try changing the power mode. Some falcons are sensitive to that when you glitch them.

Were is the power mode mate? is it the 1.2v and 1.8v jumpers you are referring to? or is it a software setting when creating a nand image on xbuild? Strange though when you boot standard nand the non touched one its immediate RROD? will those ribon cables enabe and disable the demon nand or does the en_cr have to be wired in?

 

[Morgiee101]

May sound silly but have you tried loading xell , then immediately pressing the demon button then trying to boot? Does it boot like that?

Had a box I had a look at before do that

Never tried that mate because the strict instruction when i first got the demon was that during boot of a console to never press the demon button as this could damage the console. Only press the button when the console is powered down.

 

[Scrufdog]

Search for falcon freezing power mode. There are a bunch of threads explaining how to change it.

 

[Morgiee101]

Had a good luck around, their is loads of threads about falcon freezing and mention power mode changing but their is not a solid guide on how to do it, could you post me a link to a good guide on? Thanks

 

[Martin C]

This isn't a power mode issue. If the console boots ok outside the cage, you've a dodgy solder connection or something causing massive interference.

 

[Morgiee101]

Dont know if you seen the last few posts i made but i managed to load the stock nand on will xell and boots within 5 cycles to xell and stays on too while in its case (made a new video on it). The normal nand goes onto rrod instant. smc config of power mode still worth tweaking to see if it will keep it on a glitch image? Checked all connections and moved the r-jtag to on top of the dvd drive.

 

[Martin C]

Don't touch power mode. That's a red herring and wish people didn't just throw it out there.

If it was a power mode you would have seen this issue on RGH2.

So once again (in case I'm not making myself clear), this is NOT an SMC power mode issue. Do NOT mess with these settings.

 

[Morgiee101]

So what do you Suggest Martin? iv'e checked what you have asked all connections and bridging, the demon nand boots to xell no problem and stays on, when you install and boot the glitched dashboard it boots to the logo and jumps to a RROD E79 error: 1033. Can only be software related. Also why would the stock nand fail to boot if the image has had no tampering with it only to read the nand.

Thanks

 

[Martin C]

R-JTAG is a JTAG NAND, not a glitched NAND. I hope you're not building an RGH2 NAND for it.

 

[Morgiee101]

No i have not mad it based on rgh2 image here are some screenshots to show you what i have done during creating the jtag image. The screenshot of the smc I have not edited its more to show you the info for the nand image, i have NOT edited the smc in any way and will not unless instructed.

 

[Martin C]

So - xell boots fine but the R-JTAG image gives you E79?

Does 'eject' with the R-JTAG image give you Xell?

 

[Morgiee101]

So - xell boots fine but the R-JTAG image gives you E79? Yes correct mate

Does 'eject' with the R-JTAG image give you Xell? ooohhhh never tried this, will try now and report in 5 mins

 

[Morgiee101]

Ok so created a fresh jtag image as per screenshots, loaded demon nand via the eject button and xell boots in 2 cycles, but still get E79 when booting demon nand via power button, here is the j runner log of creating nand and writing, i noticed Invalid Blocks : 0x22B when writing nand but the two stock nands are the same with no bad blocks. Strange the comparing says one thing but the writing says otherwise. The bits i put in red are strange too.


Filechecks disabled - No Filechecks carried out
Initializing nanddump1.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Comparing...
Nands are the same
Aud_Clamp Selected
R-Jtag Selected
Load Files Initiliazation Finished
Clean SMC detected
Patching Jasper version 2.3 SMC at offset 0x12BA
16537
Started Creation of the 16537 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.07.632
---------------------------------------------------------------
base path changed to C:\Users\Daniel's\Desktop\J-Runner\xeBuild
---- { Image Build Mode } ----
building jtag image




******* WARNING: could not patch SMC reset limit!


---------------------------------------------------------------
C:\Users\Daniel's\Desktop\J-Runner\351509583105\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16537.0
Console : Falcon
NAND size : 16MiB
Build : JTAG
Xell : power on console with console eject button
Serial : 351509583105
ConsoleId : 019367284134
MoboSerial: 757847C125628305
Mfg Date : 07/26/2008
CPU Key : **********************************
1BL Key : ********************************
DVD Key : ******************************
CF LDV : 21
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Daniel's\Desktop\J-Runner\351509583105
Image is Ready
DEMON
Hardware : Demon Phat
Firmware : 1.4
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0x22B
Writing Nand
Done!
in 0:25 min:sec

 

[Martin C]

so deal with the bad block per normal process?

Not sure why you'd mention this without dealing with it.

 

[Morgiee101]

Because i only noticed it now when writing. The j runner tutorial says it corrects bad blocks when discovered during comparing bad nands. So how do you do it any other time? other strange thing is why it says falcon as the nand yet patches as a jasper?

Thanks

 

[Martin C]

the patching is completely normal.

follow normal process for a DemoN with bad blocks.
(erase DemoN, build nand with noremap, use advanced write).