FIXED Falcon Not Booting to Xell or Dash

[01DawG10]

No, not at all. They would either be N/C or wildly out if they were a problem.

Thank you, thats good to know.

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

That is correct yes.

 

[Martin C]

Have you tried booting from DIPs 1 to 6, with all three power options (so 18 configurations)

For any that get past 21 in the POST output, paste onto pastebin and put the link in this thread.

 

[01DawG10]

Have you tried booting from DIPs 1 to 6, with all three power options (so 18 configurations)

Yes, I have. As far as I remember other than normal glitched awkwardly. But please see below.

For any that get past 21 in the POST output, paste onto pastebin and put the link in this thread.

Ok, I'll run and log each setting. How many cycles would you suggest?

 

[Martin C]

5 cycles for each should be more than enough.

 

[01DawG10]

Ok. Im almost done compiling the lists and thusfar its not looking good.. I hope this would not be irrelevant, but just to teach myself: 3 quick questions about efuses (Yes, I know, but the whole idea is soooo confusing)..

1. Does flashing the Xell-Reloaded blow an efuse (Apparently, updating the bootloader does)
2. Does flashing a nand image, irrespective of original or hacked, blow an efuse? (My assumption would be no)
3. Does any part of the J-TAG install/flash/dash change process blow any efuses?

 

[01DawG10]

Ok.. This is going to be a looooooooong post.. Will modify if needed. I used the following template for boots 1 to 18:

Boot No (and link to pastebin) - DIP settings 1 to 8 (1 for on 0 for off) - Voltage setting (Def, 1.2, 1.8)
No of Cycles
Cycles to glitch per cycle
Cycle 1 last post before Error or Shutdown
Cycle 2 last post before Error or Shutdown
Cycle 3 last post before Error or Shutdown
Cycle 4 last post before Error or Shutdown
No of Red Lights (if Applicable)

If all cycles ended the same, only 1 description.

 

[01DawG10]

Boot 1 - DIP 10000010 DEFAULT
4 Cycles
Glitch 2 3 2 3
Post 78 - INIT_STFS_DRIVER
Post 78 - INIT_STFS_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 78 - INIT_STFS_DRIVER
Most Fails(cumulative): 0xA0
3 Red Lights

Boot 2 - DIP 01000010 DEFAULT
4 Cycles
Glitch 1 3 3 3
Post 78 - INIT_STFS_DRIVER
Post 78 - INIT_STFS_DRIVER
Post 78 - INIT_STFS_DRIVER
Post 78 - INIT_STFS_DRIVER
Most Fails(cumulative): 0xA0
3 Red Lights

Boot 3 - DIP 00100010 DEFAULT
4 Cycles
Glitch 3 3 3 2
Post 30 - VERIFY_OFFSET_4BL_CD
Post 78 - INIT_STFS_DRIVER
Post 01
Post 78 - INIT_STFS_DRIVER
Most Fails(cumulative): 0xA0
3 Red Lights

Boot 4 - DIP 00010010 DEFAULT
4 Cycles
Glitch 1 1 4 1
Post 79 - LOAD_XAM
Post 79 - LOAD_XAM
Post 73 - INIT_SATA_DRIVER
Post 73 - INIT_SATA_DRIVER
1 Red Light

Boot 5 - DIP 00001010 DEFAULT
4 Cycles
Glitch 1 2 1 2
Post 79 - LOAD_XAM
Post 73 - INIT_SATA_DRIVER
Post 73 - INIT_SATA_DRIVER
Post 79 - LOAD_XAM
Most Fails(cumulative): 0xA0
1 Red Light

Boot 6 - DIP 00000110 DEFAULT
4 Cycles
Glitch 3 2 3 4
Post 78 - INIT_STFS_DRIVER
Post 7C
Post 78 - INIT_STFS_DRIVER
Post 78 - INIT_STFS_DRIVER
Most Fails(cumulative): 0xA0
3 Red Lights

Boot 7 - DIP 10000010 1.2V
4 Cycles
Glitch 5 5 4 5
Post 22 - INIT_SECENG
Most Fails(cumulative): 0x22
3 Red Lights

Boot 8 - DIP 01000010 1.2V
4 Cycles
Glitch 5+ 4 5+ 5+
Not Sure, but not close to 79
Most Fails(cumulative): 0xA0

Boot 9 - DIP 00100010 1.2V
4 Cycles
Glitch 5 5 2 5
Not Sure. 21 average, few 87 Panic's

Boot 10 - DIP 00010010 1.2V
4 Cycles
Glitch 1 1 1 1
Post 79 - LOAD_XAM
Post 73 - INIT_SATA_DRIVER
Post 73 - INIT_SATA_DRIVER
Post 79 - LOAD_XAM

Boot 11 - DIP 00001010 1.2V
4 Cycles
Glitch 1 3 1
Post 79 - LOAD_XAM
Post 79 - LOAD_XAM
Post 79 - LOAD_XAM
Post 79 - LOAD_XAM
Most Fails(cumulative): 0x22
Most Fails(cumulative): 0xA0
1 Red Light

Boot 12 - DIP 00000110 1.2V (did not save output :facepalm:, will re-run if needed)
4 Cycles
Glitch 5+ 5+ 5+ 5+
Post A0 - Panic - VERIFY_SECOTP_6
Post A0 - Panic - VERIFY_SECOTP_6
Post A0 - Panic - VERIFY_SECOTP_6
Post A0 - Panic - VERIFY_SECOTP_6

Boot 13 - DIP 10000010 1.8V
4 Cycles
Glitch 3 3 3 4
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
3 Red Lights

Boot 14 - DIP 01000010 1.8V
4 Cycles
Glitch 5 5 5 4
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010

Boot 15 - DIP 00100010 1.8V
4 Cycles
Glitch 3 5 3 4
Post 30 - VERIFY_OFFSET_4BL_CD
Post 20 - CB entry point reached and err 0010
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
3 Red Lights

Boot 16 - DIP 00010010 1.8V
4 Cycles
Glitch 1 1 1 1
Post 79 - LOAD_XAM
Post 73 - INIT_SATA_DRIVER
Post 73 - INIT_SATA_DRIVER
Post 73 - INIT_SATA_DRIVER
1 Red Light

Boot 17 - DIP 00001010 1.8V
4 Cycles
Glitch 2 1 3 1
Post 73 - INIT_SATA_DRIVER
Post 73 - INIT_SATA_DRIVER
Post 79 - LOAD_XAM
Post 73 - INIT_SATA_DRIVER
1 Red Light

Boot 18 - DIP 00000110 1.8V
4 Cycles
Glitch 5 5 4 4
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then 2 x Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then Post 30 - VERIFY_OFFSET_4BL_CD and err 0010
Post 70 - INIT_VIDEO_DRIVER then 2 x Post 30 - VERIFY_OFFSET_4BL_CD and err 0010

 

[01DawG10]

UPDATE:

Ok.. I have also tried all the settings on the JTAG QSB using a "stable" setting (1.2v, Dips 4 and 7), I also tried these settings without AUD_CLAMP, but no cigar.. Still getting Post 79 - LOAD_XAM, error 1033.

Just for incase, I tested the resistance on the POST Ribbon at the R-JTAG side, and they are not of problem.

 

[Martin C]

You're persistently getting E79, so as recommended your JTAG wiring needs attention.

 

[01DawG10]

You're persistently getting E79, so as recommended your JTAG wiring needs attention.

Thanks. I got it to boot everytime to Xell, but as yet no boot to dash. Not posting past Post 72 - INIT_BOOT_ANIMATION + XMADecoder & XAudioRender Init. Not sure if this is a DIP setting though, as I ran quite a few different ones with 72 being the furthest.

The problem was quite strange. I remove the JTAG and moved it to the top, soldered a header to J2D2, and connected Q2N1, R2P12 and the other little connection to a 3 pin connector. With this process, it seemed that I damaged R2P12 as it would not post with ROL attached, replaced it with a 10k smd and still it would not boot.

After reading of many many many threads I came across a post from TheGlow, and tested the QSB with his sketches. Turned out, the pads (both top and bottom) connecting to J2D2.4 had no connection to the 3 way switch. This was awkward as the pads were in the same good condition as the rest. Anyways, I soldered the wire directly to the connecting point and found myself watching a blue screen with my fusesets.

I rebooted the console 6 times and every time was about "instaboot" (a few seconds, maybe 2 or 3 before green ROL).

Just now, no dash yet... Next quest.

Thanks for your "recommendation". PS, if you have an opinion for me regarding POST 72, please shout, otherwise, off to dippin and voltin for me.

PPS. A pic for interest sake (Yeah, I know, low quality. Camera was on VGA for some reason :/ )

 

[Taijigamer2]

If you're booting to xell instaboot every time then don't mess with dips and volts. There must be something wrong with the NAND image or jtag wiring.

 

[Martin C]

If you're booting to xell instaboot every time then don't mess with dips and volts. There must be something wrong with the NAND image or jtag wiring.

Not even JTAG wiring.

The same exploit to boot xell is used to boot dash.

I'd get to a point where you're booting xell every time. If that's all good, you may need to edit your SMC Config - there's an 'RGH2 Falcon freezing' thread which states acceptable SMC POWER/VCS options. Hopefully this will sort the issue for you.

 

[01DawG10]

If you're booting to xell instaboot every time then don't mess with dips and volts. There must be something wrong with the NAND image or jtag wiring.

Thanks.. I really dont want to be rude, or over enthusiastic, but right now, I strongly doubt that the JTAG wiring is of problem. I've checked every connection over and over and measured resistance and continuity all over the place, so much I actually feel the ohms when I close my eyes. I ensured I have no cold soldering or bridges or disconnections...

But the image, makes me wonder yes..

 

[01DawG10]

Not even JTAG wiring.

The same exploit to boot xell is used to boot dash.

I'd get to a point where you're booting xell every time. If that's all good, you may need to edit your SMC Config - there's an 'RGH2 Falcon freezing' thread which states acceptable SMC POWER/VCS options. Hopefully this will sort the issue for you.

Ah, we replied at the same time, did not see you there Mr Martin.

I'll check about 10 times or so for Xell boot?

Yeah, I have received a "******* WARNING: could not patch SMC reset limit!" every time I created an image.. Will check that side..

 

[Taijigamer2]

I was doubtful it was your wiring as you were successfully booting xell But Your NAND image definately needs looking at.

 

[01DawG10]

Thanks again. If I heard "check your wiring" one more time I swear I would develop a wireless hack... Anyhow. I will report my results, if permission is granted to me for doing that.

I could not read this anywhere though: If I manage to boot to the dash, need the POST ribbon be connected or not? I know MartinC said it must be connected for the exploit to work, but round 'bout that time we were discussing Xell Booting..

 

[Martin C]

The SMC reset thing isn't an issue.

Read from here onwards:

http://team-xecuter.com/forums/showthread.php?t=95054&page=7

 

[01DawG10]

The SMC reset thing isn't an issue.

Read from here onwards:

http://team-xecuter.com/forums/showthread.php?t=95054&page=7

Whoops.. Following wrong thread :facepalm:

This guys said:
"Open J-Runner -> load your updflash.bin in the load source section -> cpu key should be loaded automatically -> click on tools and then smc config editor -> click on Edit config located at the bottom left -> change your Power mode value -> diminish the value by 100(if your initial value is 8080 then augment the value by 100) then hit save config -> J-Runner will create a new image called updflash_edited.bin -> flash this image to your nand and test"

So the above I should not try?

EDIT:
Decreased my Power Mode Value by 100 to 8180, currently on 5th successful boot, 14 seconds after green light on to green ring. Last one was 6 seconds.

But I do notice the following difference in post:
Post 81 - Panic - MACHINE_CHECK
Post C1 - LZX_EXPAND_1

Anything I should stress about?

EDIT2:
Darn its fast , rater log if needed:

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 80
Post 80
Post 80
Post 80
Post 80
Post 80
Post 80
Post 80
Post 80
Post 80
Post 80
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 A0 - Panic - VERIFY_SECOTP_6
Post 80
Post C1 - LZX_EXPAND_1
Post 81 - Panic - MACHINE_CHECK
Post 01
Post 81 - Panic - MACHINE_CHECK
Post C1 - LZX_EXPAND_1
Post 01
Post C1 - LZX_EXPAND_1
Post 01
Post 81 - Panic - MACHINE_CHECK
Post C1 - LZX_EXPAND_1
Post 81 - Panic - MACHINE_CHECK
Post C1 - LZX_EXPAND_1
Post 01
Post 81 - Panic - MACHINE_CHECK
Post 10 - Payload/1BL started
Post 15 - FETCH_OFFSET
Post 16 - FETCH_HEADER
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 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 5B - INIT_KEYRING
Post 5A - INIT_XEX_TRAINING
Post 61 - INIT_HAL_PHASE_0
Post 62 - INIT_PROCESS_OBJECTS
Post 64 - INIT_MEMORY_MANAGER
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 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
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 16 - FETCH_HEADER
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 23 - INIT_SYSRAM
Post 31 - FETCH_HEADER_4BL_CD
Post 33 - FETCH_CONTENTS_4BL_CD
Post 44 - FETCH_CONTENTS
Post 45 - HMACSHA_COMPUTE
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 52 - BRANCH
Post 59 - INIT_SOC_MMIO
Post 5A - INIT_XEX_TRAINING
Post 5B - INIT_KEYRING
Post 5C - INIT_KEYS
Post 5F
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 6C - INIT_SECURITY
Post 6D - INIT_KEY_EX_VAULT
Post 6F - INIT_POWER_MODE
Post 70 - INIT_VIDEO_DRIVER
Post 72 - INIT_BOOT_ANIMATION + XMADecoder & XAudioRender Init
Post 73 - INIT_SATA_DRIVER
Post 75 - INIT_DUMP_SYSTEM
Post 77 - INIT_OTHER_DRIVERS
Post 78 - INIT_STFS_DRIVER
Post 79 - LOAD_XAM

And just now I got Most Fails(cumulative): 0xA0 although it booted fine?

 

[Martin C]

If you're now booting to dash, test it for stability. You may still need to tweak the power settings.

Looking better though!

 

[01DawG10]

If you're now booting to dash, test it for stability. You may still need to tweak the power settings.

Looking better though!

Thanks Martin! And everybody else for their input.

As said, 16202 ran perfectly every time, glitching 1 1 1 1 1... Updated the dash to 16537, had to reduce my Power Mode to 8080.

Its seems to be running ok now, instaboot every few times, glitching either 1 2 or 0, but the stability seems too much of an issue for me.. Not close to the 16202.. Hmmm.. Wonder why. I also noticed that it might be running hotter as the fan speed increases quite a bit just in RATER. Any way to monitor the temps to see if it is in range?

If the problem persists, I'll flash back to 16202. Dont have too many games and not too interested in the newest games (Still a PC fan )

As said a thousand times, thank thou

EDIT: While RATERing, just had glitch 0 with the following repeating:

Post 81 - Panic - MACHINE_CHECK 
Post C1 - LZX_EXPAND_1 
Post 01 
Post 01 
Post C1 - LZX_EXPAND_1 
Post 01 
Post C1 - LZX_EXPAND_1 
Post 01 
Post C1 - LZX_EXPAND_1 
Post 01 
Post 81 - Panic - MACHINE_CHECK 
Post 81 - Panic - MACHINE_CHECK 
Post C1 - LZX_EXPAND_1

Then let it cool for 3 min, next boot did the same and all of a sudden HUGE fan speed, 2 lights barely came on and I switched it off.. This thing is scaring me now

EDIT2:

Hell with that, flashed back 16202, enjoying instaboot and stability until further notice.

My problem(s) has been solved, and MartinC has been quite generous as to me somewhat going off topic.

Take good care and hope this has helped somebody as much as it did me.

Adios!