I know 
But the only thing that mattered when i heard that was the concept itself. Since you are saying it's doable, great.
You know, like you said before about the "Lord of the hacks" or whatever they called it back then.
It was like some teams were just shooting s... in the air hoping somebody else would come up with something... 

A source from team Matrix said they would be releasing proprietary fw to be used on a regular freedom replacement board (1339  on ext. spi). Seems feasible.
Those 1175 are an easy mt replacement as well, no glue stuff.
Question is how to be sure you are not just buying a locked chip, the sellers on Ali-Express are kind of leaving it in a "gray area" so to speak.
One even said "removed from DG16D5S 1175 board".

Is there any reliable source for those 

There is a way... 



A friend of mine did this on a Corona V2 just for fun... We are kind of working on a sort of "blade" qsb to connect to the ball...

Credits to: Morenomdz from Madchipz

Did you guys read what GEREMIA just said about this 

HE IS the Kamikaze guy...

This is a totally different ball game... Please read the thread...

That's more like it 

I would say #1 for them 

Well, we know fcrt.bin is a must. Today on a 0225 dump for example, even on a partial dump (with a locked spi) you get enough data to build a cfw on a replacement board (at least on a lizard, i think jf is the same) without any issues.

But in the early days a partial dump on a 0225 would give you random "Play DVD" or worse. So we needed a full dump, hence we needed to unlock the spi anyway.

And since by the decap photos it looks that there's not much to drill in this one (there is one guy here who can prove me wrong hopefully in order to make a cfw there would be the need of more than just the key, unless MS/Phillips had screwed up this one severally (which i doubt since there is all this time span from the 1175 release with nothing new regarding cfw) and we know the fcrt challenges are there since we glitched every single one of them. They didn't even bother to throw that glue on this 1332 Mediatek.

Like the master said, the bullet was ready... Point taken, they do build good stuff. I have pretty much everything from them (and Maximus) but this time around everything regarding this hack, from them (and Matrix) started to popup after the x3key guys added the 1175/Hitachi support to their solution. And i remember that when the x3key was launched C4/Xecuter claimed it "unsafe", "easily detectable" by an update.

My point is, if their work is based on those guys work on the x3key (and i am not a x3key lover - for ME i think it's useless if you need a rgh to get it working), that would be a great slap in the face...

Thuth is, MS is not banning anybody right now (except the morons who insisted to play Halo 4 online or in their live profile), BUT that can change and if they find a way to detect something... you know...

Giving a taste of all those "great" new futures that only work online on a gold account (even internet explorer, wtf...) and THEM banning people in order to make a portion of them buy another console...

And Thanksgiving is just around the corner... like in 2009... 

edit: on top of that Geremia shed a light on something a lot of us had no idea. (i didn't, thanks). So is just a bit harder then ? lol

Well, now the cat is pretty much out of the bag, they kind of confirmed rgh will be needed anyways, so it looks that their work was based on the x3key guys effort to port their dongle thing into the DG5 and Hitachis, so looks kind of pointless unless you are a xbox live freak. Even though a dual boot on a locked drive is always an option... I'm still thinking how they plan to build the challenge response without fcrt.bin (since they claim all is needed is the dvd key)... More to come...

It only works in some cases, this fix is known for a while... John's remark about the input diode is correct.

This is the second time i posted it back in January. If you can read Portuguese 

http://forum.outerspace.terra.com.br/showpost.php?p=8992802&postcount=9998

If you're keeping the xbox on RGH you should build a 0272 FW with your right key injected (it doesn't matter if your original is a 0225/0401/1071 drive) and build your hacked kernel using "-a nofcrt" and that's it.
I will try this "regen" thing though... When i need it.

I was having random 0022 mostly on slims. For me what fixed the problem completely was this:

I use xebuild, so usually what we do is put cpukey + nanddump and that's about it right. Reading my logs one thing i noticed (full verbose) is that it was always warning about the "clean smc found", you need a hacked smc and "done" or something like that, meaning the program corrected it.

To generate my ecc i use that "gggggg-hack", and like most of the ecc programs it gives you an output folder with 3 or 4 files (CB's / image_00000000.ecc and SMC.bin).

What i did was i started adding this SMC.bin file in my xebuild "mydata" folder with the cpukey and the nanddump.bin. Never saw a random 0022 again. And in the logs xebuild states that "hacked smc found" or "glitch hack smc found" or something, and does nothing with it. I tried this because i was never having problems with ecc only, the 0022 always showed up after flashing the hacked kernel.

I really don't thinks that's a coincidence, i even recalled some customers to rebuild the hacked image and all stopped.

Hope my 2 cents help someone. Cheers

Yes it should, read the log it will say that blocks were remapped. Open your original nand on flash tool. There as well you should be able to see the remaps

10 k ohms

Yeah we know, but by now i saw (read)  that you already figured out what the problem is  I was going for the easy road...

Oh, and by the way if by "Sputnik PCB" you mean a Xecuter replacement PCB it will not work. One of the things it has problems with, is going from 9504 to 0272 in an update. Better use a "slave" (i use a pre-drilled winbond) slim drive with an unlocked SPI flashed with stock 9504 to finish the 13164 update. Then you can update to 14.699 and then put your drive with 3.0 back in it. But if that's still too much trouble, go option 3 

So it's better just to answer his question though... NO it's impossible to fix your console using your friend's xKey. Hope that helps.

Dude: He has the key and it's a Pre-08/2010 unit (9504 not 0225). No need for RGH here...

So, what is the problem anyway ? You have the key right... Is the problem a locked SPI now ? Do the Sputnik (MXIC) or Kamikaze (Winbond) to unlock the SPI again and you are good to go. Flash Stock 9504 back (with your key, of course) finish to update kernel to 13146 using a flash drive (assuming you're stuck in ther middle of the update), make a new dump of the drive (it won't be 9504 anymore, fw version will be 0272 from now on) flash 0272 LT+3.0 to the drive and that's about it (you can lock the SPI again, but if you are not going LIVE a soft lock (0x0C) will suffice.

Thank you very much, so basically  i was thinking of using an xecuter white pcb i have here to flash original then lock it 0x8c flick switch to wp=on , then mount an extra spi i got it off a benq drive on top of the existing one (bending pin 1)  to flash ixtreme to it, cut pin 1 from the board spi (or a trace) to install the spi switch in between. Only question i have is: i understand that the xecuter board wp switch will work on both spi since is connected to other pins, if that can create an issue regarding the onboard spi with the stock fw (if the switch acts in the added spi with ixtreme i was thinking of that i can just keep it hard locked as well until i need to update the hacked fw).

About the 10k resistors i was thinking of using 1/8 soldered directly on pin 1, so only wires go to the switch, i will not make it a joined switch with nand, will be a dedicated one just for the drive so there is the option of hacked fw on stock nand as well. The other switch will have nand, smc and glitch chip.

Please let me know if you think something is off on this train of thought.

thanks, so to update ixtreme in the future you can put the switch in the ixtreme position and reflash the spi ?