Print

[krizalid]

QUOTE(Spegs12 @ Jun 4 2010, 10:18 PM)

Great app! Just an FYI Jasper BBs and Jasper 16s use the same SMC and you can download package with all of the SMCs on #freeboot on efnet. Does this perform the bug fix as well?

Well, having the additional option in the menu is going to help newbies and not ask: "No JasperBB support" before testing the app, and I'm sure they most didn't know about the SMC being the same.

Hey, I just learned this months ago, so many ppl out there still doesn't know.
Yes it does perform the bugfix since it uses smc_io.exe v0.2A by Blackddr.


Package doesn't contain any SMC files, but I coded so that you may extract SMC using SBTool.exe (debug).

[Drefsab]

QUOTE(SBEEZY @ Jun 4 2010, 08:19 PM)

i want my zeph 10/10 too but being that its a modded console i know that they fritz every now and then its something i can live with because of the capabilities of the system ( i might jtag my xenon so i dont have to deal with e79 but i love my HDMI box)

what secondary errors do your zephs get?

I will try them tonight I have a couple of falcons and a xenon jtaged so the Zeph's just sit there gathering dust I will put them on and make a note of the secondary error's.

[hundshamer]

So let me get this strait. If I patch my SMC do I have to move the jtag wiring. For instance to I move the point from the RF to the AUD-CLAMP? Is it possible to use this without rearranging soldering points? Finally, does updating the SMC makes the Jtag hack more stable (less boot errors)?

Sorry for the noobish questions but I want to make sure I have this correct before I try it. Just want some lamens terms.

[antisniperspy]

QUOTE(hundshamer @ Jun 6 2010, 10:50 AM)

So let me get this strait. If I patch my SMC do I have to move the jtag wiring. For instance to I move the point from the RF to the AUD-CLAMP? Is it possible to use this without rearranging soldering points? Finally, does updating the SMC makes the Jtag hack more stable (less boot errors)?

Sorry for the noobish questions but I want to make sure I have this correct before I try it. Just want some lamens terms.

You only have to move the point if you patched the smc for the new point. Yes you can patch the smc to fix the bug and then reflash and it should help.

[SBEEZY]

QUOTE(hundshamer @ Jun 6 2010, 09:50 AM)

So let me get this strait. If I patch my SMC do I have to move the jtag wiring. For instance to I move the point from the RF to the AUD-CLAMP? Is it possible to use this without rearranging soldering points? Finally, does updating the SMC makes the Jtag hack more stable (less boot errors)?

Sorry for the noobish questions but I want to make sure I have this correct before I try it. Just want some lamens terms.

my zephyr still e79s but its not as bad as it used to be i might open her up now and  do the aud clamp fix

[hundshamer]

OK, from what I can tell this will be an awsome tool! Thanks.

Now I have dug a little into it and from looking at the options you can use the Open_Tray for TMS (RF solder point) so all the work can stay on the top of the board (no need to remove mobo and easier to solder to as I have the DB1F1 in place). Has anybody tried this? If so, does it solve boot speed and/or ROL errors?

[krizalid]

QUOTE(hundshamer @ Jun 6 2010, 09:10 PM)

OK, from what I can tell this will be an awsome tool! Thanks.

Now I have dug a little into it and from looking at the options you can use the Open_Tray for TMS (RF solder point) so all the work can stay on the top of the board (no need to remove mobo and easier to solder to as I have the DB1F1 in place). Has anybody tried this? If so, does it solve boot speed and/or ROL errors?

I have and It works great, but if you do it on a Zephyr, your DVD Drive will always eject during boot.
This does not happen on my Falcon and I don't know about jaspers, since I don't have one to test.

Another option is to use TMS=ARGON_DATA (rf_board) and TDI=OPEN_TRAY on Falcons and japsers, and they will work fine, except for the charge kit issue.  

[hundshamer]

Thanks for the reply. I have a Falcon and have had little sucsses soldering to the bottom of the board. The only issues I have is the ROL errors and one that I don't know if this will solve. I have a Media Center remote. It has a regular power button and a Media Center button that ,when unhacked, would launch the 360 directly to Media Center. Now with the hack in place, it turns on the 360 only the center light and fans power up, but no audio/video. No error lights or anything. I wonder if it has to do with the SMC and/or the original wiring messing up the boot sequence, or if it is an error with freeBOOT 0.032 with Xbox 1 compatability running on a single NAND.

[SBEEZY]

QUOTE(Drefsab @ Jun 4 2010, 09:29 AM)

Id be very intersted to see your results on that, I have a couple of Zephyr's that rrod on boot, I used a 330 resistor in place of the jumper wire that helps things but would love to get them booting 10 for 10 etc.

well results are in 10/10 on hdmi 10/10 on component/sd cables dre get on it man u and your zephs will be makin sweet love after u do the aud_clamp fix

[krizalid]

QUOTE

Thanks for the reply. I have a Falcon and have had little sucsses soldering to the bottom of the board. The only issues I have is the ROL errors and one that I don't know if this will solve. I have a Media Center remote. It has a regular power button and a Media Center button that ,when unhacked, would launch the 360 directly to Media Center. Now with the hack in place, it turns on the 360 only the center light and fans power up, but no audio/video. No error lights or anything. I wonder if it has to do with the SMC and/or the original wiring messing up the boot sequence, or if it is an error with freeBOOT 0.032 with Xbox 1 compatability running on a single NAND.

hmmm, cannot know if I don't have it on hand, what I do suggest is updating your SMC using only the bug fix only and not patching any I/O ports.

Try that first, if not, than I suggest you change your wiring.

[gui1e]

Tried the bugfix on my jasper 256 and just get blank screen (freeboot) reverted back to old smc.

[Definitely Wapner]

Got a quick question and scenario for you guys:

Initial Setup: Zephyr CB 4580 flashed with falcon freeboot .32 --> the only one that works; kept giving random errors

The fix: ran "update my SMC" and applied both patches to the smc for my falcon freeboot. Keep this in mind, when I ran the program, I pulled the smc from the falcon freeboot when it asked me which mobo revision I had.

The NEW Problem I changed the wire config, flashed, and get a boot with no picture.

Questions

1. When using "update my SMC", should I have run the patch for the ZEPHYR motherboard?

2. Should I only apply the "AUD_CLAMP" fix and not both of them

3. Should I try flashing with Zephyr Freeboot with Patched SMC now?

Anything you guys might have done that worked, please let me know. Thanks

[Travulese]

How exactly do I use this tool? I have a freeboot.bin (16,896kb) that I made it has my cpu key and everything in it, I put it in the smc_updater_v0.2 folder, I then opened up DumpSMC-fromANY_image and chose my freeboot.bin image and chose falcon which is my chipset type and it created Falcon.bin(12kb). I then went to update-my-smc! selected falcon.bin and then selected 3 to change the jtag points to aud_clamp and tray_open. The Falcon.bin is now 16,896kb. I cannot open it with 360_flash_tool.194 or anything.. did I do this correctly? can someone please help me out Im stumped and dont know if im doing this correctly.

This post has been edited by Travulese: Jun 8 2010, 11:19 PM

[hundshamer]

QUOTE(Travulese @ Jun 8 2010, 05:17 PM)

How exactly do I use this tool? I have a freeboot.bin (16,896kb) that I made it has my cpu key and everything in it, I put it in the smc_updater_v0.2 folder, I then opened up DumpSMC-fromANY_image and chose my freeboot.bin image and chose falcon which is my chipset type and it created Falcon.bin(12kb). I then went to update-my-smc! selected falcon.bin and then selected 3 to change the jtag points to aud_clamp and tray_open. The Falcon.bin is now 16,896kb. I cannot open it with 360_flash_tool.194 or anything.. did I do this correctly? can someone please help me out Im stumped and dont know if im doing this correctly.

From what I understand you extracted the SMC correctly. Now you should have freeboot.bin and falcon.bin. When you run update-my-smc! point it to freeboot.bin not falcon.bin. Then the freeboot.bin will now have the patched SMC.

[Travulese]

QUOTE(hundshamer @ Jun 8 2010, 07:02 PM)

From what I understand you extracted the SMC correctly. Now you should have freeboot.bin and falcon.bin. When you run update-my-smc! point it to freeboot.bin not falcon.bin. Then the freeboot.bin will now have the patched SMC.

Thanks, Ye I figured that out.. I was just getting confused.. thx for the quick reply.. appreciate it man.

can you use the freeboot image that you used to install to your nand and run freeboot with, Like I took the smc out of my freeboot image that I created with jtag tool 1.72 so im using the image that I had flashed into my nand and actually had it working but then the ft1u2 trace fell off and I got screwed and then I did another one and it fell off, the worst of luck.. basically Im asking if the freeboot.bin that I created using jtag tool 1.72 is fine to extract the smc and then inject the new smc into the file using smc update v0.2

This post has been edited by Travulese: Jun 9 2010, 12:49 AM