Console Type: Jasper
NAND size: 16
Dashboard version: 2.0.16203
CB version: 6754
Screenshot of NAND details from J-Runner: 52ec14149bb74495c0478a136adec36f.png
J-Runner log:
Monday, May 27, 2013 5:22:49 PM
J-Runner v0.2 Beta (288) Started
WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Checking Files
Version: 03
Flash Config: 0x00023010
CB Version: 6754
Finished Checking Files
Reading Nand to C:\Documents and Settings\Administrator\Desktop\J-Runner v02 Beta (287) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 2:23 min:sec
Reading Nand to C:\Documents and Settings\Administrator\Desktop\J-Runner v02 Beta (287) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Nand Initialization Finished
Done!
in 2:22 min:sec
Comparing...
Nands are the same
XeLL file created Successfully jasper_hack_aud_clamp.bin
Version: 03
Flash Config: 0x00023010
Writing Nand
jasper_hack_aud_clamp.bin
Done!
in 0:11 min:sec
POST output from J-Runner:
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Description of problem: Using the Jtag xell reloaded, before the update i recieved today, the console usually boots, within 2-3 cycles, i havnt dont much optimisation really just left it at defaults.
or at least i assume its booting, as i am getting 1033, looking up this rrod seems to be harddrive and occasionally JTAG related. I touched up all the points on the JTAG qsb really, thats all ive done i dont know how to go about fixing this problem, as i assume my glitch settings on the console are ok for the time being since it gets this far ? maybe im wrong (im talking about the dips and jumpers here)
Got the new J-Runner update today, and flashed the nand again with xell but this time with r-jtag ticked, still 1033. Any ideas ?
Was the console working before you started: YES
Edit : While i was righting this post, i accidentally left RATER on, im getting relatively good results (2,4,2,2,2), but rater thinks the console is booting when really its getting 1033
NAND size: 16
Dashboard version: 2.0.16203
CB version: 6754
Screenshot of NAND details from J-Runner: 52ec14149bb74495c0478a136adec36f.png
J-Runner log:
Monday, May 27, 2013 5:22:49 PM
J-Runner v0.2 Beta (288) Started
WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button
Checking Files
Version: 03
Flash Config: 0x00023010
CB Version: 6754
Finished Checking Files
Reading Nand to C:\Documents and Settings\Administrator\Desktop\J-Runner v02 Beta (287) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 2:23 min:sec
Reading Nand to C:\Documents and Settings\Administrator\Desktop\J-Runner v02 Beta (287) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Nand Initialization Finished
Done!
in 2:22 min:sec
Comparing...
Nands are the same
XeLL file created Successfully jasper_hack_aud_clamp.bin
Version: 03
Flash Config: 0x00023010
Writing Nand
jasper_hack_aud_clamp.bin
Done!
in 0:11 min:sec
POST output from J-Runner:
Code:
Post A0 - Panic - VERIFY_SECOTP_6
Post 70 - INIT_VIDEO_DRIVER
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 13 - FSB_CONFIG_TX_STATE
Post 14 - FSB_CONFIG_TX_CREDITS
Post 15 - FETCH_OFFSET
Post 16 - FETCH_HEADER
Post 17 - VERIFY_HEADER
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post 1E - BRANCH
Post 20 - CB entry point reached
Post 21 - INIT_SECOTP
Post 22 - INIT_SECENG
Post 70 - INIT_VIDEO_DRIVER
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 13 - FSB_CONFIG_TX_STATE
Post 14 - FSB_CONFIG_TX_CREDITS
Post 15 - FETCH_OFFSET
Post 16 - FETCH_HEADER
Post 17 - VERIFY_HEADER
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 1B - RC4_DECRYPT
Post 1C - SHA_COMPUTE
Post 1D - SIG_VERIFY
Post 1E - BRANCH
Post 20 - CB entry point reached
Post 21 - INIT_SECOTP
Post 22 - INIT_SECENG
Post 2F - RELOCATE
Post 2E - HWINIT
Post 31 - FETCH_HEADER_4BL_CD
Post 33 - FETCH_CONTENTS_4BL_CD
Post 34 - HMACSHA_COMPUTE_4BL_CD
Post 35 - RC4_INITIALIZE_4BL_CD
Post 36 - RC4_DECRYPT_4BL_CD
Post 37 - SHA_COMPUTE_4BL_CD
Post 3A - BRANCH
Post 40 - Entrypoint of CD reached
Post 42 - FETCH_HEADER
Post 44 - FETCH_CONTENTS
Post 45 - HMACSHA_COMPUTE
Post 46 - RC4_INITIALIZE
Post 47 - RC4_DECRYPT
Post 48 - SHA_COMPUTE
Post 4B - LZX_EXPAND
Post 4E - FETCH_OFFSET_6BL_CF
Post 4F - VERIFY_OFFSET_6BL_CF
Post 50 - LOAD_UPDATE_1
Post 52 - BRANCH
Post 58 - INIT_HYPERVISOR
Post 59 - INIT_SOC_MMIO
Post 5A - INIT_XEX_TRAINING
Post 60 - INIT_KERNEL
Post 61 - INIT_HAL_PHASE_0
Post 63 - INIT_KERNEL_DEBUGGER
Post 64 - INIT_MEMORY_MANAGER
Post 65 - INIT_STACKS
Post 66 - INIT_OBJECT_SYSTEM
Post 67 - INIT_PHASE1_THREAD
Post 68 - Started phase 1 Initialization + INIT_PROCESSORS
Post 69 - INIT_KEY_VAULT
Post 6A - INIT_HAL_PHASE_1
Post 6B - INIT_SFC_DRIVER
Post 6C - INIT_SECURITY
Post 6D - INIT_KEY_EX_VAULT
Post 6E - INIT_SETTINGS
Post 6F - INIT_POWER_MODE
Post 70 - INIT_VIDEO_DRIVER
Post 71 - INIT_AUDIO_DRIVER
Post 73 - INIT_SATA_DRIVER
Post 75 - INIT_DUMP_SYSTEM
Post 77 - INIT_OTHER_DRIVERS
Post 79 - LOAD_XAM
Description of problem: Using the Jtag xell reloaded, before the update i recieved today, the console usually boots, within 2-3 cycles, i havnt dont much optimisation really just left it at defaults.
or at least i assume its booting, as i am getting 1033, looking up this rrod seems to be harddrive and occasionally JTAG related. I touched up all the points on the JTAG qsb really, thats all ive done i dont know how to go about fixing this problem, as i assume my glitch settings on the console are ok for the time being since it gets this far ? maybe im wrong (im talking about the dips and jumpers here)
Got the new J-Runner update today, and flashed the nand again with xell but this time with r-jtag ticked, still 1033. Any ideas ?
Was the console working before you started: YES
Edit : While i was righting this post, i accidentally left RATER on, im getting relatively good results (2,4,2,2,2), but rater thinks the console is booting when really its getting 1033