No cables at all, its fine mate anyway. I wanted it just for safety and to check out and get more info on these strange white S XDKs
I have one too, engineering sample with the clear sides to it. Odd how it has no dev headers/pinouts on the board. Went over it with fine tooth comb thinking I would find some motherboard modifications. First thing I did is start by eject and expected to see Xell Reloaded pop up. Oddly and thankfully enough I saw no such thing.
Yeah, with the microwave beep startup haha these are definatley anomalies. Really dont know what they could have been working on at such a late stage.
Yeah the sound effect is strange, even stranger they chose to have both eject and power up be the same. I thought maybe the soley white S were demo kits of sorts for something like E3. The clear/white ones don't make any sense considering the radio FCC shell is inside the clear shell so there isn't really any point for it to be clear. Looks awesome though if there is one definite.
does Hvxos or the dev kit xell launcher work on the dev kit, that is the only other thing to get access to the nand, or use the 4gb r/w kit. the nand spi wont work on the 4gb models.
I've got HvXBootOS 1.0, never used it, but that is outdated as well I think, the video in the readme shows 20353.2, also before slim XDKs were around. If it does work, how do I dump in xell? Cheers EDIT: Found this thread which says it works up to 20353 - 20500 :/ (I only have 20500.1 on iso, and Im not sure if iso will f* up the system / flash (also, highest disc recovery I have so no recovering from above that) unlike how the remote recovery just fails, although remote does make the kit end up on the recovery screen then when I have to power off, it crash dumps xboxkrnl.xex http://www.assemblergames.com/forums/showthread.php?45194-Linux-on-Xenon-Dev-Kit
Ive had that error on a phat console before, it was something to do with the format of the drive... or in your case the the onboard memory. In the xdk dashboard settings there should be an option to toggle the internal memory on and off. Try disabling it and running the recovery again. Let us know how it goes, too many threads like this end up resolved but without the solution documented for anyone experiencing the issue in the future. Fingers crossed!
Thanks mate, tried it, but again, just crashes and gives me the same error. It recovers to the latest recoveries just fine. I'm maybe thinking its actual physical hardware limitations somehow, these are odd kits. Did you ever manage to dump you white S's NAND? It wasnt 4GB was it? :/ EDIT: Also just tried 20675 and that failed too :/
Have you run xbdmrecovery.xex on your kit? If so it'll cause errors with remote recoveries until you first recover with an iso based recovery.
Not ran xbdmrecovery.xex, I did run InternalDriveLinker.xex? Are there any .iso recoveries available on a recent recovery? I could use an .iso if it was high enough, but nothing that low works EDIT: Found 20871.2 and 21119.10 isos, Ill try 21076.11 remote, and if that works I guess 21119.10 should work 21076.11 works, I'll download 21119.10 now and try a disc recovery
Yeah try an iso recovery and then re-recover with the newest remote you have later. Hopefully will do the trick. I have downgraded a trinity XDK in the low 9000's before without an issue. But as far as Corona, mine came with a 21000's recovery so I never downgraded below that. Currently running 21256.3
Isnt there a way to tell if youve messed about with the flash? Like an extra file? And ooo very nice .3 EDIT: Also, this 21119.10 iso has a default.xex.orig somehow when the others dont, do I just delete it or leave it in?
That seems suspicious as if the xex had been resigned for devkit use by X360gamehack which makes no sense. Delete it I suppose since the kit wont read a .orig extension.
Really dont know which one to believe, Ill have to compare with another xex soon but they are practically the same Except for Allowed Media .xex xex.orig Ill report back
An original xex comes back same as the .orig, I guess it will be fine just to delete the xex and rename the default.xex.orig to default.xex within the .iso Pretty glad I checked now haha
Tried using the 'fixed' iso on my jasper but it just black screens, but I removed the HDD because I know it formats it doesnt it? Does it matter wether its on or off? The jasper also has 512MB on board memory. Going to try and use the original iso now EDIT: Original, again, black screens :/
