Just add the VID and PID into USBDEVS.c in the toolchain files .... I added the Afterglow PDP controller about a month ago , it's about 2 lines of code , and you will have to rebuild all your ELFs to run with the new information ... My suggestion is just to get a different controller that is already supported , it will save you some trouble ... If you add it I suggest getting ahold of Juvenal or Tuxuser from Libxenon and have them add it into the git so everyone can benefit from it.

 I'm curious as to why this is news? I glitched an Opus a couple weeks ago (before this news) using the falcon files and gliglis build.py, I know from experience with SMC/Jtag modding that there isn't a difference in them save for the lack of an HDMI port on the Opus and the / between the word Falcon and Opus in the information. The bootloaders are the same, and the SMC is the same, also the CPU/GPU are the same, and therefore the timings are the same. We all know each console has a different timing, it is semi specific to each MB revision Zephyr, Falcon/Opus, Jasper ,Trinity , but each console has a so called 'sweet spot', if there was a change made to the Jed file where it is '3 ticks' off, then it is a new timing for all Falcon/Opus motherboards, not specific to the Opus itself.

 I wouldn't say anything if I hadn't seen this exact story as front page news at 2 different sites .... Should I have gotten a big pat on the back if I posted that I glitched an HDMIless falcon?
 
 

 If want to fix a Lite-On you have to replace it with another lite-on. Spoofing is a thing of the past now. The dashboard checks for spoofed drives , and since a samsung also doesn't do Ap2.5 checks , and the lite-on does , the KV will see Lite-On and tried to run the correct commands on it for a Lite-On not a samsung. Spoofing only changes the OSIG , and some other pertinent info , but will not actually make it a Lite-On. If you spoof it I believe you will get a play DVD "error."

 In short no you cannot spoof a sammy into a console that requires a LO , at least not anymore. I don't do a lot of drive flashing so don't flame me for not knowing every detail but this is what I have understood about it recently.

 You do realize you have already started out badly here right? Making a 12625 rebooter image has no other purpose but to allow more online cheating, as their isn't a big enough change to anything for it to affect game play etc. Why not just play around with the already existing rebooter?

 Or better yet why don't you go back and read through Arnezmi , tmbinc's , robinsod , etc.. etc.. research over in important links and threads? the source for the original rebooter by Arnezami is still in that thread, it may not work in it's current form but their is enough other research that you can add to the information and come up with your own rebooter.

 The bottom line is this is a research and technical board it's not meant for spoon feeding se7ensinners who want to run cheat lobbies, what was your first question here? How do you get 12611 to load in IDA lol , I say again GTFO and i won't be the only one.

Edit: Don't be surprised when this ends up in the trash like your other thread or at the very least locked ... they don't tolerate this type of nonsense here PERIOD.

I believe the answer to your question is GTFO!!

 No one is interested in helping you get rebooters back online.

 I know im bumping this and it's actually pretty old. I wanted to give a little thanks to the folks who provided the original information. I have saved at least 3 drives for people who F%$%^d up trying to flash their 93's. This works like a charm. And those posting for a spoon feeding give it a rest, if you can't get it from reading the given information put down the soldering iron and take it to a "pro".

 You can still play on Xlink it just has to be Devkit VS Devkit. You can definitely see games though, as long as the person is on another devkit.

 Yea i am not the best writer, which is why i made the video tutorial...

 I like using DVD_tray open because it is a little easier to solder to than DB1F1 or the other (can't remeber the name FtU2 or something). With Aud_clamp you get a beep when you power on, and with both points swapped the center lights blinks also when you turn the system on... I have also found that if the system does a dashlaunch reboot from a crash and you have a disc in the drive with DVD_tray the drive will almost always open when it reboots.

 The first system i did this to someone had trashed both DB1F1 points and shorted something out on the RF circuit so the RF board didn't do anything but power the system on, it wouldn't sync a controller or anything and someone had definitely soldered on it, so i had to use both alternates. But i was still able to save the system and mod it.

 Nice to see someone else noticed my tutorial though.

 I don't really post much here but here is my opinion. To say that releasing information about an open source solution to 360 homebrew hurts the scene really doesn't follow any logic.  It would open it up to developers (who may be good) who are unable to get an SDK/XDK and give them a means to create homebrew for the 360.

 Also this would get us off of the MS code and therefore get the system off of Live and possible DMCA infringements. Every open source idea starts small. I don't how much Linux history everyone knows, but here is a little trip in time.. Linus Torvalds started his kernel as a terminal emulator for what was a somewhat popular OS minix , his terminal emulator turned into it's own  kernel and no longer needed minix and thus the Linux kernel was born. but because he didn't just reverse and hack someone elses code he was able to be open about it and retain licensing on it to this day. Now with the sharing of that information Linux has become a very good FREE operating system. Anyone can develop for Linux without any fear of legal issues.

 I can honestly see no harm in keeping people informed that their is an open source solution for the 360 homebrew scene.  Reading a wiki BTW doesn't give anyone the knowledge to become a libxenon programmer you still have to be a programmer to know how to use what you read.

 Ok , I tried this last night on my Jasper256. I extracted my SMC_dec with flash 360 tool. I ran the default command which i gathered was to move the ROL signal too Aud_clamp and fix the bug. I used sbtool to re-encrypt the SMC I didn't get any errors. I moved the ROL point to AUD_clamp and upon booting it runs for a minute the fan speeds up and then turns off. I have already moved it back and reflashed it , everything is fine. Any insight into what the problem might be. Do I have to build a brand new image to do this , as i only used sbtool to re-encrypt the SMC to the flash i wanted to flash to the system.
Thank you

 Put it in your internal HDD case if you want to use all 500 GB for a normal 360 drive. Or format it too fat 32 for use with FreeStyle Dash/Xexmenu etc. if you want it in the enclosure. their is no way too use all the space on a USB drive formatted with the NXE yet it will only use 16GB of it.

 My Zephyr does the e79 much less with a freeBOOT image. Also in regards to how i wire them I have a lot less e79 with them wired with the diodes at the Jtag port instead of at the end points like this.


 Don't diss the tape i am paranoid about a customer breaking those connections loose. I used glue and tape haha!!
The only time i see it do this now is when i change from VGA too Component or vice versa , or if it has just been sitting unplugged for a while. With the dash launch going to freestyle when it boots i don't notice it even happened unless i go back too the NXE for some reason like quiting a game and i have to reset everything.

 I forgot about deleteing .X0-lock from tmp i am just doing that i can actually work on it now my bad starting a new thread.

 Wow not the forum i thought i was in wrong place for this

This is what my screen looks like after it gets installed. I have been able to get it too work "normally" by editing my rc-default and doing some other small edits. Is their anyone who has not had this problem? as all machines have the same hardware , and i simply followed the instructions i don't see how i could be the only person who has this issue.
 I would like too know if their is a way too edit my rc-default file too get it too boot into a command prompt only? The only thing i have been able to do is cause a fatal error which makes the x-server not load therefore letting me run startx from another terminal , but editing the runlevel settings in rc-default did nothing it still loaded gdm.
 I don't want to hear any nonsense about type telinit  , that doesn't work with Ubuntu and everyone who would answer should know that already.

 I am not afraid of command lines , i only use windows for specific things so you can tell me in exact ways what i need to do , i have tried re-configuring the x-server with the same result. I followed the directions on the free60 site just because i know it is different when running linux on a game system.

 Also keep in mind that i can get it into the x-server without graphical glitches i just have to go about it a different way GDM will not load it correctly , even if i log in for the gdm window blindly , it is still screwed up when it gets booted into gnome.

 Any help is very much appreciated.

 E79 is usually related to your wiring. Make sure the diodes are facing the right direction. Make sure the one on the ROL board is not shorted to anything else on the ROL board , it probably wouldn't light up at all if their was a short. And check the Ft2U1 spot the most since it is tiny. When i do the Falcon/Zephyr/Jasper I reverse the diodes , i plug them into the Jtag port with the red side facing the port and the black line facing out , and solder it that way to the wire and solder the wire too the point instead of the stem of a diode maybe you already did it that way.

 I have had a few minor wiring problems on the first couple Falcons\Zephyr\Jaspers i did but now they are a breeze. I am not sure about the Jtag NT adaptor never heard of turning the 360 on too do a read but if that is what you do with that device i guess.
 
 Hope that helps

 I am not sure you can install the live cd... I think Ubuntu may be the only distro for the 360 HDD , it's the only one i have seen anything about. I don't think enough people are interested in Linux on the 360 yet

 Thanks entering the command and plugging it in as i hit enter worked thanks for the quick reply and not flaming me.

 The first one was correct here you go if you want a youtube video it is from my page should get you going on linux , you always have to use the ubuntu disc too boot the HDD installed version , but you can take it out once it is booted. I am a bad videographer but you can get the idea and their is a link to the free60 tutorial it takes you through step by step , i use a second HDD because you can't use 1 for games and Linux if you use it as a game drive it will overwrite your linux partition and the more you use it in linux it slowly gets rid of the data for the 360. The script from ep-comps is the one i always use most other links to it are broken.
http://www.youtube.com/jcplinux2008

 Yea but i flashed the wrong smc on the other 1 and it worked? Anyway you could point me to the place where i can find the information you mentioned in your post? So what exactly would it be doing then , if i had the wrong SMC in it is it then not powering the circuit because it is the wrong code? and the pins i need to short wouldn't that be erasing it therefore making it blank and in which case it would have no SMC on it at all?