Xell or Xellous on a Dev

Hi all

this is probably a stupid idea but is there any way to compile xell/xellous to run on a XDK. just thinking that it would be useful to any one with a 0022 pnetbricked kit like me

Thanks

 

Xell already does run on a dev...what do you mean exactly?
Maybe you mean with Jtag? I'm sure a lot of things would have to happen, and I don't think too many people on this board care about it either.

 

It would be intresting to try to launch xellous with the king kong hack, anyone ever try it?

 

id try it but my kit is bricked lol i just wanted to know if u could flash it like the jtag hack

 

Xell does not run on dev kits... Atleast not without recompiling it to use devkit memory addresses instead of retail...

 

:shrug: I've tried to tell you before...
http://www.assemblergames.com/forums/showpost.php?p=284308&postcount=27
Xell and Xellous run fine on a devkit. Please do follow your own recent post regarding keeping information accurate and... well I'll just say etc. and let others look it up for themselves.

What will not work with devkits are the retail payload and SMC hack (or in the case of KK, the retail shader exploit), which aside from being able to load xell have nothing to do with xell itself. Also, whether zeropair (getting around the cause of the 0022) is an open path and whether jtag port isn't being tied up by SC init would also be good questions, ones which I have no answer to.

 

The payload will not run, nor will the shader like you said. I highly doubt anyone here who want's to run xell has any idea on how to do so. Seeing as all they want is their cpu key, xell is pretty much useless. Getting your cpu key can be done in a few instructions, but I would imagine anyone that can get xell running on a devkit already knows how to do this. This just proves what I said before.

 

Actually it will, the shader does run when you run the kk exploit in retail mode.

 

How would one go about it in those few instructions then?

 

I really hope you know I mean cpu instructions, not readme instructions...

 

I did know you meant that, just thought it would be a nice share

 

cOz and I have already spoken about this. What he says is 100% true. Also if your kit was bricked by PN your CB has been updated meaning that the KK exploit will not work. On that note xell on a development kit can only be useful for people who were victims to XXXXXXXXX's bricking xex however this is a catch 22 without a method of flashing xell and booting it as a primary flash your development kit cannot inject a donor without the proper keys. A method needs to be developed for the development kit first and if made public could have some negative consequences. If your serious about repairing borked flashes without a backup then push for this research however this solution will not help the 0022 problem as it would have to be made public for a rebooter and that is a no-no.

 

I think the naming of people and accusations needs to stop, right now.

Kits affected by the flash-erasing xex can be brought back by flashing a backup.

 

Many people did not have a backup as they were not expecting to be victimized in large numbers.

 

Lets Keep On Topic, And Not Be Rude...

 

People with bricked kits probably wouldn't be able to run the KK exploit anyway... because you know... their kit was bricked.

 

Read.

 

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

pourriez vous expliquer comment faire ?? a un novice

 

afaik there was a internal KK shader for devs no?

 

no just patch a retail copy of kk with the shader, extract the iso, convert for dev, burn to disk, recover box as retail on 4548 run kk and there you go