Repairing Recovery bricked Devs

Do not post in this thread if your kit was bricked by Partnernet. I believe I have found a solution to repair Devkits that were hit by the bricking recovery without a Backup of their NAND. Please contact me at
AIM: Shad0w LAG
MSN: Shadowlag@hotmail.com

 

i was going to post asking if someone knew how to fix this yesterday :S

 

No one really ever thought of extracting config/kv and injecting into a same model nand....

 

Leo you need the KV or CPU key from the original which means anyone who has such would need have their backup. Also with this method if theory becomes reality you will not need a KV. I know of people that this actually worked for.

 

hello

I sent many mail but no response from you??

 

Might be busy mate.

 

hello

then this solution, you can connect us thank you, or is it a false hope

 

any console bricked by the "9328.9" fake recovery cant be repaired without its origernal nand as the pairing data is lost when the fake recovery is run

 

9328.9 must die.

 

Recovery of the subject
is there a solution for a devkit which debricker boot in 0022, I have access to the nand, with my USB module

 

imo the only real way to bring those bricks back are to get XeLL going at boot by perhaps using customized files to work with XDKs. i mean without a cpukey i dont think there is really anything anyone can do to recover.