I am not trying access partnernet I am exploring a devkit flash, dumping it, then researching it. Unfortunatly it never got that far so I must wait for my dev kit to arrive. I in no means am trying to replace devkits. I am just borrowing files for personal research.
oooo thats no fun. But I mean in reality you would have to have a big block jasper, OR XD Mod to allow for bigger NAND images. I believe it's very possible and would come for jaspers if anything, since they have the space on the NAND already. I don't care personally since retails can run unsigned xex's there really is no point. I doubt you'll be able to use RTH but you never know. It would be nice to see, I will say but doesn't matter to me cause I have a kit.
I know its not you its just the other retarted people who will try to connect to Pnet, I just want RTH and to debug apps if this gets out
There are many reasons why this recovery would fail. For one the recovery performs various test on the hardware, such as HDD, Audio, Usb, Dvd etc. When it realizes that the dev hdd partitions don't exist, it probally fails. Then it starts by blowing an efuse. After it uses some hardcore crypto to "recover" or reinstall the system files, generating random keys and Id's based on random seeds. Some of these functions I believe are dev kit only, so you would have to already be running the kernel. The bin files you are talking about are encrypted.
They do a lot more then format your hdd. If you got this to run and not crash on a retail console, you would pretty much brick it. Even if you stopped the blowing of the efuse and the check to make sure it blew, the flash image it writes is 512mb.
Even though dev kits (that I have seen) only have a 64mb nand ? Maybe I just haven't had one of the new jasper-like dev kits.
Look guys I strongly recommend against trying to make a devkit. Thats not what I was trying to do and hope thats clear to everyone. I don't support anyone attempting to do so.
Well from the reading so far I don't think you have to worry about that. If it comes it'll be from the people in the XBR, FB camps, unless it just comes from no where, the biggest issue is the nand size. But wouldn't matter on a jasper big block, or it could happen with XD mod, but I don't see that much need for it since retails do it all. But if retail fuses can be emulated, I don't see why dev's fuses cant. The normal recovery won't work any way because it wouldn't be patched with the rebooter stuff. If someone had xdmod installed with a 64mb card, go for it try it, worst case your reflash your card, best case is somehow it works unaltered, which I doupt, but there is no doubt it's going to fail on just a jtagged box, and you will have to reflash the nand. Now modding the recovery disk to install the latest hacked dash would be a good idea. :icon_bigg
I read around XeLL is being updated to do just that, Install new kernel revisions without having to use LPT/Jtag once installed. Could be hear say but I doubt they wouldn't have it so. When XBR and FreeBOOT release future revisions it could just be able to hook the network, I had a talk with certain parties and they said it wouldn't be hard. XeX booting and network hook should cover it. No need to go out of your way and litterly create a devkit.
Eh, but the total conversion is that much more fun if you can manage it. Someone figured out how to do it on the original Xbox, and you've posted in other threads on how you've made a hobby of converting various retail systems to their debug counterparts. With an exploitable hole, it's only a matter of time. And I suspect that matter of time will be sooner rather than later simply because whoever does it will make a name for themselves if they aren't already known. -hl718
I'm not doubting I can or cannot do it, I am just stating doing so would cause problems for Microsoft and other people who are collectors and people who go out of their way and almost lose their jobs to bring to people collectors items and developing tools at that. It just wouldn't be very practical if someone wants to do it... fine. Making it public is another thing.
Messing with partnernet or live is something I would not advise anyone to do, MS are very likely to easily figure out anyone with a retail box connecting to partnernet or anyone that is not running a stock kernel on either of the networks, not to mention the legal implications, including connecting to partnernet illegally (technically speaking, we are talking of hacking your way in a server you are not allowed to be in, this is called server hacking and is liable to prosecutions in most countries). Also MS are pretty keen at protecting live, and people using hacked boxes to run mods or cheat online, if found, will be banned, if not sued. In my opinion, people using hacked boxes should do it offline, or on their own networks.
This is key. There is nothing wrong with hacking your own box. There is a whole legal shitstorm that can fall on anyone who illegally obtains a connection to PartnerNet -- this includes with an illegit devkit. Remember, PartnerNet is a private, testing network owned by Microsoft. There are no privacy policies in play and as it is setup, every kit that connects to PartnerNet is owned by Microsoft so it has full access to do whatever it wishes to those kits. This is a *far* cry from Xbox Live where the end user owns their kit. If Microsoft wants to send out an update that wipes the NAND of every kit connected to PartnerNet on the thrid sunday of every month, it could. And there would be no recourse. If Microsoft wants to read any messages sent over PartnerNet or listen in on voice communication, it can. It owns the whole network, part and parcel. Connecting to the network without permission is a big risk. It may not seem like much, but it is. That said, I would still encourage anyone and everyone to use their system to learn. Tear it apart, hack it, learn what makes it tick and rebuild it. Get it functioning as a full devkit replacement if you can. But follow the advice quoted above and don't connect to PartnerNet if you don't want to take a large legal risk. -hl718
