New XeBuild and devkit unbricking?

[LEo]

"Devkit image building:
======================
This feature is currently considered Beta/Work In Progess.

A new image target type was added, "-t devkit" which builds 64M flash images for devkits. Currently untested,
building with a 00 filled CPU key will create a zeropaired devkit image that may allow one to boot a software
bricked devkit that one does not know the CPU key for and recover it to an operational state. By powering on
the console with such an image present, with a recovery DVD in the drive, the recovery software should be able
to create a new keyvault, re-pair the DVD drive to the new keyvault, and allow normal operation once complete.

Normal devkit image building when one does know their CPU key and thus has security files and keyvault should
work as expected.

Building devkit for glitch/jtag is also possible using the standard -t glitch/devkit methods. Sample ini
have been provided with this release, but will not work unless patches and files are supplied. Note that devkit
is not our focus, but was relatively easy and straight forward option to supply for those that wish to make
use of it."

Hmm wonder if this works? It seems it would fix a badflash kit but not a Pnet banned devkit.

[hacker360]

wow, does this work

[OnePlayer]

I would love to give this a try !

[halo3]

so this would fix wiped nand dev kits not pnet bricked kits, correct? :L

[LEo]

so this would fix wiped nand dev kits not pnet bricked kits, correct? :L

Specifically says "software bricked kits" so it seems like it...

[halo3]

Specifically says "software bricked kits" so it seems like it...

Doesn't hurt to double check.

[TheFallen93]

Amazing... Only took how many years for someone to figure out how to fix recovery "bricked" kits when they were never even bricked in the first place...

[KIWIDOGGIE]

Looks legit.

[adrianc]

That took a while.

-adrianc

[Repoman 108]

To clarify, this doesn't grant any special features (ie dashlaunch etc) for devkit users, right? It's just to replace your current (presumably broken) dev-orig image?

[Dabman]

so i don't understand
this software can rebuild KV.bin? - so can unbrick bricked console right? so aso can unban after rebuid kv.bin?

and what going on with retail, so You can convert retai to dev using it on retail? i mean dev - full dev to using recovery disk/remote recovery, not always this stuff

[nickcas]

It will build a dev image for your rgh/jtag but you won't be able to use the recovery software to upgrade.

[LEo]

Its been known for a while that you generate KV's everytime you recover... I think. Since your dvd key changes.

[halo3]

leo where did u copy that from?

[LEo]

leo where did u copy that from?

Xebuild readme...

[[cOz]]

LEo: recovery iso only generates a keyvault when the existing one is corrupt.

Fallen: ...

[halo3]

Xebuild readme...

so then it is public and works? pm me it?
@COZ what do you mean by generates a keyvault? lol like if you run a recovery iso on a system that is banned with a corrupt kv it won't unban the kit?

[Dabman]

Amazing... Only took how many years for someone to figure out how to fix recovery "bricked" kits when they were never even bricked in the first place...

yeah you and your leaked stuff... 9328 recovery and hvxdump etc...
and after all you call our leakers :)

anyway: good JOB! now alot of people can get kits back:)

[[cOz]]

halo3: like if you turn on your devkit and get xmas lights, recovering should fix it regardless of the problem... so long as it boots at least to the kernel and the dvd drive is operation enough to read a standard ISO disk.

Keep in mind, a temporary kv isn't issued to the console from whatever they use as a signing authority, it's created locally with an entirely different set of keys and is easily identified as such - and certainly won't change hardware details. Definitely not ban-evasion material.

[TheFallen93]

LEo: recovery iso only generates a keyvault when the existing one is corrupt.

Fallen: ...

Take any doner image, zero CB pairing data. You now have enough to boot any console that was bricked with my xex and run an iso recovery. It's been fixable since day 1... Knowing your cpu key is 100% useless on a dev, like I have stated many times.

Anyone who is slightly above the mentally retarded line should be able to figure out how to recover pnet bricked consoles. So lets see how many people really are not as dumb as they claim. I shall give 100 keyvaults to whoever has a working poc first.