RGH Posible fix for Falcon RGH 2 freezing problem

[Groxack]

Posible Fix for Falcon RGH 2 freezing problem

Hi, first of all I apologize for my poor English and second I'm not a total noob I have done dozens of rgh's up to the corona v2. Now, I been searching for a solution for the freezing problem on the falcon whit RGH 2 for a few weeks now, and reading thru the Spanish forum "el otro lado" I found a post talking about how a member fixed the freezing problem injecting the first Mg of his stock nand into a donor nand and then using this one to produce the xebuild image, other member's also reported success using this method, some others didn't succeed on his first try but after some tuning on the temp settings they got it.

Unfortunately for me this didn't work, the only thing that i noticed on the console after using this fix and a few changes in temp settings was the time that it took to freeze (and it didn't have nothing to do whit the fans running at 100%). first I tried 50 50 55 and 100 100 100 on max temps and it worked for about an hour and half and it froze again, then i decided to use dashlaunch temp monitor to check the temperature on real time and chenged the max temp setings to 70 70 70 and this is what i got:

** Reading from: 10/26/2012 9:17:19 PM ** CPU: 51.3°C GPU: 53.1°C EDRAM: 56.4°C Mobo: 32.3°C Unkown: 74

** Reading from: 10/26/2012 9:17:29 PM ** CPU: 51.3°C GPU: 53.1°C EDRAM: 56.3°C Mobo: 32.3°C Unkown: 75

** Reading from: 10/26/2012 9:17:34 PM ** CPU: 51.3°C GPU: 53.1°C EDRAM: 56.4°C Mobo: 32.3°C Unkown: 76

** Reading from: 10/26/2012 9:17:39 PM ** CPU: 51.3°C GPU: 53.1°C EDRAM: 56.3°C Mobo: 32.3°C Unkown: 77

** Reading from: 10/26/2012 9:17:44 PM ** CPU: 51.3°C GPU: 53.1°C EDRAM: 56.3°C Mobo: 32.3°C Unkown: 77

** Reading from: 10/26/2012 9:17:49 PM ** CPU: 51.2°C GPU: 53.1°C EDRAM: 56.3°C Mobo: 32.3°C Unkown: 78

** Reading from: 10/26/2012 9:17:54 PM ** CPU: 51.1°C GPU: 53.1°C EDRAM: 56.3°C Mobo: 32.3°C Unkown: 78

** Reading from: 10/26/2012 9:17:59 PM ** CPU: 51.1°C GPU: 53.0°C EDRAM: 56.2°C Mobo: 32.3°C Unkown: 79

** Reading from: 10/26/2012 9:18:04 PM ** CPU: 51.1°C GPU: 53.0°C EDRAM: 56.2°C Mobo: 32.2°C Unkown: 79

** Reading from: 10/26/2012 9:18:09 PM ** CPU: 51.1°C GPU: 52.9°C EDRAM: 56.2°C Mobo: 32.2°C Unkown: 80

** Reading from: 10/26/2012 9:18:14 PM ** CPU: 51.1°C GPU: 52.9°C EDRAM: 56.1°C Mobo: 32.2°C Unkown: 80

** Reading from: 10/26/2012 9:18:19 PM ** CPU: 51.0°C GPU: 52.9°C EDRAM: 56.1°C Mobo: 32.3°C Unkown: 80

** Reading from: 10/26/2012 9:18:24 PM ** CPU: 51.0°C GPU: 52.8°C EDRAM: 56.1°C Mobo: 32.2°C Unkown: 81

** Reading from: 10/26/2012 9:18:29 PM ** CPU: 50.9°C GPU: 52.8°C EDRAM: 56.0°C Mobo: 32.2°C Unkown: 81

** Reading from: 10/26/2012 9:18:34 PM ** CPU: 50.9°C GPU: 52.7°C EDRAM: 56.0°C Mobo: 32.1°C Unkown: 81

** Reading from: 10/26/2012 9:18:39 PM ** CPU: 50.8°C GPU: 52.6°C EDRAM: 55.9°C Mobo: 32.1°C Unkown: 82

** Reading from: 10/26/2012 9:18:44 PM ** CPU: 50.8°C GPU: 52.6°C EDRAM: 55.8°C Mobo: 32.1°C Unkown: 82

** Reading from: 10/26/2012 9:18:49 PM ** CPU: 50.7°C GPU: 52.6°C EDRAM: 55.8°C Mobo: 32.2°C Unkown: 82

** Reading from: 10/26/2012 9:18:54 PM ** CPU: 50.7°C GPU: 52.6°C EDRAM: 55.8°C Mobo: 32.2°C Unkown: 83

** Reading from: 10/26/2012 9:18:59 PM ** CPU: 50.7°C GPU: 52.5°C EDRAM: 55.7°C Mobo: 32.1°C Unkown: 83

** Reading from: 10/26/2012 9:19:04 PM ** CPU: 50.6°C GPU: 52.3°C EDRAM: 55.6°C Mobo: 32.1°C Unkown: 83

** Reading from: 10/26/2012 9:19:09 PM ** CPU: 50.5°C GPU: 52.1°C EDRAM: 55.4°C Mobo: 32.0°C Unkown: 83

** Reading from: 10/26/2012 9:19:14 PM ** CPU: 50.5°C GPU: 52.0°C EDRAM: 55.2°C Mobo: 31.9°C Unkown: 82

** Reading from: 10/26/2012 9:19:19 PM ** CPU: 50.4°C GPU: 51.8°C EDRAM: 55.0°C Mobo: 31.9°C Unkown: 82

** Reading from: 10/26/2012 9:19:24 PM ** CPU: 50.3°C GPU: 51.6°C EDRAM: 54.9°C Mobo: 31.8°C Unkown: 82

** Reading from: 10/26/2012 9:19:29 PM ** CPU: 50.3°C GPU: 51.5°C EDRAM: 54.8°C Mobo: 31.8°C Unkown: 82

** Reading from: 10/26/2012 9:19:34 PM ** CPU: 50.3°C GPU: 51.4°C EDRAM: 54.7°C Mobo: 31.6°C Unkown: 81

** Reading from: 10/26/2012 9:19:39 PM ** CPU: 50.2°C GPU: 51.3°C EDRAM: 54.5°C Mobo: 31.5°C Unkown: 81

** Reading from: 10/26/2012 9:19:44 PM ** CPU: 50.1°C GPU: 51.2°C EDRAM: 54.5°C Mobo: 31.5°C Unkown: 81

** Reading from: 10/26/2012 9:19:49 PM ** CPU: 50.1°C GPU: 51.1°C EDRAM: 54.3°C Mobo: 31.6°C Unkown: 81

** Reading from: 10/26/2012 9:19:54 PM ** CPU: 49.9°C GPU: 50.6°C EDRAM: 54.2°C Mobo: 31.5°C Unkown: 80

** Reading from: 10/26/2012 9:19:59 PM ** CPU: 49.9°C GPU: 50.9°C EDRAM: 54.0°C Mobo: 31.6°C Unkown: 80

** Reading from: 10/26/2012 9:20:04 PM ** CPU: 49.9°C GPU: 50.9°C EDRAM: 54.0°C Mobo: 31.6°C Unkown: 80

** Reading from: 10/26/2012 9:20:09 PM ** CPU: 49.8°C GPU: 50.9°C EDRAM: 54.0°C Mobo: 31.5°C Unkown: 79

** Reading from: 10/26/2012 9:20:14 PM ** CPU: 49.8°C GPU: 50.5°C EDRAM: 54.1°C Mobo: 31.5°C Unkown: 79

** Reading from: 10/26/2012 9:20:19 PM ** CPU: 49.5°C GPU: 50.6°C EDRAM: 53.6°C Mobo: 31.5°C Unkown: 79

** Reading from: 10/26/2012 9:20:24 PM ** CPU: 49.5°C GPU: 50.5°C EDRAM: 53.5°C Mobo: 31.4°C Unkown: 78

** Reading from: 10/26/2012 9:20:29 PM ** CPU: 49.9°C GPU: 50.0°C EDRAM: 53.5°C Mobo: 31.3°C Unkown: 78

** Reading from: 10/26/2012 9:20:34 PM ** CPU: 49.6°C GPU: 49.9°C EDRAM: 53.4°C Mobo: 31.4°C Unkown: 77

** Reading from: 10/26/2012 9:20:39 PM ** CPU: 49.4°C GPU: 49.8°C EDRAM: 53.2°C Mobo: 31.3°C Unkown: 77

** Reading from: 10/26/2012 9:20:44 PM ** CPU: 49.4°C GPU: 49.6°C EDRAM: 53.1°C Mobo: 31.3°C Unkown: 77

** Reading from: 10/26/2012 9:20:49 PM ** CPU: 49.1°C GPU: 49.7°C EDRAM: 53.2°C Mobo: 31.6°C Unkown: 76

** Reading from: 10/26/2012 9:20:54 PM ** CPU: 49.3°C GPU: 49.4°C EDRAM: 52.9°C Mobo: 31.2°C Unkown: 76

** Reading from: 10/26/2012 9:20:59 PM ** CPU: 49.3°C GPU: 49.4°C EDRAM: 52.8°C Mobo: 31.3°C Unkown: 75

** Reading from: 10/26/2012 9:21:04 PM ** CPU: 49.4°C GPU: 49.3°C EDRAM: 52.7°C Mobo: 31.2°C Unkown: 75

** Reading from: 10/26/2012 9:21:09 PM ** CPU: 49.4°C GPU: 49.3°C EDRAM: 52.7°C Mobo: 31.2°C Unkown: 74

** Reading from: 10/26/2012 9:21:14 PM ** CPU: 49.5°C GPU: 49.1°C EDRAM: 52.6°C Mobo: 31.2°C Unkown: 74

** Reading from: 10/26/2012 9:21:19 PM ** CPU: 50.0°C GPU: 49.1°C EDRAM: 52.5°C Mobo: 31.1°C Unkown: 74

** Reading from: 10/26/2012 9:21:24 PM ** CPU: 49.6°C GPU: 50.3°C EDRAM: 53.4°C Mobo: 31.1°C Unkown: 74

** Reading from: 10/26/2012 9:21:29 PM ** CPU: 49.5°C GPU: 50.7°C EDRAM: 53.9°C Mobo: 31.0°C Unkown: 75

** Reading from: 10/26/2012 9:21:34 PM ** CPU: 49.5°C GPU: 51.0°C EDRAM: 54.3°C Mobo: 31.0°C Unkown: 76

** Reading from: 10/26/2012 9:21:39 PM ** CPU: 49.6°C GPU: 51.2°C EDRAM: 54.5°C Mobo: 30.9°C Unkown: 76

** Reading from: 10/26/2012 9:21:44 PM ** CPU: 49.5°C GPU: 51.6°C EDRAM: 54.9°C Mobo: 30.9°C Unkown: 77

** Reading from: 10/26/2012 9:21:49 PM ** CPU: 49.5°C GPU: 52.0°C EDRAM: 55.2°C Mobo: 31.0°C Unkown: 77

** Reading from: 10/26/2012 9:21:54 PM ** CPU: 49.8°C GPU: 52.2°C EDRAM: 55.4°C Mobo: 30.9°C Unkown: 78

** Reading from: 10/26/2012 9:21:59 PM ** CPU: 49.6°C GPU: 52.3°C EDRAM: 55.6°C Mobo: 31.0°C Unkown: 79

** Reading from: 10/26/2012 9:22:04 PM ** CPU: 49.5°C GPU: 52.4°C EDRAM: 55.8°C Mobo: 31.0°C Unkown: 79

** Reading from: 10/26/2012 9:22:09 PM ** CPU: 50.2°C GPU: 52.6°C EDRAM: 55.8°C Mobo: 31.0°C Unkown: 80

** Reading from: 10/26/2012 9:22:14 PM ** CPU: 49.4°C GPU: 52.7°C EDRAM: 56.0°C Mobo: 31.0°C Unkown: 81

** Reading from: 10/26/2012 9:22:19 PM ** CPU: 49.4°C GPU: 52.8°C EDRAM: 56.2°C Mobo: 31.0°C Unkown: 81

** Reading from: 10/26/2012 9:22:24 PM ** CPU: 49.4°C GPU: 52.9°C EDRAM: 56.3°C Mobo: 31.0°C Unkown: 82

** Reading from: 10/26/2012 9:22:29 PM ** CPU: 49.3°C GPU: 53.1°C EDRAM: 56.3°C Mobo: 31.0°C Unkown: 83

** Reading from: 10/26/2012 9:22:34 PM ** CPU: 49.4°C GPU: 53.1°C EDRAM: 56.6°C Mobo: 31.0°C Unkown: 84

** Reading from: 10/26/2012 9:22:39 PM ** CPU: 49.4°C GPU: 53.3°C EDRAM: 56.7°C Mobo: 31.1°C Unkown: 85

** Reading from: 10/26/2012 9:22:44 PM ** CPU: 49.4°C GPU: 53.5°C EDRAM: 56.7°C Mobo: 31.1°C Unkown: 85

** Reading from: 10/26/2012 9:22:49 PM ** CPU: 49.4°C GPU: 53.4°C EDRAM: 56.9°C Mobo: 31.1°C Unkown: 87

** Reading from: 10/26/2012 9:22:54 PM ** CPU: 49.4°C GPU: 53.5°C EDRAM: 56.9°C Mobo: 31.1°C Unkown: 88

** Reading from: 10/26/2012 9:22:59 PM ** CPU: 49.4°C GPU: 53.6°C EDRAM: 57.0°C Mobo: 31.1°C Unkown: 88

** Reading from: 10/26/2012 9:23:04 PM ** CPU: 49.5°C GPU: 53.7°C EDRAM: 57.0°C Mobo: 31.1°C Unkown: 89

** Reading from: 10/26/2012 9:23:09 PM ** CPU: 49.5°C GPU: 53.8°C EDRAM: 57.1°C Mobo: 31.0°C Unkown: 90

** Reading from: 10/26/2012 9:23:14 PM ** CPU: 50.1°C GPU: 54.0°C EDRAM: 57.3°C Mobo: 31.1°C Unkown: 92

** Reading from: 10/26/2012 9:23:19 PM ** CPU: 49.7°C GPU: 54.2°C EDRAM: 57.4°C Mobo: 31.1°C Unkown: 93

** Reading from: 10/26/2012 9:23:24 PM ** CPU: 49.7°C GPU: 54.3°C EDRAM: 57.5°C Mobo: 31.1°C Unkown: 94

** Reading from: 10/26/2012 9:23:29 PM ** CPU: 49.7°C GPU: 54.2°C EDRAM: 57.6°C Mobo: 31.1°C Unkown: 95

** Reading from: 10/26/2012 9:23:34 PM ** CPU: 49.7°C GPU: 54.2°C EDRAM: 57.7°C Mobo: 31.1°C Unkown: 97

** Reading from: 10/26/2012 9:23:39 PM ** CPU: 49.7°C GPU: 54.4°C EDRAM: 57.7°C Mobo: 31.1°C Unkown: 98

** Reading from: 10/26/2012 9:23:44 PM ** CPU: 49.6°C GPU: 54.4°C EDRAM: 57.8°C Mobo: 31.2°C Unkown: 99

** Reading from: 10/26/2012 9:23:49 PM ** CPU: 49.6°C GPU: 54.4°C EDRAM: 57.8°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:23:54 PM ** CPU: 49.6°C GPU: 54.4°C EDRAM: 57.8°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:23:59 PM ** CPU: 49.8°C GPU: 54.3°C EDRAM: 57.7°C Mobo: 31.1°C Unkown: 100

** Reading from: 10/26/2012 9:24:04 PM ** CPU: 50.0°C GPU: 54.6°C EDRAM: 57.8°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:09 PM ** CPU: 50.0°C GPU: 54.7°C EDRAM: 57.9°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:14 PM ** CPU: 50.0°C GPU: 54.7°C EDRAM: 58.0°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:19 PM ** CPU: 50.0°C GPU: 54.7°C EDRAM: 58.1°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:24 PM ** CPU: 50.0°C GPU: 54.8°C EDRAM: 58.2°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:29 PM ** CPU: 50.0°C GPU: 54.9°C EDRAM: 58.3°C Mobo: 31.3°C Unkown: 100

** Reading from: 10/26/2012 9:24:34 PM ** CPU: 50.1°C GPU: 54.9°C EDRAM: 58.3°C Mobo: 31.3°C Unkown: 100

** Reading from: 10/26/2012 9:24:39 PM ** CPU: 50.1°C GPU: 55.0°C EDRAM: 58.4°C Mobo: 31.3°C Unkown: 100

** Reading from: 10/26/2012 9:24:44 PM ** CPU: 50.1°C GPU: 55.0°C EDRAM: 58.4°C Mobo: 31.3°C Unkown: 100

** Reading from: 10/26/2012 9:24:49 PM ** CPU: 50.1°C GPU: 55.1°C EDRAM: 58.4°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:54 PM ** CPU: 50.1°C GPU: 55.0°C EDRAM: 58.5°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:24:59 PM ** CPU: 50.1°C GPU: 55.1°C EDRAM: 58.4°C Mobo: 31.2°C Unkown: 100

** Reading from: 10/26/2012 9:25:04 PM ** CPU: 50.1°C GPU: 55.3°C EDRAM: 58.5°C Mobo: 31.2°C Unkown: 100

it just worked for 20 minutes, then i decided to use the stock temp settings (80 75 78 and 100 100 102) and it worked again for about an hour and half, Unfortunately I didn't save the log this time but temps kept around 60 60 55 the whole time again. I still trying to make it work, but nothing new has come up.
if I remember correctly, Martin c mentioned something about the SMC and and the temperatures stored in this one, I hope he can take a look at this.

 

[madhaxer]

pics of wire routing as per rules pics are needed , and have you tried retail image bet your coming down with the rrod blues

 

[Groxack]

I can post some pictures, but I'm sure thats not the problem, I even took off all the wiring after the console glitched to see if there was any change but that wasn't the case.
Also, I already restored the console to stock and it worked fine for weaks, so I guess this one has the frezzing problems that some people are reporting.

 

[Groxack]

Well I really hoped for more input in this post, but I guess nobody cares or is to busy to respond to a noob. Anyways, I think that I finally hit the nail, after a few days of trial and error I received a response on other forum from another user telling me that he used donated nand with dashboard version 13604 and it worked for him very well, so after i got home yesterday, I proceeded to use the donated nand with the version indicated to make my freeboot image, then I flashed the image and stared testing the console and it went thru for 5 hours without a single freeze or fatal crash, I will continue testing it so I'm sure it's cured for good.
Well there you have it guys, It would be interesting hear from others with this same problem.

 

[Martin C]

If you could upload the smc-config.bin from this NAND I would be interested in seeing it.

 

[Groxack]

Good to see you joining the thread martin, right now I'm at work so I don't have the nand That I used to flash the console, when i get home I'll upload all the stuff that you need, for now here is the link to the donated nand that I used:

http://www2.zippyshare.com/v/62419006/file.html

 

[an01523]

Hello! Can you explain how you did this? I want to try on my Falcon 14719 with RGH 2.0. I allready have CPU-Key, but freeze in Freeboot after 30-60 seconds every time.

 

[Groxack]

well there are different ways of doing this but the easiest is just to get a donor nand and use the "inject1M" option on Autogg or just get smc_conf.bin and inject it into your original nand and proceed to create your freeboot image.

 

[Martin C]

so you used the SMC config from this Donor NAND?

 

[Groxack]

well I guess thats where the problem lies, since you just inject the first Mg from your nand, and the SMC config is at the end, But I guess you could explain this better, since I'm just talking out my ass.

 

[Martin C]

No, that's spot on.

On a falcon, the smc config is at 3de. The 1st MB is up to block 40 and the only data in here we keep for an RGH would be the KV and SMC. So it's possibly the latter. I'll take a look later tonight.

 

[Groxack]

one more detail that I must add is that some games still freezing after a few hours, others just keep going without a single problem.

 

[an01523]

I can confirm: it works fine with donor nand. no more freeze.

i have read 1MB with "nandpro.exe nanddump.bin: -r16 nand1mb.bin 0 3E" from my orignand.
then used "inyect1M" to inject nand1mb.bin with autogg in donor nand.

 

[Martin C]

I can confirm: it works fine with donor nand. no more freeze.

i have read 1MB with "nandpro.exe nanddump.bin: -r16 nand1mb.bin 0 3E" from my orignand.
then used "inyect1M" to inject nand1mb.bin with autogg in donor nand.

I suggest you put it back.

You've just overwritten your keyvault.

I thought I made this clear on my previous post.

 

[Groxack]

I suggest you put it back.

You've just overwritten your keyvault.

I thought I made this clear on my previous post.

luckily for him the option "inject1m" in autogg ask you for a complete dump to read the first Mg and then inject it into the donated nand.

 

[Martin C]

Yes and where do you think the keyvault is.

the inject1m option is for LPT users who refuse to invest in a proper USB read/write solution. You can dump 1mb of your console and then write XeLL to it, then inject it back over once you have a full dump.

 

[an01523]

luckily for him the option "inject1m" in autogg ask you for a complete dump to read the first Mg and then inject it into the donated nand.

no, autogg have not asked for a complete dump. my separate file nand1mb.bin was accepted.

 

[Martin C]

You're really not understanding the process.

Here - from the readme:

Tutorial to read full Nand by Net reading only 1 Mega by USB/LPT:
If you have a slow nand reader, the reading process can take hours.
There is the possibility of read-only area we need to generate the NandXell and once loaded in console then to read the rest of the Nand by Network
The process is as follows:
1-Press Read nand. Choose Size 1Meg. Save file.
2-Choose image type (Glitch / JTAG) and click Generate NandXell.Once generated write it clicking Flash Xell. If all is ok start the console with network cable
connected and chip installed. you will get the screen Xell
3-When Xell start IP will be assigned to the console and show us on screen. Write it in the IP field of autoGG and press IP-Nand to read and save file.
4-Press Inject 1M and choose the file saved in the first point. Save file.
Now you have the original nand .

So what it's doing is copying the data from the 1MB you originally dumped, overwriting the NAND you dumped (with the first 1MB having XELL written to it).

Prove me wrong - insert a game disc and try to play it.

 

[an01523]

Prove me wrong - insert a game disc and try to play it.

Of course i did this test after flashing donor nand. Playing games on disc is no problem (even backups).

I put first 1MB of original nand in the donor nand. then used the new donor nand, which now has first 1MB of my original nand, to create freeboot nand image.

 

[Martin C]

right, ok. Now I'm understanding what you did!

So you KEPT the 1st MB of your original NAND?

So in which case, it's more than likely the SMC-Config which is the file in question which needs looking at.