TX Product(s) used: Corona 4gb r/w, slim proto v2 and rev c+corona qsb upgrade, post fix adapter v1 and v2
Console Type: Corona v6
NAND size: 4GB
Dashboard version: 2.0.16203
CB version: 13182
Screenshot of NAND details from J-Runner:
updflash.bin log
1)
Thursday, April 17, 2014 12:28:03 AM
J-Runner v0.3 Beta (4) Started
Initializing nanddump1.bin..
Corona 4GB
RGH2 Selected
Nand Initialization Finished
Load Files Initiliazation Finished
Started Creation of the 16547 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image
---------------------------------------------------------------
H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\037599232408\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16547.0
Console : Corona
NAND size : 48MiB MMC (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 037599232408
ConsoleId : 189307472056
MoboSerial: 9590022209103248
Mfg Date : 06/15/2013
CPU Key : AEA8AC9F9CC57215903D0C3FA6D90046
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : AE84015DAD200EE9B170DCE7250CFC09
CF LDV : 1
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\037599232408
Image is Ready
2)
Friday, April 18, 2014 5:08:38 PM
J-Runner v0.3 Beta (4) Started
Corona 4GB Manually Selected
F:\
Reading from F:\ to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Done!
in 0:02 min:sec
F:\
Initializing nanddump1.bin..
Reading from F:\ to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Corona 4GB
RGH2 Selected
Nand Initialization Finished
Done!
in 0:02 min:sec
Comparing...
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Nands are the same
ECC created
Writing to F:\ from H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\output\image_00000000.ecc
Done!
in 0:00:256 min:sec:ms
Initializing nanddump1.bin..
Corona 4GB
Nand Initialization Finished
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Corona 4GB
Nand Initialization Finished
Moving All files from output folder to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\038018132408
Load Files Initiliazation Finished
16547
Started Creation of the 16547 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image
---------------------------------------------------------------
H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\038018132408\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16547.0
Console : Corona
NAND size : 48MiB MMC (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 038018132408
ConsoleId : 361106146660
MoboSerial: 9590022203473248
Mfg Date : 06/15/2013
CPU Key : F2F4E10F6CF064F1570C99F146189B9C
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 0E53BCFB68184D9B62906C4C54CD25C6
CF LDV : 1
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\038018132408
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Description of problem:
I recently came across two corona v6 which needed to be RGH'ed(unfortunately i didnt take the pix before returning to the customer:facepalm
. I have since started using the slim proto v2 but still have a large number of corona qsb upgrade i intend to use. I noticed the reported problem with the v6 mobo( constant whining sound and unresponsive power button) which in some cases could be fixed by removing r1r1 resistor, this worked for the 2 consoles above. However i am curious if this had to do the slim proto because l did a couple of v6's several months back and i dont recall having to resort to this fix. if its of any relevance both consoles above had samsum ram. just need some clarification as my current stock of proto v2 is almost exhausted and i might revert to the qsb upgrades.:facepalm:
Was the console working before you started: Yes
Do you get a green debug light appear on the RGH chip every 4-5 seconds: Yes
How long is the light on for each time: on the proto a flash of green, on the rev C 2-3 secs
Console Type: Corona v6
NAND size: 4GB
Dashboard version: 2.0.16203
CB version: 13182
Screenshot of NAND details from J-Runner:
updflash.bin log
1)
Thursday, April 17, 2014 12:28:03 AM
J-Runner v0.3 Beta (4) Started
Initializing nanddump1.bin..
Corona 4GB
RGH2 Selected
Nand Initialization Finished
Load Files Initiliazation Finished
Started Creation of the 16547 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image
---------------------------------------------------------------
H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\037599232408\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16547.0
Console : Corona
NAND size : 48MiB MMC (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 037599232408
ConsoleId : 189307472056
MoboSerial: 9590022209103248
Mfg Date : 06/15/2013
CPU Key : AEA8AC9F9CC57215903D0C3FA6D90046
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : AE84015DAD200EE9B170DCE7250CFC09
CF LDV : 1
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\037599232408
Image is Ready
2)
Friday, April 18, 2014 5:08:38 PM
J-Runner v0.3 Beta (4) Started
Corona 4GB Manually Selected
F:\
Reading from F:\ to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Done!
in 0:02 min:sec
F:\
Initializing nanddump1.bin..
Reading from F:\ to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\output\nanddump2.bin
Corona 4GB
RGH2 Selected
Nand Initialization Finished
Done!
in 0:02 min:sec
Comparing...
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Nands are the same
ECC created
Writing to F:\ from H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\output\image_00000000.ecc
Done!
in 0:00:256 min:sec:ms
Initializing nanddump1.bin..
Corona 4GB
Nand Initialization Finished
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Corona 4GB
Nand Initialization Finished
Moving All files from output folder to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\038018132408
Load Files Initiliazation Finished
16547
Started Creation of the 16547 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.12.659
---------------------------------------------------------------
base path changed to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image
---------------------------------------------------------------
H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\038018132408\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16547.0
Console : Corona
NAND size : 48MiB MMC (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 038018132408
ConsoleId : 361106146660
MoboSerial: 9590022203473248
Mfg Date : 06/15/2013
CPU Key : F2F4E10F6CF064F1570C99F146189B9C
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 0E53BCFB68184D9B62906C4C54CD25C6
CF LDV : 1
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to H:\CONSOLES AND HANDHELDS\J-Runner v02 Beta (284) Core Pack\038018132408
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Description of problem:
I recently came across two corona v6 which needed to be RGH'ed(unfortunately i didnt take the pix before returning to the customer:facepalm
. I have since started using the slim proto v2 but still have a large number of corona qsb upgrade i intend to use. I noticed the reported problem with the v6 mobo( constant whining sound and unresponsive power button) which in some cases could be fixed by removing r1r1 resistor, this worked for the 2 consoles above. However i am curious if this had to do the slim proto because l did a couple of v6's several months back and i dont recall having to resort to this fix. if its of any relevance both consoles above had samsum ram. just need some clarification as my current stock of proto v2 is almost exhausted and i might revert to the qsb upgrades.:facepalm:Was the console working before you started: Yes
Do you get a green debug light appear on the RGH chip every 4-5 seconds: Yes
How long is the light on for each time: on the proto a flash of green, on the rev C 2-3 secs