I just successfully installed new Corona V4 and thought I might share my experience with others who gets newest Corona into their hands.
Input information:
Model: Brand new Corona V4
MFR: 08/2012
Pre-installed DB: 15574
Components used: All Xecuter's recommended parts, i.e. DGX, X-Clamp removal tool, Postfix adapter, Corona 4GB R/W Kit, CR3 Lite
SW used: J-Runner (in time of writing v0.2 Beta (284)
1. POSTFIX ADAPTER INSTALLATION
First of all I would say that Postfix adapter is easy to install and perfectly fits. Using Xecuter X-clamp removal tool eases the work and I had the heatsink removed in a few seconds. Postfix adapter perfectly fits into the position and alone holds firmly.
However, to make it even securer, I have soldered it into the place using recommended anchors.
I did not bother with thermal compound as it was kept untouched and it did not change its consistency because of whole process lasted maximum of a few minutes.
2. CORONA 4GB R/W QSB INSTALLATION
Since the new QSB for reading/writing 4GB NAND are not yet sold, I used original QSB supplied with Corona 4GB R/W Kit. I had not a single problem to install it, as you can see it fits into the place flawlessly.
I made the three dumps of the NAND using latest version of J-Runner. I would like to note that, unlike Corona V2 that I did before, NAND size of Corona V4 is reported as 3648 MB in J-Runner. I was little worried to continue writing DGX ECC to the NAND as I thought the NAND size should be the same size as for Corona V2, i.e. 3588 MB. Also J-Runner had warned twice that the size of NAND has no expected size and because I have not found nothing related to exact capacity in MB of Corona V4, I was really unsure.
Common sense has won, I had three dumps of NAND, all did match, input information presented correctly in J-Runner (CB/DB version etc.), so I went forward :smile:
3. DGX INSTALLATION
I have installed DGX using Xecuter's recommended wiring and turned ON my Corona. After approx. 15 minutes I had green debug LED on DGX still blinking and no Xell (besides the TV out I used IP scan on my network). What did I notice was that the fan was not ticking in glitch pulses, nothing like on Trinity or Corona V2 that I did before. Even I put my ear very close to the fan I could not hear any ticking. Accustomed to the fact that ticking fan is one of the accompanying events of the glitch I was in doubts of my installation.
From the various tips and hints that I found on this forum I could not even imagine from which end should I start. What I did in the first place (do not ask me why, I call it just a pure luck) was usage of extended wire to post_out, in my case total of 60 cm length (thanks to Screamo and his hint HERE).
What a pleasant surprise when the debug LED on DGX had stopped blinking after the fourth glitch. Not only that I got my CPU KEY using IP scan in J-Runner, but believe or not, I also got Xell on my TV screen!. I could not believe how many joy can blue color of Xell Reloaded bring :smile:
4. CR3 LITE INSTALLATION
I was full of unanswered question like "Should I keep such long post_out wire also for CR3 Lite installation to have it working?", or "What about the DGX ECC written in NAND, will J-Runner take care of that while building the freeboot image?". Well, I used standard lenght of post_out wire, had followed Xecuter's recommended installation diagram and CR3 Lite settings. Since first batch of new Corona V3 QSB did not arrive yet from States (I really do not understand why both MTUK and CK3 do not sell the yet), I had to use wire installation of CR3 Lite.
What I got at the end is flawlessly working Corona V4 RGH, booting at the 3 - 5th cycle :smile:
5. FINISH
Never give up, follow the instructions, listen to voices, read the experiences of other users. Patience brings the roses.
I would like to thank Team Xecuter for their yet another great products (DGX, Postfix adapter) that are easy to install if you just follow instructions. Thanks also goes to J-Runner Team for the best ever RGH application available.
Input information:
Model: Brand new Corona V4
MFR: 08/2012
Pre-installed DB: 15574
Components used: All Xecuter's recommended parts, i.e. DGX, X-Clamp removal tool, Postfix adapter, Corona 4GB R/W Kit, CR3 Lite
SW used: J-Runner (in time of writing v0.2 Beta (284)
1. POSTFIX ADAPTER INSTALLATION
First of all I would say that Postfix adapter is easy to install and perfectly fits. Using Xecuter X-clamp removal tool eases the work and I had the heatsink removed in a few seconds. Postfix adapter perfectly fits into the position and alone holds firmly.
However, to make it even securer, I have soldered it into the place using recommended anchors.
I did not bother with thermal compound as it was kept untouched and it did not change its consistency because of whole process lasted maximum of a few minutes.
2. CORONA 4GB R/W QSB INSTALLATION
Since the new QSB for reading/writing 4GB NAND are not yet sold, I used original QSB supplied with Corona 4GB R/W Kit. I had not a single problem to install it, as you can see it fits into the place flawlessly.
I made the three dumps of the NAND using latest version of J-Runner. I would like to note that, unlike Corona V2 that I did before, NAND size of Corona V4 is reported as 3648 MB in J-Runner. I was little worried to continue writing DGX ECC to the NAND as I thought the NAND size should be the same size as for Corona V2, i.e. 3588 MB. Also J-Runner had warned twice that the size of NAND has no expected size and because I have not found nothing related to exact capacity in MB of Corona V4, I was really unsure.
Common sense has won, I had three dumps of NAND, all did match, input information presented correctly in J-Runner (CB/DB version etc.), so I went forward :smile:
3. DGX INSTALLATION
I have installed DGX using Xecuter's recommended wiring and turned ON my Corona. After approx. 15 minutes I had green debug LED on DGX still blinking and no Xell (besides the TV out I used IP scan on my network). What did I notice was that the fan was not ticking in glitch pulses, nothing like on Trinity or Corona V2 that I did before. Even I put my ear very close to the fan I could not hear any ticking. Accustomed to the fact that ticking fan is one of the accompanying events of the glitch I was in doubts of my installation.
From the various tips and hints that I found on this forum I could not even imagine from which end should I start. What I did in the first place (do not ask me why, I call it just a pure luck) was usage of extended wire to post_out, in my case total of 60 cm length (thanks to Screamo and his hint HERE).
What a pleasant surprise when the debug LED on DGX had stopped blinking after the fourth glitch. Not only that I got my CPU KEY using IP scan in J-Runner, but believe or not, I also got Xell on my TV screen!. I could not believe how many joy can blue color of Xell Reloaded bring :smile:
4. CR3 LITE INSTALLATION
I was full of unanswered question like "Should I keep such long post_out wire also for CR3 Lite installation to have it working?", or "What about the DGX ECC written in NAND, will J-Runner take care of that while building the freeboot image?". Well, I used standard lenght of post_out wire, had followed Xecuter's recommended installation diagram and CR3 Lite settings. Since first batch of new Corona V3 QSB did not arrive yet from States (I really do not understand why both MTUK and CK3 do not sell the yet), I had to use wire installation of CR3 Lite.
What I got at the end is flawlessly working Corona V4 RGH, booting at the 3 - 5th cycle :smile:
5. FINISH
Never give up, follow the instructions, listen to voices, read the experiences of other users. Patience brings the roses.
I would like to thank Team Xecuter for their yet another great products (DGX, Postfix adapter) that are easy to install if you just follow instructions. Thanks also goes to J-Runner Team for the best ever RGH application available.
