Quantcast
Channel: Team Xecuter
Viewing all 6917 articles
Browse latest View live

RGH /ODE Which one should I use?

$
0
0
Hey all

Bought sometime ago a "X360 250GB Slim" glossy from some guy second-hand to mod it. Yesterday I opened it to find out what drive/model it has, which is the following:
Drive: DG 16D4S 0225
135W PSU 10,83A MFR: 2011-01-14
It has a HANA chip --> Trinity
Metro dash 14699 – 16547 -> dashboard 2.0.16203.0

So if I want to RGH it what's the best and easy/cheap way to do? What kind of RGH tools do I need to buy? And which guide do I need to follow here or on which subforum can I find it. I don't really care for Xbox Live since I aint gonna pay for MP. I just wanna play some game on it via a external hdd. My other option is to buy a X360key and install it that only require the Xecuter X360 USB Pro V2 and the x360key which is kinda pricey right? Or what else do I need for it? I modded some other consoles like my Wii with a Wodejukebox. Still have an Xbox modded with Xecuter modchip dunno which one but that's almost 10years ago or so. I know that the X360key only plays region based games and no XBLA games also no DLC or other crap but that doesn't matter much. Soldering isn't a big issue but solderless is alot easier. Which one should I do? RGH or ODE it? My console is open atm so going to buy some stuff asap that it's get done till the end of next week hopefully.

Error 0022 after flashing back to stock.

$
0
0
Hey guys... did a console (Zephyr - RGH1) for a kid that is local but moved to Colorado... Everything was good on my end when i shipped it out (USPS)... but when the customer got the console he couldnt get it to glitch. I thought at first it was the PRG/NOR switch got tripped (ive had it happen once before shipping USPS...NO freaking clue how...). So, I had the kid take the cover off and check the PRG/NOR switch as well as take a look at the DBG light (DBG wasnt lighting up) so, I had him send it back to me.

Anyway, long story short, I got it back today and redid all the wiring figuring it was a broken solder joint or something. Still no debug light). So, figured...lets check stock NAND... lo and behold, im getting RRoD (0022)... is rthere any chance this is a lifted trace i just cant see? or is 0022 always needing to be reflow/reball?

Photos of PLL_BYPASS (As it's the only thing ive seen so far that MIGHT cause 0022)
There doesnt seem to be any damage, and pad is not lifted...

http://i1326.photobucket.com/albums/...ps34e7df7f.jpg

http://i1326.photobucket.com/albums/...psbbb81acf.jpg

ALSO, now that i compare nands (i read the nand before flashing back to retail...)
here are screen shot comparing the nand i took from the machine after i got it back and one of the nand when i load it from retail...

Parallels Picture 1.pngParallels Picture 1.png
Attached Images

R-Jtag power but green power led doesn't comes

$
0
0
Hello, Please help me just received a R-jtag ultimate kit, I installed it and read Nand, create ECC and Write ECC that part went well. Now when i power up the xbox Jasper 512 console it turns on but, the power green led doesn't comes on

that's where i stuck..
Anyone Please help

R-JTAG Falcon Boot problems

$
0
0
Console Type: Falcon
NAND size: 16
Dashboard version: 2.0.16547.1


CB version: e.g 5774
Screenshot of NAND details from J-Runner:y
POST output from J-Runner (either POST_OUT monitor or RATER output):rater y
(2 cycles is enough)

aud_clamp
1.8v dips 7 and 1 on all else off. 470 on.
original reset point worked (alt tired but no boot at all.)

Description of problem: Was up and running to dash but a bit was still a bit temperamental. Tried a few more setting with dips and voltages but now even original settings wont boot. Yes i have burnt off the voltage jumper pads and pad K but this is what comes of late nights and stupidly not taking a break. (Hands Up F**K Up) But this was all fixed as shown and the xbox booted to dash with my temp repairs. (might order a new board to make it look pretty again when funds allow) any help would be more than warmly received.


Was the console working before you started: Y

Code:

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 12 - FSB_CONFIG_RX_STATE
Post 10 - Payload/1BL started
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
Post 20 - CB entry point reached
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 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 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
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
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 22 - INIT_SECENG
Post 2F - RELOCATE
Post 2E - HWINIT
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 17 - VERIFY_HEADER
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Most Fails(cumulative): 0xA0
Shutdown
Resetting................

20140410_211014.jpg20140410_211240.jpg20140410_211344.jpg20140410_211452.jpg20140410_211521.jpg20140410_211650.jpg20140410_211727.jpg20140410_211835.jpg20140410_211920.jpgCapture.PNG
Attached Images

New To 360 - Where Do I Start ??? Please Help !

$
0
0
Hey Guys ! I am new to the world of Xbox 360 , however I do have prior experience with electronics , I repair smart phones for friends as a hobby in my spare time and I do have decent soldering skills. I recently acquired a Xbox 360 Slim from a garbage pile believe it or not. Ive done some research as I know in order to be able to find out what can be done I need to know what hardware components the Slim contains. From what I have seen so far on the net I believe the motherboard in the Slim is the Corona V1. I used these 2 sites as references http://www.consolehacker.co.uk/INFOR...DEL/SLIM-MODEL and http://team-xecuter.com/forums/showthread.php?t=76989 now according to the console hacker uk ID page my MOBO is the Corona V1 with 250GB HDD ( ID'd by chip on MOBO ) however according to team xecuter ID page my MOBO is the Trinity as the plastic cover on the back where the power supply plugs in says it is using the 135W PSU @ 12V and 10,83A. Also I believe that the DVD Rom in the Slim is the Philips - LiteOn DG-16D4S wit the 0225 Firmware and I used this site as the reference http://www.360drives.com/list . Now the Slim is also missing the Hard Drive , Controllers , Power Cable / Cube ( I dont know what XBOX 360 Slim Uses :( ) and the AV Cables. My question to you is where do I start ? I know obvious things such as get a HDD and the cables but can I just slap any SATA Notebook HDD in there or are the XBOX 360 Slim HDDs console specific ? Once I accomplish that task I would ultimately like to get the Slim to play copied games directly of off the HDD but I would also like to retain the capability of going online without being banned ( Is that a possibility ? ) So im here pretty much to be schooled in the art of modding the slim. Drop some knowledge on me and point me in the right direction please and if possible I would like "NOOBPROOF Instructions" :) Thanks Guys !!!!!!!!!!!!

DeSEBticoN

No more 4gb nand r/w QSB's????

$
0
0
I'm from california and i've contacted Xconsoles and modchipcentral asking about the xecuter 4gb nand r/w qsb's, because i've recently run out, and they've both stated that they don't have anymore and don't know when their getting more. Same goes for the 4gb nand r/w kit. Is team xecuter not making them anymore? Just thought i'd come here and ask anybody who is in the circle that may know. Thanks for any answers.

And actually just checked their websites and they dont even have an option to buy the qsb's separately anymore.... weird. I need more :-(

X360 Glitch Chip / Coolrunner Transplant

$
0
0
I got a trinity in today that had an x360 glitch chip inside with horrible boot times. I wanted to replace it with a coolrunner but in my infinite wisdom I ripped the chip out without first getting the CPU key and now it won't glitch with the coolrunner in there...I guess the hacked images are different????

Anyway, I wanted to know if I would be able to dump the existing NAND and then write the trinity.ecc from Jrunner and use the trinity timing file with my coolrunner to glitch it and get the CPU key then build a hacked image in Jrunner...

I tried explaining this the best I could sorry if it's not translating well.

My main question is: If you don't have the original NAND for a console can you write an ecc file to glitch it for the CPU key and then use that key to build a working NAND?

Please tell me I don't have to solder this hunk of crap back in there to get the cpu key.

GENERAL Which is better for Glitching? Trinity or Corona ?

$
0
0
Hi.... I am looking for a Slim to buy.. I just want to know if there is any difference between Trinity and Corona in terms of glitching and which is easier to mod, or if there is any other major difference between the two.

Also, do I have to look for any particular version of Corona, such v1,v2 etc...

Thanks in advance for any help...

RGH help with corona

$
0
0
hi guys i bought an rgh system but i want to revert to stock the problem is that the one who hack the console change the dvd key to 12345678123456781234567812345678 i already bought ltu 2 board...... any help

Demon & JRP v2 Nand Reads Different?

$
0
0
Someone brought me a corona with a pin header installed that he used to read the nand & he decided to let me install the demon and after install i compared a demon dump to a jrp v2 dump and they did not match, is that normal??

Jrunner Log
Code:


===================================================
Friday, April 11, 2014 3:32:51 AM


J-Runner v0.3 Beta (4) 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
Initializing nanddump1.bin..
Corona
RGH2 Selected
Nand Initialization Finished
Comparing...
0x0390
0x0391

Maybe this should be in the jrunner section, if so i'm sorry..

RJTAG Installation Problems, Jasper, Template inside

$
0
0
Console Type:Jasper
NAND size: 16
Dashboard version: 2.0.16537
CB version: 6754
Screenshot of NAND details from J-Runner:
IMG_3645.jpgIMG_3646.jpgIMG_3647.jpgIMG_3649.jpg
POST output from J-Runner (either POST_OUT monitor or RATER output):
Nandx only..

Description of problem:
After writing Xell-reloaded the console doesn't boot. RJTAG chip shows red light and green light flashes. Green light flashes several times. The console then displays error 0022, and the flashing stops. The console works fine if flashed back to stock and the chip is removed.

Was the console working before you started:
Yes
Attached Images

Finally!!! Burning Forza 4 successfully with HP 1260i(1260v AH24) DVD Burner!!!

$
0
0
Please note that this is specific to those of you who bought the HP1260i(1260v AH24) DVD burner hoping that it would be crossflashable to iHas, but was disappointed
to find out that it could'nt:facepalm: (yes, like me:( )

Not to worry, i,ve figured out how to burn Forza 4 onto an HP Dual Layer disc WITHOUT ANY ERRORS!!!(as i don't have any Verbatims)
Also note that I've done some ISO mods on it too!!! If you are not interested in the modding part, then just skip down to the ImgBurn Settings.

This is what i did in the ISO mods:
...Unlocked All Unicorn Cars
.......Top Secret Silvia
.......Top Secret Supra
.......Mines GTR R34
.......Mines GTR R32
.......Can't remember the others:crazy:

...Wheel Spacers
.......Toyota Celica SS-1 2003
.......Top Secret Silvia
.......Honda Civic Si Coupe 1999
.......Honda Civic TypeR 1997
.......Honda Prelude
.......Nissan 240SX
.......Nissan Silvia 1992
.......Nissan Silvia 1994
.......VW Golf GTi 16v MKII 1992
.......VW Golf GTi Rabbit
.......VW Golf GTi MKV
.......VW Golf GTi VR6 MK3:confused:

...Also tempered with their "Spring damper Physics" to be able to lower them extremely.
...Also tempered with their Static Camber angle settings to be able to actually see a visual diffirence on the home screen!!!

At this point my gamedb.slt was still at 6.19Mb(6 348Kb) in size, so i decided to unlock all the manufacterer rims:facepalm:
After unlocking about 30 Rims, the size of the gamedb.slt changed to 6.20Mb(6 350Kb) in size. Stupid me went and
saved it, thinking it was just a glitch in the ******:facepalm:
Opened it again and tried deleting what i did last(locking the manufacturer Rims again), but the size remained the same:facepalm:

I Then noticed that there is an option in Sqlite under the "File" tab(Compact Database). I clicked it....and low-and-behold, it shrunk
the size to 6.19Mb(6 347Kb this time).:)

Okay now that part was done. It was onto the replacing of the gamedb.slt into the ISO.
Now this what i did and it might not even be needed to do(but please, you've tried it your way so just do what i did).
Open Xbox Backup Creator(i used v2.9.0.350), go to the Image Tools Tab select the INJECT option under the Action setting.
Now find the Forza 4 ISO and find where the gamedb.slt is on the ISO, highlight it, right click and replace it with the moddified
gamedb.slt. Now close Xbox Backup Creator.
Insert a blank Dual Layer DVD+R disc.
Open BurnerMax Payload Tool and enable your drive by clicking the BurnerMax button(if it doesn't enable automatically).
Don't close it!!! Just minimize it!!!
Now Open ImgBurn(the version i have is v2.5.8.0)
Okay now from here, i will post pictures of how my ImgBurn settings are. Follow them exactly!!!! It will save your life...or your discs:facepalm:

I Know that this will help a lot of you.
Enjoy
I am The Nitman:crazy:

I've done this 3 times btw!

This might work for other dvd drives capable of using BurnerMax Payload Tool.

RGH Problem with soldering R2C7 and glitch corona v3.

$
0
0
DSCN8224.JPGDSCN8216.JPGDSCN8226.JPGDSCN8222.JPG
Description of problem:
When I bridge R2C7 my consol stops working and a red light shows on the consol. When I remove bridging the consol shows a green light and starts up.
I have checked all my solder points on the JPR/NAND/CR QSB V3 and when reading NAND with the NAND-X every thing works fine.
You may see in the pictures that a couple of the resistors are missing (R2C9 and R2C10). This is because I have soldered and de-soldered quite a few times to find out about R2C7, I have bridged these as well.
When I connect the Slim Proto V2 the green pulse light begins to flash but the consol does not glitch. I have read in the forums that you have to bridge R2C7 for the corona V3 to glitch but when I do this there is no life in my consol. I haven’t seen this type of problem mentioned in the forums about this.

Questions:
Any explanation as to why I get a red light on my consol when I bridge R2C7?
If I can’t bridge R2C7 will I not be able to glitch my consol?

Xbox 360 Slim Info:
Corona V3 (MFR:2012-09-27)
SN nr.: 203705423943
Dash nr.:2.0. 165470

NAND-X
Slim Proto v2
JPR/NAND/CR QSB v3
Slim Post QSB v3
Postfix adapter v1

Tuning of Slim Proto:
Post Out pad 1
Cpu_RST pad default (under X-clamp)
Dips 3 and 8 on.
Red light on with green light every 5 seconds- no picture on screen and no booting to xell.

Any help or tips are much appreciated.
Steven.
Attached Images

LITEON DG-16D2S looking for a working drive

$
0
0
must have the pcb in it and of course work this is the model PLDS DG-16D2S

Help tracing R-Jtag 1.2 or 1.8 volts points

$
0
0
Help tracing R-Jtag 1.2 or 1.8 volts points

My Point got mess up, it got ripped out . Where else can i trace this point?
Can’t do any of the bridge without this point (1.2 volts) or (1.8 volts)

see image: http://s1.postimg.org/3p3o98067/image.jpg

Please help if you can Urgent...Thanks

R-JTAG zephyr wont boot

$
0
0
Console Type: zephyr
NAND size: 16
Dashboard version: 2.0.15574.0
CB version: 4558


i'm sorry but i have a problem with uploading images to here, i have used another site for image install pics
i created image without nanddump.bin but when i flash updflash.bin, the console refused to boot i gone through all dips
but no luck. it behaves funny. not powering on normally and the glitching is not correct. the green led flashes starts normal but
after a few cycles the led flashes 3-4 times non-stop and goes back to normal. powering it is a big problem it doen't
allow to put unless it is off for a long tome but still if it does second time, it will refuse. no light is on. all the 5 green lights
are not on. the ring and the middle are not on. even jrunner cant put it on
i'll appreciate any help

http://feed1.tinypic.com/rss.php?u=v...uGHgoq1g%3D%3D

Code:

Phat Selected
Device not found
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 08
Post F1 - Panic - VERIFY_HEADER_CB_B
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
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 80
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
Post FC
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
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
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
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 03
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
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 80
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
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
Most Fails(cumulative): 0xA0
Shutdown

Attached Images

Help tracing R-Jtag 1.2 or 1.8 volts points

$
0
0
Help tracing R-Jtag 1.2 or 1.8 volts points

My Point got mess up, it got ripped out . Where else can i trace this point?
Can’t do any of the bridge without this point (1.2 volts) or (1.8 volts)

see image: http://s1.postimg.org/3p3o98067/image.jpg

Please help if you can Urgent...Thanks

R-JTAG R-Jtag Chip problem

$
0
0
I have a new R-jtag chip, after I installed it to my Jasper, the green light is always on, even when I only solder the 5V and GND wires, and the green light is on before I power on the Xbox. I replace it another R-jtag Chip and the xbox boots fine each time.Does any know know what's wrong with R-Jtag Chip?
Attached Images

R-JTAG JASPER CAN'T GO PAST XBOX LOGO

$
0
0
Kernel : 2.0.16747.0
Console : Jasper
NAND size : 16MiB

i got the cpu_key and created image but when i wrote it on the console, the machine started behaving
funny and this has happened to me with all r-jtag chip i bought this time around.
the console fail to power up with their normal power switch, instead you have to give time or pull and push back
the power switch for them to power up the console, it also fails to show the ring leds even the centre one is not displaying.
i have posted pics in other threads i have created with almost similar issues and i have not got one my/our seniors telling me that
i have poor installation or bad soldering. i have also failed to boot into xell with the jtag qsb but instead i got the key of this console
(jasper in this thread) using resistors/ manual install i grabbed the and installed the jtag qsb back.
i'm sorry if the problem is with me but i'm eager to find out what causes the console not to power, and once it starts doing that,
you also get problems with stock. i have read a similar issue in someone's thread and i hope its easy to fix.
please i'm calling for help if any of the expert can help here.

---------------------------------------------------------------
Kernel : 2.0.16747.0
Console : Jasper
NAND size : 16MiB
Build : JTAG
Xell : power on console with console eject button
Serial : 317772192805
ConsoleId : 019582582976
MoboSerial: 792105C207109285
Mfg Date : 07/09/2009
CPU Key : E24356C6F5772C4DEA7484006F8B6C8F
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 2F42D59DD2CFF6B1B412F7D9E5F2A068
CF LDV : 7
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to F:\X\J-Runner v03 (1) Core Pack\J-Runner\317772192805
Image is Ready
Initializing updflash.bin..
Jasper 16MB
Nand Initialization Finished
Version: 10
Flash Config: 0x00023010
Writing Nand
updflash.bin
Done!
in 3:36 min:sec

there is also change in color but with AV only HDMI its clear but with AV color fades, its not pure.





Device not found
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 07
Post C7 - LZX_EXPAND_7
Post 87 - Panic - ALIGNMENT
Post 97 - Panic - NONHOST_RESUME_STATUS
Post F7
Post C7 - LZX_EXPAND_7
Post F7
Post C7 - LZX_EXPAND_7
Post E7
Post F7
Post C7 - LZX_EXPAND_7
Post F7
Post C7 - LZX_EXPAND_7
Post E7
Post F7
Post C7 - LZX_EXPAND_7
Post F7
Post C7 - LZX_EXPAND_7
Post E7
Post F7
Post C7 - LZX_EXPAND_7
Post F7
Post C7 - LZX_EXPAND_7
Post E7
Post C7 - LZX_EXPAND_7
Post 10 - Payload/1BL started
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 A0 - Panic - VERIFY_SECOTP_6
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post FC
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post FC
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post FC
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
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 1E - BRANCH
Post 20 - CB entry point reached
Post 21 - INIT_SECOTP
Post A0 - Panic - VERIFY_SECOTP_6
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post FC
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 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
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 F8
Post 70 - INIT_VIDEO_DRIVER
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post F8
Post 40 - Entrypoint of CD reached
Post FC
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post F8
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 A0 - Panic - VERIFY_SECOTP_6
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post FD
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post FC
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 70 - INIT_VIDEO_DRIVER
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
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 A0 - Panic - VERIFY_SECOTP_6
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post FC
Post F8
Post 40 - Entrypoint of CD reached
Post 70 - INIT_VIDEO_DRIVER
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post FE
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
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 F8
Post C0
Post F8
Post C0
Post F8
Post C0
Post F8
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post E0
Post C0
Post F8
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post F8
Post C0
Post F8
Post C0
Post F8
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
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 60 - INIT_KERNEL
Post F8
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post E0
Post FC
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post E0
Post F8
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post F8
Post C0
Post F8
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post F8
Post 80
Post F8
Post C0
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 A0 - Panic - VERIFY_SECOTP_6
Post 40 - Entrypoint of CD reached
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 60 - INIT_KERNEL
Post F8
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 40 - Entrypoint of CD reached
Post F8
Post 40 - Entrypoint of CD reached
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post 40 - Entrypoint of CD reached
Post FC
Post 40 - Entrypoint of CD reached
Post 10 - Payload/1BL started
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 80
Post F8
Post C0
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post F8
Post C0
Post FC
Post C0
Post E0
Post F8
Post C0
Post F8
Post C0
Post E0
Post F8
Post C0
Post F8
Post C0
Post F8
Post F0 - Panic - VERIFY_OFFSET_CB_B
Post C0
Post F8
Post C0
Post E0
Post 10 - Payload/1BL started
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 31 - FETCH_HEADER_4BL_CD
Post 33 - FETCH_CONTENTS_4BL_CD
Post 34 - HMACSHA_COMPUTE_4BL_CD
Post 35 - RC4_INITIALIZE_4BL_CD
Post 36 - RC4_DECRYPT_4BL_CD
Post 37 - SHA_COMPUTE_4BL_CD
Post 3A - BRANCH
Post 40 - Entrypoint of CD reached
Post 42 - FETCH_HEADER
Post 44 - FETCH_CONTENTS
Post 45 - HMACSHA_COMPUTE
Post 46 - RC4_INITIALIZE
Post 47 - RC4_DECRYPT
Post 48 - SHA_COMPUTE
Post 4B - LZX_EXPAND
Post 4E - FETCH_OFFSET_6BL_CF
Post 4F - VERIFY_OFFSET_6BL_CF
Post 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 60 - INIT_KERNEL
Post 61 - INIT_HAL_PHASE_0
Post 62 - INIT_PROCESS_OBJECTS
Post 64 - INIT_MEMORY_MANAGER
Post 65 - INIT_STACKS
Post 66 - INIT_OBJECT_SYSTEM
Post 67 - INIT_PHASE1_THREAD
Post 68 - Started phase 1 Initialization + INIT_PROCESSORS
Post 69 - INIT_KEY_VAULT
Post 6A - INIT_HAL_PHASE_1
Post 6B - INIT_SFC_DRIVER
Post 11 - FSB_CONFIG_PHY_CONTROL
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 44 - FETCH_CONTENTS
Post 45 - HMACSHA_COMPUTE
Post 46 - RC4_INITIALIZE
Post 48 - SHA_COMPUTE
Post 4B - LZX_EXPAND
Post 4D - DECODE_FUSES
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 5E - INIT_SOC_INT_COMPLETE
Post 5F
Post 60 - INIT_KERNEL
Post 61 - INIT_HAL_PHASE_0
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 77 - INIT_OTHER_DRIVERS
Post 78 - INIT_STFS_DRIVER
Most Fails(cumulative): 0xA0
Shutdown

Cant add Avatar to profile

$
0
0
I do what it says here: http://team-xecuter.com/forums/showt...ghlight=avatar

I then try to add a simple avatar and it give me " is_writable(): open_basedir restriction in effect." at the top of the page

Is this feature locked out now :confused:

I have tried on both firefox and Internet Explorer and get the same result.

Others have asked this question on this site but it seems no one answers.
Viewing all 6917 articles
Browse latest View live