R-Jtag and demon won't boot after installing demon

orgino

Junior Member
Jun 9, 2013
22
1
Trondheim, Norway
Console Type: Japser
NAND size: 512
CB version: 6723

When I try to start my xellreloaded image on the r-jtag with the demon I get this from post:

Code:
Version: 10
Power Up
Waiting for POST to change
Post 82 - Panic - DATA_STORAGE 
Post 92 - Panic - 1BL is executed on wrong CPU thread (panic) 
Post F2 - Panic - SHA_VERIFY_CB_B 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
Post 8A - Panic - DECREMENTER 
Post FA 
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 8C - Panic - SYSTEM_CALL 
Post CC 
Post 8C - Panic - SYSTEM_CALL 
Post CC 
Post FC 
Post CC 
Post FC 
Post CC 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post DC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 10 - Payload/1BL started 
Post 12 - FSB_CONFIG_RX_STATE 
Post 15 - FETCH_OFFSET 
Post 16 - FETCH_HEADER 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
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 88 - Panic - PROGRAM 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post CC 
Post 8C - Panic - SYSTEM_CALL 
Post CC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post CC 
Post 8C - Panic - SYSTEM_CALL 
Post CC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post FC 
Post 8C - Panic - SYSTEM_CALL 
Post 15 - FETCH_OFFSET 
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 5A - INIT_XEX_TRAINING 
Post 60 - INIT_KERNEL 
Post 61 - INIT_HAL_PHASE_0 
Post 62 - INIT_PROCESS_OBJECTS 
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 
Shutdown
J-runner:

Code:
===================================================
3. august 2013 15:18:42

J-Runner v0.2 Beta (289) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Filechecks disabled - No Filechecks carried out
Initializing nanddump1.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully jasper_hack_aud_clamp.bin
Current: DemoN
Switching to XBOX
Success
Current: XBOX
Switching to DemoN
Success
DEMON
Hardware   : Demon Phat
Firmware   : 1.4
Flash ID   : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0x1 
Writing Nand
Done!
in 0:02 min:sec
It looks like it boots but the screen is just black.

1.jpg2.jpg3.jpg4.jpg
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com

orgino

Junior Member
Jun 9, 2013
22
1
Trondheim, Norway
Thanks, xell is now booting.

Now I can't seem to have access to my onboard memory.
Tried to find it on the stock nand and the demon nand, no device appeared