Everything is almost ready. The new Gtuner software is looking fantastic - all the plugins are now in testing and the website is almost done.

Here's a peak at the Gtuner app

Dose anyone have a white fat xbox 360 window modded case for sale?

TX Product(s) used: CR3 Lite, DemoN
Console Type: Trinity
NAND size: 16
Dashboard version: 12625/16537
CB version: 9188
Was the console working before you started: Y

I had my xbox operating no problem from either NAND, and then about a month later it completely quit powering on. It would make the noise, but no fan rotation or anything.

As you can see in the picture, I had to attach a 33 ohm resistor due to damaging R3B15, but this has not been an issue so far.

I have since de-soldered and re-soldered every connection at least twice, including fully removing the Demon from the board and re-attaching it, also twice.

The xbox boots properly when the Demon and CR3-Lite are removed.

I can read both NAND’s still. I have tried reprogramming the CR3-Lite.

There is no continuity between any of the pads on the Demon. All the wires have continuity from one end to another. The 33 ohm resistor I soldered in measures properly from the CR3-Lite to the other side of the R3B15 resistor (that I broke). If there are any other points anyone recommends I check, I’m open to that.

Now when I turn it on, the fan spins up briefly, then the front light turns red and the fan spins down. If I press the power button enough times, the front light starts blinking at 2hz?, but the RBG light never comes on.

IMG_0638.jpgIMG_0639.jpgIMG_0640.jpgIMG_0641.jpgIMG_0642.jpgIMG_0643.jpgIMG_0644.jpgIMG_0645.jpgIMG_0646.jpgIMG_0647.jpgIMG_0648.jpg

Attached Images

• IMG_0639.jpg (262.5 KB)
• IMG_0638.jpg (277.0 KB)
• IMG_0640.jpg (254.9 KB)
• IMG_0641.jpg (232.2 KB)
• IMG_0642.jpg (255.3 KB)
• IMG_0643.jpg (254.1 KB)
• IMG_0644.jpg (261.6 KB)
• IMG_0645.jpg (204.9 KB)
• IMG_0646.jpg (154.6 KB)
• IMG_0647.jpg (220.1 KB)
• IMG_0648.jpg (209.0 KB)

Hey,

So I purchased the CR3 PRO Starter kit expecting it to be an extremely simple install and be booting fairly reliably with little to no tweaking necessary. But that's not the case AT ALL. I can't even get a SINGLE boot to xell out of this thing. And from what I can tell it's glitching, but how can you really know for sure without RATER? No matter how you wire the CR3 the green light STILL blinks. Even if I disconnect the CPU_RST and K wires the light STILL blinks. So it's impossible to know if it's REALLY glitching.

Also the CR3 PRO installation guide seems to have up and disappeared and all that exists is the corona v3/v4 guide which is useless to me since I'm doing a trinity. Also is the STBY_CLK point no longer used on trinity boards with a CR3 PRO? All the pictures I see of installs done with the QSB from the ultimate kit show the STBY_CLK point being soldered to on the QSB, whereas pics of wire installs show that just the Kiosk point is used. Regardless I can't get this thing booting at all and I've done many trinitys with Rev.C's and gotten them to boot and glitch with even the shittiest quick solder job done to them and yet the CR3 has been going for over 30 minutes now with no boots just sits there blinking every few seconds.

I've started with the standard setup most people seem to be going with (10cm CPU_RST to point 22 on POST_QSB, LONG Ribbon cable). Tried dip 3 and 3+4+5 so far plus the 100pf cap to no avail. And like I said already it's impossible to tell if the chip is even truly glitching because I can disconnect wires from it and it will STILL blink which just doesn't seem right.

Couple pics of the install as it stands right now. Really want to get this thing working and it's frustrating the hell out of me. P1030351.JPGP1030315.JPG

Attached Images

• P1030351.JPG (1.56 MB)
• P1030315.JPG (1.48 MB)

01 - GTA V Disc 1.PNG

This is obviously a coaster, so where do I go from here? Do I just randomly tweak my EEPROM settings until I find the combination that sticks? What speed does everyone recommend burning backups on?

This Verbatim disc was burned through Imgur in Safe Mode with settings:
Smart Burn ON
Force Hyper Tuning ON
Over Speed Writing OFF
Online Hyper Tuning OFF
Perform OPC Before Write OFF

Imgur also asked be before starting if I would like to disable Online HyperTuning for optimal 'overburning' performance and burning at 4x. Should I just accept these optimal settings?

Attached Images

• 01 - GTA V Disc 1.PNG (19.3 KB)

I got my console RGH in the first month when the RGH Hack came out and at that time only CB 6750 was supported and mine was CB 6752 but later on got my console RGH by using a Donor Nand of 6750 have being flashing my console with my nand which i dump using Flash 360 and it shows 6750

But here is the problem in some games mostly in xxx 5 it freezes after 20-30 mins remember it does not freezes for most games what could be the reason the donor nand does not shows any bad block flashed with Raw Flash , Flash 360 but while reading it shows reading error at status 250 but each time it shows at same blocks is there a tool to verify nand ? Also is there a software way to flash my original nand of 6752 since its being supported now or what could be cause since console does not freezes with most games.

hi all of you
i have a problem with my profile is corrupted when i put the latest dash 16537 on my glitched slim console please help me

Just lately, although it seems to be getting more frequent! When i am playing a game, the Xbox will suddenly go to a black screen and the power light will start flashing constantly as though the DVD drive is opening, however the drive never opens! More often than not i have to dashboard and press the eject button on console to open the tray and then close it to fix the problem! I'm using an unlocked PCB (v1.1) for the DG-164DS. I recorded a video of the problem as it just happened when i turned the xbox on. Any ideas or suggestions?

Hi, sorry for my english
I want to purchase a kit that allows me to perform the RGH on all xbox slim, and if I want use it for the phat what should I add?
I would like buy all in this shop www.ck3.co.uk
but there are too many kits with which to start, and what to add?
Nand-X o J-Runner V2 ? Which one for start ?
I can't use J-Runner for phat console, is right ?
I assume that the best, for all xbox360 console, is to buy

TX NANDX RGH EDITION - COMPLETE KIT

and what else?

sorry I'm a little confused

Ok got a spare xbox here Phat its either falcon or Jasper im sure its a falcon.

Whats the best chip to get? I was thinking Rjtag?
ITS RGH 2.0

If so i also heard u can install them the old jtag method with installing the RF board instead of the qsbs etc..

Whats the best way for me to do this for first installer etc.. as it will be my first rgh install I got rghs just want to do one for my self.

Thanks
Paddy

Ok so I haven't messed around with this stuff since I did the original RGH on my 512mb Jasper a couple years back, please bear with me I'm trying to re-learn everything.

So yesterday I was attempting to update to 16537, I had my updflash.bin in a USB stick and had booted into Xell. JUST as it started to update I lost power to my 360...I nearly got sick. Anyways, it still boots into Xell just fine but freezes every time while trying to mount the usb drives. I've tried to boot 10-15 times and let it sit for a couple minutes each time, no luck. So it sounds like my Xell install is broken and what I need to do is reflash my NAND another way or something? Help me out here guys. I've still got my flashing hardware - Nand-X and original ECC files, I just don't really know where to begin on how to solve this.

Also, I'm getting this when trying to write my old .ECC files back to the xbox with J-Runner:
Nand-x has yellow and red light on. Coolrunner has red light on and is in PRG mode. Nand-x is hooked to Coolrunner and PC but nothing else.

Jasper 512MB Manually Selected
Version: 03
Flash Config: 0xFFFFFFFF
Writing Nand
EccImage.ecc
Error: 000 writing block 0
Error: 222 writing block 1
Error: 282 writing block 2
Error: 6AA writing block 3
Error: 3F2 writing block 4
Error: 612 writing block 5
Error: 000 writing block 6
Error: 002 writing block 7
Error: 000 writing block 9
Error: 000 writing block A
Error: 000 writing block B
Error: 000 writing block C
Error: 000 writing block D
Error: 000 writing block E
Error: 000 writing block F
Error: 000 writing block 10
Error: 000 writing block 11
Error: 000 writing block 12
Error: 000 writing block 13
Error: 000 writing block 14
Error: 000 writing block 15
Error: 000 writing block 16
Error: 000 writing block 17
Error: 800 writing block 18
Error: 002 writing block 1A
Error: 000 writing block 1B
Error: 002 writing block 1C
Error: 000 writing block 1E
Error: 000 writing block 1F
Error: 000 writing block 20
Error: 000 writing block 21
Error: 020 writing block 22
Error: 202 writing block 23
Error: 000 writing block 24
Error: 000 writing block 26
Error: 002 writing block 27
Error: 000 writing block 28
Error: 000 writing block 29
Error: 000 writing block 2A
Error: 000 writing block 2B
Error: 020 writing block 2D
Error: 020 writing block 2E
Error: 000 writing block 2F
Failed to write 0x30 block
Failed to write 0x31 block
Error: FFE writing block 32
Error: EFE writing block 33
Error: FFE writing block 34
Error: FFE writing block 35
Error: FFE writing block 36
Error: FFE writing block 37
Error: FFE writing block 38
Failed to write 0x39 block
Failed to write 0x3A block
Failed to write 0x3B block
Failed to write 0x3C block
Failed to write 0x3D block
Failed to write 0x3E block
Failed to write 0x3F block
Failed to write 0x40 block
Failed to write 0x41 block
Failed to write 0x42 block
Failed to write 0x43 block
Failed to write 0x44 block
Failed to write 0x45 block
Failed to write 0x46 block
Failed to write 0x47 block
Failed to write 0x48 block
Failed to write 0x49 block
Failed to write 0x4A block
Failed to write 0x4B block
Failed to write 0x4C block
Failed to write 0x4D block
Failed to write 0x4E block
Failed to write 0x4F block
Starting remapping process
Remapping Block 23 @ 3FF
Failed to write 0x23 block
Error: 000 writing block 23
Done!
in 1:29 min:sec

I have a 0225 drive that I recovered the key on and I need to build a firmware file using the extracted files within Jrunner. My question is, can I use an 1175 pcb or do I need a regular lt 1.1. I assume it's 1.1 but just wanted to double check. What PCB board should I buy for this?

Console Type: FalconDashboard version: 5774
CB version: e.g 5774
Screenshot of NAND details from J-Runner:
(attach an image to your post)
J-Runner log:
=================================
21 September 2013 14:21:40
J-Runner v0.3 Beta (1) Started

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

Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 03
Flash Config: 0x01198010
CB Version: 5774
Falcon/Opus
Reading Nand to C:\Users\Sean\Desktop\J-Runner\output\nanddump1.bin
Reading Nand
Jtag Selected
Error: 250 reading block 27C
Done!
in 2:13 min:sec
Initializing nanddump1.bin..
Reading Nand to C:\Users\Sean\Desktop\J-Runner\output\nanddump2.bin
Falcon/Opus
Nand Initialization Finished
Reading Nand
Error: 250 reading block 27C
Done!
in 2:13 min:sec
Comparing...
Bad Block ID 027C Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 027C [Offset: 0xA3F800]
Bad Blocks Remapped
Bad Block ID 027C Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 027C [Offset: 0xA3F800]
Bad Blocks Remapped
Nands are the same
R-Jtag Selected
Retail Selected
Jtag Selected
Version: 03
Flash Config: 0x01198010
Writing Nand
nanddump1.bin
Done!
in 0:09 min:sec
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully falcon.bin
Version: 03
Flash Config: 0x01198010
Writing Nand
falcon.bin
Done!
in 0:09 min:sec
Aud_Clamp Selected
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully falcon_hack_aud_clamp.bin
Version: 03
Flash Config: 0x01198010
Writing Nand
falcon_hack_aud_clamp.bin
Done!
POST output from J-Runner (either POST_OUT monitor or RATER output):
(2 cycles is enough)
updflash.bin log (if applicable):
Image of R-JTAG board:
Images of close-up soldering to motherboard:
(attach images to your post)

Description of problem:

Was the console working before you started: Y/N

Version: 10
Power Up
Waiting for POST to change
Post 20 - CB entry point reached
Post 28 - FETCH_CONTENTS_3BL_CC
Post 08
Post 20 - CB entry point reached
Post 28 - FETCH_CONTENTS_3BL_CC
Post 38 - SIG_VERIFY_4BL_CD
Post 3A - BRANCH
Post 7A
Post 7B
Post 7F
Post 77 - INIT_OTHER_DRIVERS
Post 73 - INIT_SATA_DRIVER
Post 53 - DECRYT_VERIFY_HV_CERT
Post 13 - FSB_CONFIG_TX_STATE
Post 12 - FSB_CONFIG_RX_STATE
Post 20 - CB entry point reached
Post 28 - FETCH_CONTENTS_3BL_CC
Post 38 - SIG_VERIFY_4BL_CD
Post 3A - BRANCH
Post A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 30 - VERIFY_OFFSET_4BL_CD
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 A0 - Panic - VERIFY_SECOTP_6
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
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 F0 - Panic - VERIFY_OFFSET_CB_B
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 A0 - Panic - VERIFY_SECOTP_6
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
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 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 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 40 - Entrypoint of CD reached
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 15 - FETCH_OFFSET
Post 16 - FETCH_HEADER
Post 18 - FETCH_CONTENTS
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 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post E0
Post 10 - Payload/1BL started
Post 12 - FSB_CONFIG_RX_STATE
Post 13 - FSB_CONFIG_TX_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 A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
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 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
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 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 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post F0 - Panic - VERIFY_OFFSET_CB_B
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 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 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 40 - Entrypoint of CD reached
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post F0 - Panic - VERIFY_OFFSET_CB_B
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 15 - FETCH_OFFSET
Post 16 - FETCH_HEADER
Post 18 - FETCH_CONTENTS
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 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 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 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 40 - Entrypoint of CD reached
Post 70 - INIT_VIDEO_DRIVER
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 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 A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 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 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 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 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 10 - Payload/1BL started
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
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 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 A0 - Panic - VERIFY_SECOTP_6
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
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 15 - FETCH_OFFSET
Post 16 - FETCH_HEADER
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1B - RC4_DECRYPT

I'm wondering if there's any way to Install CR3Pro with just wires no qsbs? I see people saying they've done it but can't find any tutorials, thanks

hi guys.. i would like a help ...one week ago a friend did the flash at my dvd samsung ms28 but now xbox has a error the central light green flashing and 3 red led error ..how i can do?:facepalm::facepalm::facepalm::facepalm::facepa lm:

Hi all,
I recently bought a xbox 360 s 4gb, still haven't opened the case, but i'm pretty sure it's a corona v4 since it's from 2012, and if that's the case then what products am i going to need to perform a full rgh install, i've already read some guides so i wanted to know if the 4gb r/w qsb is really necessary, and if it is than am i going to need anything else to read the nand, or do i just need to purchase the cr3 pro ultimate bundle. It's just so i can order it all together.
thanks in advance

Ok, I'm as close to a n00b as you can get. I'm sorry if this has already been answered, I know most of the time the answers are out there, it's just a matter of entering the proper string into Google. I don't mind doing things, but I'm just not sure what direction I should go at this point. Please follow me as I explain all of this:

I received a spoofed 360 from a friend, worked great. He did not want it because it was banned. I have no issue with that, I play all local stuff anyways, don't need to go online. Worked great for a long time, I think one of my kids dropped in a game that wanted a dash update. Now, the 360 is stuck trying to do an update. I cannot put the original drive back in, as it was thrown away because it died. So, every time the 360 is powered on, I receive cannot complete update, 213b-3cd6-b800-0402-c000-0001 is the error code. I had at one time figured out what update it died on, tried to restart the update, etc. I cannot get it to finish the update, and that's the ONLY thing the box will do.
SO, I did some forum reading, and decided to RGH2 it. I picked up a CR3 Rev C, and a Nand-X. I have a Zephyr. Come to find out, they are a pain for RGH, and I should have gotten a JTAG instead.
Well, I was going to try my luck, see if I can get anywhere. But, no such luck. I can read the nand from the 360, and there's no issues. I try to patch it, to boot Xell, and I end up getting an assertion error, or it just will not work.
I'm not sure what serial number I have here is correct (there is one on the black case that it has, and a different one by the USB ports on the metal cage.
So, with what I have, and the information I've given you, can you help me please? I'll gladly supply any additional information needed. CB is 4569. I can write the original NAND back to the 360 and it will power on and try to complete the update. Thanks in advance!

I have a Samsung SE-208DB/TSBS Slim Portable DVD Writer (Black) burner max says its compatible but I've went through four disc and no success. I'm trying to burn xgd3 games. I use a verbatim dual layers.Any help would be much appreciated. Is it even possible to burn them with my drive?

So, I obtained this xbox 360 from a friend. He said every time he turns it on it says "Sorry, this console can't be played until the subscription is up to date." I've done some digging on this and it turns out it's one of those entertainment for all deals. Whoever he got it from cancelled their sub without paying or something.

What I wanna know is if there is a way to mod the motherboard to where I can get around this problem.

Thoughts?

i got Falcon to RGH, and cannot configure what is the problem in my j-runner...ERROR 202, and after flashing then turn on, E71 on my screen..

LOG:

Checking Files
Finished Checking Files
RGH Selected
CpuKey is Correct
Falcon Manually Selected
Load Files Initiliazation Finished
16537
Started Creation of the 16537 xebuild image
---------------------------------------------------------------
xeBuild v1.09.639
---------------------------------------------------------------
base path changed to C:\Documents and Settings\noi\My Documents\Xbox\J-Runner v03 (1) Core Pack\J-Runner\xeBuild
---- { Image Build Mode } ----
building glitch image

---------------------------------------------------------------
C:\Documents and Settings\noi\My Documents\Xbox\J-Runner v03 (1) Core Pack\J-Runner\048277781507\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.16537.0
Console : Falcon
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 048277781507
ConsoleId : 011280912015
MoboSerial: 8394663205008157
Mfg Date : 04/11/2008
CPU Key : A5B3CFA354E870DC95DE12F8C0185121
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 898C76B190CDD53FC7A980FE184A5840
CF LDV : 9
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Documents and Settings\noi\My Documents\Xbox\J-Runner v03 (1) Core Pack\J-Runner\048277781507
Image is Ready
Initializing updflash.bin..
Falcon/Opus
Nand Initialization Finished
Version: 03
Flash Config: 0x01198010
Writing Nand
updflash.bin
Error: 202 writing block DA
Done!
in 2:07 min:sec