what's the settings of xebuild in winbond? shall I choose glitch2m or glitch2 CR4? In patches/dashlaunch, WB4G should be selected right?
Have the cpu key, using cr4 in 360E.
Have the cpu key, using cr4 in 360E.
FIXED winbond xebuild settings in j-runner
- Thread starter WalangAlam
- Start date
BL4K3Y
VIP Member
Select Glitch2 (RGH2) and tick the CR4 check box.
To enable Winbond patches, select "WB" (16MB NAND) or "WB4G" (4GB NAND) under the "Patches/DashLaunch" tab.
To enable Winbond patches, select "WB" (16MB NAND) or "WB4G" (4GB NAND) under the "Patches/DashLaunch" tab.
selected 1-6 dipswitches but green light stop blinking after several blinks then continuous sound from fan . I selected CR4 glitch2 and WB4G. How to fix?
Code:
Saved to C:\J-Runner\035368335108
Image is Ready
Initializing updflash.bin..
Corona 4GB
Glitch2 Selected
Nand Initialization Finished
Writing to F:\ from C:\J-Runner\035368335108\updflash.bin
Done!
in 0:06:291 min:sec:ms
Load Files Initiliazation Finished
16767
Started Creation of the 16767 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.14.693
---------------------------------------------------------------
base path changed to C:\J-Runner\xeBuild
---- { Image Build Mode } ----
building glitch2 image
---------------------------------------------------------------
C:\J-Runner\035368335108\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16767.0
Console : Corona
NAND size : 48MiB MMC (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 035368335108
ConsoleId : 548968455835
MoboSerial: 9870432210413518
Mfg Date : 12/19/2013
CPU Key : 5D5BBF0D1810D0D2BDF2413ADC196C7C
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 10CA9833C421C70EA42BAAF7041DA308
CF LDV : 2
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\J-Runner\035368335108
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Writing to F:\ from C:\J-Runner\035368335108\updflash.bin
Done!
in 0:06:292 min:sec:ms
Last edited:
BL4K3Y
VIP Member
i ticked it and has already check
http://imgur.com/W8yboZA
Code:
CR4 Selected
Load Files Initiliazation Finished
16767
Started Creation of the 16767 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.14.693
---------------------------------------------------------------
base path changed to C:\J-Runner\xeBuild
---- { Image Build Mode } ----
building glitch2 image
---------------------------------------------------------------
C:\J-Runner\035368335108\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16767.0
Console : Corona
NAND size : 48MiB MMC (system only)
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 035368335108
ConsoleId : 548968455835
MoboSerial: 9870432210413518
Mfg Date : 12/19/2013
CPU Key : 5D5BBF0D1810D0D2BDF2413ADC196C7C
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 10CA9833C421C70EA42BAAF7041DA308
CF LDV : 2
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\J-Runner\035368335108
Image is Ready
Initializing updflash.bin..
Corona 4GB
Nand Initialization Finished
Last edited:
BL4K3Y
VIP Member
jligg
VIP Member
BL4K3Y
VIP Member
Good stuff.thanks. Instant boot
I don't think the 16767 INIs contain the correct information for Winbond data which probably explains your issue.