Zephyr Problems? Read Here ! *** UPDATED AUGUST 10TH 2013 ***

Xecuter

Staff member
Top TX Brass
Dec 6, 2002
11,465
128
Asia
team-xecuter.com
AUGUST 10TH 2013 UPDATE:

We are now seeing users getting their Zephyrs to work, however as expected the boards are awful quality and require a reflow/reball to the CPU/GPU/RAM.

We have confirmed the following RATER POST error codes:

Zephyr RJTAG stock smc:

Hang on fast 2E locks up = 0110 -> CPU/GPU/RAM Related
Hang on 40, 41 or 42 = 0102 -> CPU/GPU/RAM Related
Hang on long 2E = 0022 -> General HW Error

AUGUST 2ND 2013 UPDATE:

After testing many different Zephyr's we found there are 3 types so far. We have changed the hardware to a new version (v1.1). All resellers will have these in stock by now, and if they are not advertising v1.1 and you have a Zephyr insist that the version they send you is v1.1. It will not matter if you have a Falcon/Opus/Jasper. This does not mean that the v1.0 was faulty, we wouldn't have shipped it if our Zephyrs didn't work, of course not. What it means is that after large usage a number of customers found that they had one of the versions that we did not know about. As soon as we discovered this we launched a plan to get as many of these as we could so we could make any necessary changes or additions. There is no way to tell you if a v1.1 will work or if a v1.2 will be released in future. If there is a new release then we will not swap any v1.1 for v1.2 or any other subsequent version as we are giving full notice of this policy so it shouldn't be of any surprise. We are offering to change the v1.0 to v1.1 for Zephyr users as a gesture of goodwill.

Now bear in mind Zephyrs suck. Even if it glitches there is every chance that it won't boot due to the fact that the board requires a reflow or better still a reball - especially the CPU/GPU.

We have 19 Zephyr's in our possession and every single one of them works with v1.1 (half of those required a reflow at least). This is great but we cannot guarantee that they will work with every Zephyr.

Along with all the different ways to fine tune a Zephyr there are also two new options with v1.1

1. The DIP switch settings have changed

JASPER DIP 7-8 ON ON
ZEPHYR DIP 7-8 OFF OFF
FALCON DIP 7-8 ON OFF

2. You can also use a FALCON NAND (basically use Falcon 5770 CB)

If the Zephyr fails to boot on 2E, it is glitching correctly and the R-JTAG is working perfectly - the problem is that the CPU needs a reflow / reball.


I know there are users who have an R-JTAG v1.0 and they can't get it to work on their Zephyr. While there is never any guarantee that if you can't get it to work you can return it, we will in this case accept R-JTAG v1.0's from Zephyr users who wish to get a v1.1 model. This will be done on a RTB (Return to Base) basis only i.e. You ship the R-JTAG itself (no packaging / wires / qsb's etc) to one of our collection addresses in China at your expense and we will arrange a return shipped item at our expense.

We have setup a special email address for users to contact and make the necessary arrangements: [email protected]

Thank you


Original Post:

We are seeing a number of users who get the same non-boot issues with Zephyrs.

For the record all our Zephyr's boot just fine in testing, the design was tuned to work well with Zephyrs - however we think there maybe hardware variables with the Zephyr that is causing it to non boot.

So. We want your Zephyrs.

They have to be booting perfectly fine when in stock mode - no RROD's.

They have to be not booting with R-JTAG (or RGH) when installed correctly - don't waste your time if you are an electronics butcher - you must be confident that your install is good and that you qualify in this scenario.

If you are that guy - then please respond here with the full information of your zephyr including pictures, logs and info regarding your tests.

if we feel you qualify we will arrange for the console to be collected and we will look at it ourselves to determine if there is any extra work required to R-JTAG to get them working.

Your console - if working - will be returned. If we find any are RROD and require a reflow/reball we will not return them.

Thanks
 

Dublicious

VIP Member
Mar 3, 2012
250
48
Modding on 22's
Re: Zephyr Problems? Read Here !

I am willing to send my sons console off to help with this problem:

Console Type: (Zephyr)
NAND size: 16
Dashboard version: 15574
CB version: 4569

Zephyr Nand.png

POST:

Version: 10
Power Up
Waiting for POST to change
Post 01
Post 01
Post 20 - CB entry point reached
Post 30 - VERIFY_OFFSET_4BL_CD
Post B0 - Panic - VERIFY_CONSOLE_TYPE
Post A0 - Panic - VERIFY_SECOTP_6
Post E0
Post 60 - INIT_KERNEL
Post 20 - CB entry point reached
Post 10 - Payload/1BL started
Post 08
Post C1 - LZX_EXPAND_1
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
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 A0 - Panic - VERIFY_SECOTP_6

AUD QSB 1.jpgAUD QSB 2.jpgAUD Wire.jpgCPU_RST.jpgnand 2.jpgNand.jpgPost Out QSB 2.jpgPost out QSB.jpgRjtag.jpg

I attempted to glitch this using AUD_CLAMP and without AUD_CLAMP. All dips and variations were tried all with the same A0 Failure.

I attempted to RGH2 this console but to no avail. 13 hours and not glitch into XELL. This console is my sons so I am willing to send it in. I think he will understand.
On that note, do you want the original NAND written back and all R-Jtag removed or?
 

eshugo

Noob Account
Feb 6, 2011
2
0
Re: Zephyr Problems? Read Here !

Console Type: Zephyr
NAND size: 16
Dashboard version: 16202
CB version: 4569
Screenshot of NAND details from J-Runner:
NAND Info.PNG
POST output from J-Runner (either POST_OUT monitor or RATER output):

Code:
[COLOR=#000000][FONT=Arial]Version: 10[/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Power Up[/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Waiting for POST to change[/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 10 - Payload/1BL started [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 11 - FSB_CONFIG_PHY_CONTROL [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 12 - FSB_CONFIG_RX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 10 - Payload/1BL started [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 11 - FSB_CONFIG_PHY_CONTROL [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 12 - FSB_CONFIG_RX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 10 - Payload/1BL started [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 11 - FSB_CONFIG_PHY_CONTROL [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 12 - FSB_CONFIG_RX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 10 - Payload/1BL started [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 11 - FSB_CONFIG_PHY_CONTROL [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 12 - FSB_CONFIG_RX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 13 - FSB_CONFIG_TX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 14 - FSB_CONFIG_TX_CREDITS [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 15 - FETCH_OFFSET [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 16 - FETCH_HEADER [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 17 - VERIFY_HEADER [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 18 - FETCH_CONTENTS [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 19 - HMACSHA_COMPUTE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1A - RC4_INITIALIZE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1B - RC4_DECRYPT [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1C - SHA_COMPUTE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1D - SIG_VERIFY [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1E - BRANCH [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 20 - CB entry point reached [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 21 - INIT_SECOTP [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post A0 - Panic - VERIFY_SECOTP_6 [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 10 - Payload/1BL started [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 11 - FSB_CONFIG_PHY_CONTROL [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 12 - FSB_CONFIG_RX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 13 - FSB_CONFIG_TX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 14 - FSB_CONFIG_TX_CREDITS [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 15 - FETCH_OFFSET [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 16 - FETCH_HEADER [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 17 - VERIFY_HEADER [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 18 - FETCH_CONTENTS [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 19 - HMACSHA_COMPUTE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1A - RC4_INITIALIZE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1B - RC4_DECRYPT [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1C - SHA_COMPUTE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1D - SIG_VERIFY [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1E - BRANCH [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 20 - CB entry point reached [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 21 - INIT_SECOTP [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post A0 - Panic - VERIFY_SECOTP_6 [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 10 - Payload/1BL started [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 11 - FSB_CONFIG_PHY_CONTROL [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 12 - FSB_CONFIG_RX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 13 - FSB_CONFIG_TX_STATE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 14 - FSB_CONFIG_TX_CREDITS [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 15 - FETCH_OFFSET [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 16 - FETCH_HEADER [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 17 - VERIFY_HEADER [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 18 - FETCH_CONTENTS [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 19 - HMACSHA_COMPUTE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1A - RC4_INITIALIZE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1B - RC4_DECRYPT [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1C - SHA_COMPUTE [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1D - SIG_VERIFY [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 1E - BRANCH [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 20 - CB entry point reached [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post 21 - INIT_SECOTP [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Post A0 - Panic - VERIFY_SECOTP_6 [/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Most Fails(cumulative): 0xA0[/FONT][/COLOR]
[COLOR=#000000][FONT=Arial]Shutdown[/FONT][/COLOR]
Image of R-JTAG board: Image below but not great. Dips 8 and 3 set currently.

Images of close-up soldering to motherboard:
IMG_20130615_110452_788.jpgIMG_20130615_110617_582.jpgIMG_20130615_110623_590.jpgIMG_20130615_110504_929 - Copy.jpgIMG_20130615_110504_929.jpgIMG_20130615_110525_106.jpgIMG_20130615_110432_145.jpg

Description of problem: Unable to glitch and sometimes will eventually RROD. Before uncovering and soldering the point circled in RED the xbox would seem to “glitch” and boot but go back into glitching. I just wasn’t sure if this was applicable to all boards since all the other solder points are exposed.

Was the console working before you started: Yes

Same as Dublicious I attempted to RGH this console and was unable to get it to XELL at all. I also attempted with and without the AUD_CLAMP. No bad blocks were found within the NAND. I don’t have a ton of experience with these recent mods but my Falcon will RGH2 in a couple cycles and I think my soldering is above average.
 
Last edited:

Antalpromille

VIP Member
Aug 4, 2011
3,165
0
Borås, sweden
Re: Zephyr Problems? Read Here !

We have enough Zephyrs. A prototype of a new R-JTAG is being made available to certain testers.
is it new hardware or new software?
 

mrdrifta

VIP Member
Jan 31, 2011
325
0
New Zealand
Re: Zephyr Problems? Read Here !

Its likely the same hardware with different software, like, DIPS 7on 8off for one version of the code, adjust timing with DIPS, or 7on 8on for another version of code, etc.

I can wait for a solution, have i pile here that i have been contemplating scraping. Guess ill hold of until after the results of testing
 

BL4K3Y

VIP Member
Jul 7, 2010
12,842
118
Colne, Lancashire (UK)
Re: Zephyr Problems? Read Here !

is it new hardware or new software?
I don't have a Zephyr board here to test the new R-JTAG prototype with, but I'm sure it involves new code (the JTAG header doesn't seem "redundant" now - at least not for Zephyr owners ;)).

However, certain hardware changes may also need to be implemented to accommodate for Zephyr boards, but I am sure it has more to do with the R-JTAG code.

I only know as much as you guys and I am sure that TX will provide us with a reliable solution.
 
Last edited:

pengekcs

BANNED
Mar 1, 2010
216
0
EU
Re: Zephyr Problems? Read Here !

Great great news. I have with me since weeks now a crappy board and keep telling the owner to wait just a bit more every once in a while thinking that we'll have finally a solution. This sounds great though I was hoping for something more concrete / specific :)
 
Last edited:

BL4K3Y

VIP Member
Jul 7, 2010
12,842
118
Colne, Lancashire (UK)
Re: Zephyr Problems? Read Here !

Probably going to get flamed into oblivion but since the xenon and zephyr's are somewhat similar will this bring us any closer to a xenon hack?
Xenon R-JTAG is coming soon.

I'm sure a couple of the devs/testers already have R-JTAG DemoN setups running on their Xenon consoles ;).
 
Last edited:

[email protected]

VIP Member
Jun 21, 2012
383
0
Re: Zephyr Problems? Read Here !

I know my question is stupid, there is no point for you (I mean Team Xecuter) to improve RGH, but did you understand why some Zephyrs boot RGH1 instantly (just like Falcons) and some don't boot at all no matter what ?
 

ExBoxHax

Senior Member
Jul 5, 2013
130
0
USA
Re: Zephyr Problems? Read Here !

I have a stubborn zephyr here. I'd be willing to try the RJTAG prototype (and pay for it) if necessary. It's a cb 4578 and It simply refuses to glitch. I know my soldering is good on the RJTAG and will post pics if necessary. I'm going to try playing around with some stuff and will update if anything changes. I'm really looking forward to this stubborn zephyr fix.
 

pengekcs

BANNED
Mar 1, 2010
216
0
EU
Re: Zephyr Problems? Read Here !

I saw this image a few minutes before:

Code:
http://team-xecuter.com/forums/attachment.php?attachmentid=19025&d=1374294651


from this thread:
Code:
http://team-xecuter.com/forums/showthread.php/137883-Falcon-powers-on-then-off
It obviously came for modchipcentral.
Code:
http://www.modchipcentral.com/store/product.php?productid=17928&cat=294&page=1
Notice the "fw v1.1" text on top of the TX logo embossed XC2C128 chip? Does it mean we have to send back to TX our v1.0 R-JTAG chips for reprogramming *if* we have those nasty non-booting zephyrs? I do have one sitting next to me since 3 weeks now waiting for this "timing" issue to be fixed. I imagine you will not release a simple over-jtag programmable xsvf file to make our lives easier due to fear of cloning. Can anyone in the know comment on this?

How do we who got stuck with v1.0 and a non-booting zephyr get this update?
 
Last edited:

Sea_C

Noob Account
Jul 8, 2013
1
0
Re: Zephyr Problems? Read Here !

Sorry, pretty new here and I was wondering if this fix is hardware or software side? Because I have a Zephyr here that could really need some love since it experiences these same issues. I'm sure I soldered/wired everything right so an ETA would be nice since it's been about two weeks since I installed the ultimate kit. Cheers!
 

bluebottle

Full Member
Jan 19, 2011
86
0
nr Petersfield Hants UK
Re: Zephyr Problems? Read Here !

lets hope we don't have to send them back! Sending us a replacement would be fair, I would be happy to return mine once I had the new one installed and working. I would much prefer a s/w patch of some type which would save time as its taking so long to get my Zephyr working.
 

XDK

VIP Member
Re: Zephyr Problems? Read Here !

lets hope we don't have to send them back! Sending us a replacement would be fair, I would be happy to return mine once I had the new one installed and working. I would much prefer a s/w patch of some type which would save time as its taking so long to get my Zephyr working.
You will never see a f/w avaliable for rjtag or a cr3pro if they ever released that fw cloners would be in paradise
 
  • Like
Reactions: bluebottle