So what you say is that the Corona v4 has a hard limit inside the actual SMC chip of 5 max resets?
I'd like to know that, because I always use xebuild to build my rgh2 images and I always say yes to patch_smc which will take the smc.bin firmware from nanddump.bin, patch the limit and write that to my target image.
I haven't done a corona v4 though.

Yes, by default the smc will halt after 5 tries.
I believe xebuild has some option patch_smc which will remove the limit from the smc.
Works for my falcon.

Thanks a lot for the replies, I really appreciate it.

There was some dirt between pin4 and 5 but it didn't cause the short.
I measured all of the pins, and none of them seem to be shorting to another.
Also when removing the epoxy I used the low-setting on my heater so it'll get hot enough to pry off the epoxy with a sharp knife.
However I doubt it was hot enough to melt the solder or disconnect the legs.
When I power it, the chip starts getting hot but it sometimes identifies though.
Also the fuses C6 and U2 and/or U1 get so hot, I can almost fry en egg on it.
So I only power it for like 5 seconds now.
I tried to find spots on the board where the shortage might be, but I can only think of the 3.3v spot of the power connector, because that's the only one I soldered the wire to (that goes to my drill).
But that one seems good.
So I guess the shortage is caused within the chip because the drill spot was either a bit off or too deep, in which case I can trash it.

If you want phonsey I can send you the board, if you want to take a look.

I'm out of ideas now, guess I'll wait for the TX new board to glitch it and get the dvd-key and one of those special replacement boards that only require the dvd-key.

Hey there I need some help.
Tried the Kamikaze on a 0225 winbond lite-on slim.

While they usually go fine, this one didn't cooperate with me.

I always use dosflash spi unlock under real dos-mode (win98 bootdisk) using my ICH9R in IDE compatible mode.
So I started drilling with the 3.3v (from the drive) connected to my soldering iron but it didn't unlock when I hit the spot.
So I turned everything off and powered my drive again and I notice that the drive board gets really hot including the MCIX chip.
Like I created a shortage within the drillin hole.
Now sometimes it identifies the flash but sometimes not.
When it identified I tried a SPI unlock with a small cotton stick and alchohol and said UNLOCKED.
But still the board overheats fast and I don't think I'll be able to dump without fixing the shortage.

I could drill further hoping to somehow disconnect the shortage within the drilling hole.
Or I could send it to someone with one of those xecuter pro devices which are capable of doing a full dump.

any ideas?

here's a picture of the drilling hole: http://chicken.better-than.tv/~mastag/hole.jpg

Lets wait for these changes to be included in xeBuild then

EDIT: After reading TX's frontpage, they'll be releasing special CR3-DGX addon for their new CR3 Pro glitcher that will be able to extract the cpu-key from 15xxx and newer consoles.
After you have the key, you can use it to build a freeboot image.
Too bad the addon only works with their CR3 Pro, must be a pricey deal.
I'd rather see a stand-alone addon for extracting the cpu-key, so I can use a cheaper board for glitching..

yeah, TX will soon sell a decap-kit for dumping the firmware.
Easy-to-apply acid for the average joe.

Same here, I only have jtag consoles atm.

Oh well they have to make a little profit right?
Having it RGH-only will keep the sales up.

But to be fair, I'd buy a Coolrunner and a Demon (once it hits the stores) if:

1. The Demon would properly reset the SMC so I can switch between my onboard flash and Demon flash (running Fusion) without the risk of getting banned from Live.
2. Fusion supports xellLaunch for running Linux
3. (Optional) Comes wil a nice sata-splitter so it would connect hdd A only when booting from my onboard flash and connect hdd B when booting from the Demon flash, to prevent my hacked kernel from poluting the hdd that's connected when I connect to Live.
Keeping everything separated (nice and safe:P).

Ah thanks phonsey!
I guess I should have done my homework first.
Only had to add a switch to pin6 and soldered a long kynar wire to mpx01 so I can ground it for a sec.

Rocking LT3 now

Hi folks,

I recently got a xbox360 with a Lite-On 16d2s which has been updated to 02510c by Xbox Live.
However it used to be a 74850.
For the 74850 I created a cable for extracting the key.



I extracted many 74850 drives using this cable and Dosflash64 2.0.

But it isn't working with the 02510c.
Could it be that MS has patched the serial exploit with 02510c?

If yes what other options can I use?

The folks over at Stainless who originally created Carmageddon 1 and 2 got the rights back to their franchise.
Now they're going to make a new game for PC and shortly after that a Xbox 360 and PS3 version will follow.
They're looking at publishing the game by themselves and therefor they've setup a kickstarter in order to do so.
http://www.kickstarter.com/projects/stainlessgames/carmageddon-reincarnation
If you like Carmageddon as much as I do then show a little support

Still struggling to run the first Carmageddon in Dosbox on my 360

Thanks cory1492,

So both TX and Team Squirt can shoot themself in the foot one day claiming it's unpatchable.
If MS changes it so it won't be able to extract they cpu-key anymore then we're still screwed.

From TX's page:



So if I would like to glitch my 14719 trinity, I can only glitch it to run xell -IF- I have my cpu-key.
And in order to get my cpu-key I need to use the XOR Hack right?

Correct me if I'm wrong but the XOR hack relies on the way they use RC4 encryption, now what if MS will update the way they use the RC4 encryption patching the RC4 vulnerability.
Then some day we end up with updated boxes which we are unable to extract the cpu-key...?

So whats the difference between this and xeBuild?

Offtopic question:

I was thinking of buying a dualnand reset glitch chip for my slim which is currently on Live with 14719.
Then connect a FAT32 formatted disk for storing homebrew like Snes360 (Hdd:\Emus)
I don't MS will ban me for having homebrew on a FAT32 usb disk since the original nand doesn't care about it (it will only look for videos, music and pictures).
But if I use one offline profile for my homebrew and one online profile for Live will I be safe?
Because some homebrew will make crazy achievements like Snes360 for example.
I can of course format a second usb device for use as memory storage and use that for my offline (homebrew) profile but that defeats the purpose of having a dualboot setup because I always have to insert it for running homebrew and take it out when I go on Live.
So do you guys think MS can take a sneak peak at the other profiles I have when I go on Live?

Ah I fixed it.
Had to go into NXE and run the wizard for kinect id.
Long live xeBuild

I was bored so I decided to buy the Kinect.
I have two boxes, one original slim and one jtag jasper512.
Now I use the jtag one in the living room because of snes360 and mupen360 etc and I plan to use the kinect on it.

So anyways the Kinect came with a code to download Fruit Ninja from xbox live.
I installed it on my original slim and used my transfer cable to copy the folder to my jtag.

My jtag runs the 14719 kernel built with xeBuild 1.01 update 1.
Then I installed the original 14719 update from MS to get the avatar stuff.
I also installed dashlaunch 2.32 with the contpatch = true set in launch.ini.


The game shows up in NXE and freestyledash.
However when I run it there is this strange issue.
When I slice the "Begin"-lemon, a screen pops up where I can sign into one of my profiles.
I have 3 offline profiles and the jtag box has never been on Live.
But no matter which profile I select, I always get the message that my box cant connect to Live (obviously).
So it asks me if I want to go back to NXE and do a connection test, when I say no it will still log into the selected profile and it will take me back to the title screen again.
But when I slice the "Begin"-lemon again it will still take me to the sign in screen however I'm already logged in.

So I tried signing into all profiles but no matter what I cant get passed the title screen.

Any ideas?

I've just installed ggBuild 0.33b kernel 13604 with Dash Launch 2.26 on a trinity slim.
It boots within 5 seconds most of the time.
However there are some issues.

I can boot xexmenu from a burnt cd-r.
But I cannot boot game backups at all.
fcrt.bin was taking in account when creating the ggBuild image.
I tried Call of Duty: MW3 and Sonic Generations.
They're properly written and verified with my iHas624, without truncating.
Also I've haved tested them on two other boxes with the LT2(.01) firmware flashed onto their drives and they work fine.

My second issue is regarding the 4GB memory module, it's a small pcb with 4GB flash that sits on a small connector nearby the nand.
The original NXE dashboard detects the 4GB just fine and it can be used for creating profiles and stuff.
But xexmenu nor freestyle dash won't detect it at all?
Only flash: and dvd: are detected.
I wanted to install freestyle dash with a few emulators onto the MU (snes360 ftw).

Well after seeing most chips on youtube.
I guess the Xecuter coolrunner would be the one with the best timings for slim.

I'd like to thank CoDeFl@sher, mprace and oc or their support

So I finally got the IDE female to male cable and hooked everything up...
But I already turned on my computer and accidentally connected the power supply for IDE to sata adapter upside-down (while my computer was running).
A spark and awful smell... and the IDE adapter is wasted

But since my slim drive was already erased I just connected it to the port on the back of via and flashed LT+ 2.0 using dosflash16 (since the via never worked on jf anyways).
I used mprace's dummy.bin to create the cfw, so thanks again.

After flashing it with the via card, I used my ich9r controller (in ide compatible mode) to lock the drive again.

It works and plays original discs, haven't tried any backups but I'm sure it works.
Now it's time to get it glitched..

Great work Blackaddr,
Really appreciate your work in perfecting everything for us.
Be sure to keep us posted bro!
You're definitely my favorite hacker/engineer.