FIXED Falcon Not Booting to Xell or Dash

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
Console Type: Falcon
NAND size: 16
Dashboard version: 2.0.16202
CB version: 5774
AUD_CLAMP: YES
Dip Settings: All default as per guide
Screenshot of NAND details from J-Runner:
nand.jpg
J-Runner log:
Will also update, Nothing unusual but I think the most important were:
Code:
Bad Block ID  01EA Found @ 0x03FF [Offset: 0x107BE00] 
Bad Block ID  01EB Found @ 0x03FE [Offset: 0x1077C00] 
Bad Block ID  0250 Found @ 0x03FD [Offset: 0x1073A00] 
Bad Block ID  0251 Found @ 0x03FC [Offset: 0x106F800] 
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 01EA [Offset: 0x7E5400] 
Block ID 03FE [Offset: 0x1077C00] remapped to Block ID 01EB [Offset: 0x7E9600] 
Block ID 03FD [Offset: 0x1073A00] remapped to Block ID 0250 [Offset: 0x98A000] 
Block ID 03FC [Offset: 0x106F800] remapped to Block ID 0251 [Offset: 0x98E200]
Bad Blocks Remapped
Code:
Couldn't add dashlaunch patches to (Cant rememeber exact directory) ...glitch2m.ini
Code:
******* WARNING: could not patch SMC reset limit!
And something that seemed akward:

Code:
KV type  : type2 (hashed - unchecked, master key not available)
Nand dumps compared fine (4 of them)



POST output from J-Runner (RATER output)
:

Code:
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
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 87 - Panic - ALIGNMENT 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 10 - Payload/1BL started 
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 87 - Panic - ALIGNMENT 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
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 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 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 51 - LOAD_UPDATE_2 
Post 50 - LOAD_UPDATE_1 
Post 52 - BRANCH 
Post 58 - INIT_HYPERVISOR 
Post 5A - INIT_XEX_TRAINING 
Post 61 - INIT_HAL_PHASE_0 
Post 62 - INIT_PROCESS_OBJECTS 
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 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 78 - INIT_STFS_DRIVER 
Post 79 - LOAD_XAM 
Shutdown
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
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 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 41 - VERIFY_OFFSET 
Post 44 - FETCH_CONTENTS 
Post 45 - HMACSHA_COMPUTE 
Post 46 - RC4_INITIALIZE 
Post 47 - RC4_DECRYPT 
Post 48 - SHA_COMPUTE 
Post 49 - SHA_VERIFY 
Post 4B - LZX_EXPAND 
Post 4E - FETCH_OFFSET_6BL_CF 
Post 4F - VERIFY_OFFSET_6BL_CF 
Post 51 - LOAD_UPDATE_2 
Post 50 - LOAD_UPDATE_1 
Post 52 - BRANCH 
Post 58 - INIT_HYPERVISOR 
Post 5A - INIT_XEX_TRAINING 
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 
Shutdown
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
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 30 - VERIFY_OFFSET_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post FC 
Post 38 - SIG_VERIFY_4BL_CD 
Post FC 
Post 7C 
Post 7C 
Post 08 
Post 7C 
Post FC 
Post 10 - Payload/1BL started 
Post 12 - FSB_CONFIG_RX_STATE 
Post 13 - FSB_CONFIG_TX_STATE 
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 87 - Panic - ALIGNMENT 
Post 78 - INIT_STFS_DRIVER 
Post 38 - SIG_VERIFY_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7E 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 7C 
Post 7C 
Post 7C 
Post 7C 
Post 7C 
Post 10 - Payload/1BL started 
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 2F - RELOCATE 
Post 2E - HWINIT 
Post 38 - SIG_VERIFY_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 7C 
Post FC 
Post 7C 
Post 7C 
Post 48 - SHA_COMPUTE 
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 2F - RELOCATE 
Post 2E - HWINIT 
Post 31 - FETCH_HEADER_4BL_CD 
Post 33 - FETCH_CONTENTS_4BL_CD 
Post 35 - RC4_INITIALIZE_4BL_CD 
Post 36 - RC4_DECRYPT_4BL_CD 
Post 37 - SHA_COMPUTE_4BL_CD 
Post 39 - SHA_VERIFY_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 51 - LOAD_UPDATE_2 
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 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 76 - INIT_SYSTEM_ROOT 
Post 77 - INIT_OTHER_DRIVERS 
Post 78 - INIT_STFS_DRIVER 
Post 79 - LOAD_XAM 
Shutdown
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
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 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 51 - LOAD_UPDATE_2 
Post 50 - LOAD_UPDATE_1 
Post 52 - BRANCH 
Post 58 - INIT_HYPERVISOR 
Post 59 - INIT_SOC_MMIO 
Post 5A - INIT_XEX_TRAINING 
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 76 - INIT_SYSTEM_ROOT 
Post 77 - INIT_OTHER_DRIVERS 
Post 78 - INIT_STFS_DRIVER 
Post 79 - LOAD_XAM 
Shutdown
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
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 87 - Panic - ALIGNMENT 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 58 - INIT_HYPERVISOR 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post FC 
Post 7C 
Post 7C 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
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 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 51 - LOAD_UPDATE_2 
Post 50 - LOAD_UPDATE_1 
Post 52 - BRANCH 
Post 58 - INIT_HYPERVISOR 
Post 5A - INIT_XEX_TRAINING 
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 72 - INIT_BOOT_ANIMATION + XMADecoder & XAudioRender Init 
Post 73 - INIT_SATA_DRIVER 
Post 77 - INIT_OTHER_DRIVERS 
Post 78 - INIT_STFS_DRIVER 
Post 79 - LOAD_XAM 
Shutdown

[B]Glitch Info:[/B]
1, 1, 2, 1, 1, 
[B]
Score:[/B]
Overall: 5 / 10
Average: 1,20
Median: 1
Score: 9,60

Cycle 1 - 40,00%
Cycle 2 - 10,00%

100% within 2 Cycles

updflash.bin log (if applicable)
:n/a

Image of R-JTAG board
:
R-JTAG (Before Reinstall).jpg
This was the previous install, the last install I only made the connections look a bit better.

Images of close-up soldering to motherboard
:
JTAG Alt.jpgNand-X.jpgPost QSB.jpgPost QSB Closeup.jpgQSB.jpgCPU_RST.jpg
- I did clean the JTAG Alt soldering points after the photo was taken

Description of problem:
The console booted Xell the very first time and I was able to get the CPU key. Now its not booting to Xell, or with the Eject Button, and neither to the dashboard. When JRP V2 and Post QSB Ribbon is connected, it Posts until 79 (as above) with Single Red light (bottom left). Without these it just keeps on glitching (you can hear by the quick and sudden change of fan speed) and not booting.

Steps taken to possibly resolve:
- I recheked all of my soldering, and tested continuity on each and every point, including the PCB's themselves. If found all had continuity and NO bridged connections.

- Flashed back to Stock Nand with everything connected, boots like a normal Xbox

- De-soldered, removed and reinstalled the whole kit, no difference

- Tried without AUD_CLAMP, Tried CPU_RST point on bottom, Changed Voltages, Numerous dip settings, 3-way switch at JTAG Alt. (Might be more, spend more than 30 hours on it) Found the default settings to render a more "stable result"

- Flashed dash to 16537, it changed the CB version to 5770, but with exact same POST results.


Was the console working before you started: Yes
 
Last edited:

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
Why did you select glitch2m? At no point did you say that to me.

write the xell bin back to the console and try booting again.
Hi Martin,

My Apologies. IRC on my side disconnected and I couldnt reconnect. I see no option for selecting glitch2m, as I understand this is not intended for this console, but, the dashlaunch patches are exactly the same as the normal glitch2. I created a blank .ini and it wrote the following:

Code:
..\launch.xex
..\lhelper.xex
..\launch.ini
I did write the Xell bin back with same results.

Updating my post and pics now
 

Martin C

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

My Apologies. IRC on my side disconnected and I couldnt reconnect. I see no option for selecting glitch2m, as I understand this is not intended for this console, but, the dashlaunch patches are exactly the same as the normal glitch2. I created a blank .ini and it wrote the following:

Code:
..\launch.xex
..\lhelper.xex
..\launch.ini
I did write the Xell bin back with same results.

Updating my post and pics now
Why are you messing with ini files????


Couldn't add dashlaunch patches to (Cant rememeber exact directory) ...glitch2m.ini


You got this because at some point you selected glitch2m. No-one advised you to.
 

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
There was no glitch2m.ini to write to, so I wanted to see what info it writes in comparison with the normal glitch2.ini. I did not modify any data.

If you can refer me to the option to select glitch2m in J-Runner, I will be able to tell you if I did check it or not, but thusfar I have no clue regarding selection of such file
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Ok. Just to confirm, boot to Xell with eject button? Can I boot the console with the JRP and POST ribbon connected?
Again, nowhere does it say you need to boot to xell with the eject button.

You can use power OR eject. You need the POST ribbon connected for the exploit to work.
 

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
Again, nowhere does it say you need to boot to xell with the eject button.
Yes, I did not see it anywhere, except in J-Runner. My first and only Xell boot was with power button

You need the POST ribbon connected for the exploit to work.
Thanks, not sure if I have enough time, otherwise will post results after work.

UPDATE: Not booting. 2 by glitch, few moments of green light flicker, then one red light.

Tried RATER:
Code:
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
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 87 - Panic - ALIGNMENT 
Post 70 - INIT_VIDEO_DRIVER 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post F8 
Post 78 - INIT_STFS_DRIVER 
Post FC 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
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 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post FE 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 38 - SIG_VERIFY_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
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 70 - INIT_VIDEO_DRIVER 
Post 70 - INIT_VIDEO_DRIVER 
Post 10 - Payload/1BL started 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
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 30 - VERIFY_OFFSET_4BL_CD 
Post 70 - INIT_VIDEO_DRIVER 
Post 70 - INIT_VIDEO_DRIVER 
Post 70 - INIT_VIDEO_DRIVER 
Post 30 - VERIFY_OFFSET_4BL_CD 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 7C 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 10 - Payload/1BL started 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 3D 
Post 01 
Post 70 - INIT_VIDEO_DRIVER 
Post 70 - INIT_VIDEO_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 7C 
Post 7C 
Post 7C 
Post 78 - INIT_STFS_DRIVER
TIMEOUT or SMC CORRUPTED - Shutting Down
Single Red light.

Second Try:
Code:
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 10 - Payload/1BL started 
Post 16 - FETCH_HEADER 
Post 78 - INIT_STFS_DRIVER 
Post 12 - FSB_CONFIG_RX_STATE 
Post 13 - FSB_CONFIG_TX_STATE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 05 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post 01 
Post 7D 
Post FD 
Post 01 
Post 7D 
Post 01 
Post 01 
Post 03 
Post 06 
Post 0C 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Post 78 - INIT_STFS_DRIVER 
Shutdown
3 red lights...
 
Last edited:

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Those postout vaules are look wrong. try writing back stock nand, and disconnect 5v from r-jtag. make sure it still boots with stock. if not there is a serious problem. If it does boot go over postout again.
 

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
Those postout vaules are look wrong. try writing back stock nand, and disconnect 5v from r-jtag. make sure it still boots with stock. if not there is a serious problem. If it does boot go over postout again.
I flashed back to stock, can boot without disconnecting 5v wire.. Is this a problem?

when you get the one red light, report the secondary error code please.
That would be 1033 which would mean e79, same as where the post stops, and explanation as follow (which I could find):
"E79: Dashboard Error - Couldn't start xam.xex: probably a file system corruption, it could also be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it."
 

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
Ok. Not sure if the 1.5k is correct or not. If not, what should it be?

I rechecked my wiring, and resoldered/reflowed the connections on the JTAG qsb, but made no difference.

I found 2 threads with the exact problem on the same box.

In one scenario a connection on the JTAG qsb did not make contact after installation. On my side the qsb's are securely mounted. The other one was a bit more interesting though:

Something was wrong with the pc running JRunner, so the guy could not boot using AUD_CLAMP with pins 1-3 connected, but it did boot with 1-2 connected. After he flashed from a different pc he managed to get it booting on 1-3.

Im off to installing a 32 bit Windows on a new pc to see if it makes a difference.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
it's not a windows issue. 1.5k for both is fine.

Next check every POST 'pad' on your POST_OUT QSB against GND - set the meter to 200k. Each should give you a fairly high value. More importantly, they should all be around the same. Again, no need for a PSU connection.
 

01DawG10

Full Member
Oct 31, 2013
72
8
Rural Area, South Africa
it's not a windows issue. 1.5k for both is fine.

Next check every POST 'pad' on your POST_OUT QSB against GND - set the meter to 200k. Each should give you a fairly high value. More importantly, they should all be around the same. Again, no need for a PSU connection.
Thanks Martin, results as follow:
0 - 12.3k
1 - 12k
2 - 12k
3 - 12.4k
4 - 12.4k
5 - 12.4k
6 - 12.3k
7 - 12.2k

1 and 2 seems a bit down.. Need I check soldering on those points?
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
No, not at all. They would either be N/C or wildly out if they were a problem.

Just to confirm that you're still trying to boot a xell bin and NOT a created image?