Dual Booting Xbox Live Dash with Live Access and Reset Glitch for Homebrew Posted by XanTium | September 28 01:04 EST | News Category: Xbox360

From cygnos360.com: [QUOTE] Cygnos360 Forum Member “antman1″ has posted a video of how he switches between his xbox live dash and a homebrew image using a Cygnos360 V2. A tutorial on how to do this will follow. You can follow the thread in our forum here you can see the video here: [/QUOTE] Official Site: http://www.cygnos360.com

nice!!

Wow !!! This is going to be awesome.

Nice anthony

Before the noobs get excited, he soldered a DUAL NAND solution (iLLNESS called it a NANDWhich) this isn't a hacked kernel... this is 2 chips, 1 for retail (stock), 1 for homebrew.. most likely some switches

Still a proof of concept. I know little of the architecture, but I would think this opens up the possibility of Xbox 1 style modchips.

I help someone with this a month ago?

How is this is news.

I was hoping for something like to be done. Now you can get the best of both worlds.

Thats what i thought it was.
What else could do this?

Agreed someone in an IRC i am in did this weeks ago

This is done with a Cygnos360 v2 rev.e or lower. Hardest part will be finding the obsolete hardware.

Wouldnt it be easier to just have two xboxes?

Not everyone has the time to hang around IRC channels all day reading everything that's going on. It's good that X-S reports this, even if it is a week late. For most of us it's still news.

This sounds kinda similar to the xD-Picture card dual NAND mod you needed for JTAGs back when the JTAG exploit was new. I wonder if a similar set up could be used instead of the Cygnos360v2?

Either way this is great to hear . A dual boot slim with Live and Homebrew capabilities would be perfect!

Installed cygnos in a slim:

http://www.t3chline.com/images/IMG_0707.JPG
http://www.t3chline.com/images/IMG_0702.JPG
http://www.t3chline.com/images/IMG_0704.JPG

Dual boot ftw.

Modchip.ca has some of the older Cygnos360 chips for $15 if anyone is interested in diong this.
http://www.modchip.ca/store/product.php?pr...=284&page=1

That one will require you to lift the CE leg of your original nand or cut the trace to the CE. It is best to go for the Cygnos360v2 Rev E if you can. Make sure not to get rev F because it does not have dual nand. I have a strong feeling they will get back in stock soon.




Good Job Zoneout.

And you'll end up getting your ass BANNED in no time..

The system is entirely retail on, onboard nand side. There is nothing that will effect live play, this completely separates the hacked kernel from stock. There is no way for this to be detected on XBL if modified kernel is kept in secondary nand and disabled.

and really u shouldnt even need to read ur retail nand as there is no point using the kv from it! if you made a mistake and connected to live in glitch mode with a hacked kernel that would cause a ban on retail mode aswell

best thing to do on a dual nand setup is to use another fake ecc from the same model and hope a hacked kernel also has the hash check removed on kv like freeboot on jtag

I have one of these on order, and as soon as it's in my hands I'm gonna copy the board and put a stack of dead falcons to good use. I don't mind lifting a leg for an almost free dual-nand.

Is any of these emus you run leaving stuff behind on the retail HDD?

I have an old cygnos V2 unused sitting on the shelf. Now it has a use I guess!
I'll probably just sell it though, I don't use live.

My thoughts exactly.
Remember everybody freaking out when FSD left the shortcut on their HDD and then they didn't want to use that HDD on their Live console for fear of being band cos they'd had a faint wiff of homebrew

i use my hdd from my jtagged zeph on my stock jasper and have never had a problem on live.

Do you got to keep all homebrew and jtag games on a different drive?

Basically the emulators and homebrew right now are running off usb thumb drives and usb hard drives. So no they don't store anything on hard drives. Microsoft isnt looking for homebrew or any foreign files on the hard drive. The files on the hard drive from homebrew and such are not signed so the unmodified kernel will not be able to use the files and they will not show up if the signature is broken. The thing that can get your profile permanently suspended is if you use the snes9x emulator and get an obvious achievement that says "Unlocked Homebrew".

As of right now the Xell Reloaded doesn't touch anything having to do with xbox live so nothing on the system tell Microsoft anything about it being modded.

Once a hacked kernel does come out I do recommend using a donor KV when making the image for the modded nand because if it does accidentally talk to Microsoft it wont even look like the same console thus keeping the real kv from being banned.

This is actually just like the old Xbox1 days except it is more secure and safe in my opinion. The difference is that with the Xbox1 the tsop had just the flash that loaded unsigned files and such and it had a separate eeprom that stored the Keyvault and such. With the Xbox360 the TSOP/nand stores the KV and everything so you can have a different KV when switching between your homebrew kernel and the original.

That's not true. Homebrew achievements are not recognised by Microsoft since they technically don't exist. It doesn't matter if you unlock them with your regular account. I use the same account for all my JTAG activity as I do on my unmodified Live console. I've done this since the very beginning and never had a problem. Same goes for homebrew and games etc. Just about everything is stored on the same 120GB HDD which I switch between consoles. It's not any different to the Xbox 1 days.

Basically I was saying that it should be safe. as far as achievements I was only guessing that it might not be safe really to have achievements not recognized by Microsoft if you are wanting to be safe. I know they wont ban the console though for profile mishaps.

If you have a Jasper can you still do this even though the NAND is the wrong size? I would assume it is okay with a donor image since the code is hacked code, no? Anyone tried? I have an already banned Falcon I was going to use the NAND image from.

it should work fine. what you might have to do is copy the kv from the large nand though and inject it into a 16mb image in order to write it back after you make the ecc file.

I read somewhere the KV is fine as long as it matched in terms of having or not having HDMI. Might just give it awhirl and see what happens. Would rather use the banned KV just in case of accidents

I'm thinking you'd have to go about this like the XD-card hack where you swap a few resistors around to make the console "see" the original nand as 16mb and modify the original image accordingly.

To change the keyvault to a differnt kv like a already banned keyvault you would still have to get the original nand backup and cpu key. Then you open in 360 flash tool and inject the banned KV and fix the dvd key to match the drive, doesn't even have to be the same model motherboard. I made a guide on how to do so. I tested it out and it is good to go. By doing this you would be prepared when other things develop and you don't need to mess with your original nand.

This is fine, but what I'm talking about is the fact that none of the dual-nand set-ups support the big-block jaspers. For it to work you have to turn your console into a 16mb nand unit and the XD-card tutorial details this.

Yes, but where's the fun in that

I was curious about this as well. I know you can change things around so it is like a 16mb unit but can you convert the large dump to be 16mb and it still be like the original and safe for live? If so I dont see why you couldnt desolder the 256 or 512 TSOP after getting a dump of it then solder a 16mb chip in its place and putting your converted 16mb image on it then you could do the dual setup.

no fun but when you can pick up a rrod in some places for a fiver it works out a hell of a lot cheaper

I'm prolly wrong, but don't the BB jaspers only use the first 16mb for the nand image and the rest for storage?

I've never gotten my hand on one to try it out. You might be able to play with it and see. I have a bunch of boards with 16mb TSOPs laying around and that might help people if you figure that out. There really is no point in having a big block nand nowadays anyway. 2 saves and its full. lol

**EDIT** You could try dumping it like you would a 16mb tsop and then read it with flash360 and see if it looks good.

I am not sure if the full 16mb is all system information but you are right, when I did my 256 onboard JTAG I did everything with just dumping first 16mb, I think you can dump even less than that but it has always worked for me.

wouldnt it be easier just to use the 512 for live rather than desoldering the whole chip. then use a 16mb for the glitch? that way you are not messing with anything the system uses when in standard mode?

It would be nice but the problem is that the xbox360 motherboard has a different configuration for the 16mb nand and the 512/256 nands as shown in the pic below. You have to change the resistors to make the 16mb nand work (in this case the cygnos360v2) and that would make the onboard 512/256 not work anymore.


This is a pic from the XD Card mod guide written by "mastag21"

And this is a quote from the XD Card mod guide from "mastag21"

"You are basically switching 2 resistors and this makes the XBOX 360 think it is a SMALL-BLOCK system.
This does render the onboard NAND non-bootable. You may still be able to read/write to it but the
system will not allow it to boot because of the switching of resistors for SMALL-BLOCK."

Also I dont think it wouldn't be Live safe to go from Big Block to small block nand as long as the nand files are all there and look original to the console.

I was under the impression that changing the resistors crippled the onboard nand down to 16mb, not disable it altogether. I wish I could find that xd card tut again.

edit: nevermind, you answered my question.

edit2: wonder if changing the resistors and swapping the TSOP would work?

I seriously think it would work. without a doubt! got me wishing I had one just to try it out. lol

with the xd card for dual boot on slim it looks like lifting the ce pin or cutting hard traces isnt needed as iLLNESS over on xboxhacker used a 2nd nand piggy backed and found the switch works with just the bottom chip enable trace cut with 10k to pull up

this should work fine for cheap dual nand on slim

the xd mod is identical to the 'nandwhich'.. as well as the cygnos dual boot. they are all basically the same chips in a different package.

you COULD do a dual boot with 512mb jasper and XD/cygnos but it would require switching those resistors as well. your best bet is to nandwhich a second 512 or replace the 16mb on the cygnos with a 512...

if your intentions are to dual boot and be live safe i dont think its possible to switch a 512mb nand with a 16mb nand as the 512mb nand uses a 64mb kernel.

also,

<<<<<<<<<<<-------------!!!!!!!!!!!!!!!!!------------ iLLNESS, does not take credit for these discoveries there is already a large thread from the xbr/freeboot days where others have done this work. he is just resurrecting the info due to the response from other users.

dual nand 360 slim aka 'nandwhich'

not the clearest picture.. didnt have time for a video nor do i want to show how ghetto the switch is at the time being but its just a manual resolder to switch nands right now.

you can see top nand is wired to 3.3v through 10k pullup and to CE (not shown, underside). CE 10k resistor was removed from southbridge line.

i need to pickup a switch tomorrow to do the switching until i do some pic coding or begging to switch to xell on eject

has anyone the connection for this chip as i see they have only pads
0
1
2
3
4
5
6
7
gnd, on, off , vcc ,
v
u
t
q
p
o
n
m

k
a
u
ce 360

like ps2 modchip .. has anyone a schematic for slim console to this chip

The quick-solder points are the same as the V2, you just have to determine which pad corresponds to the quick-solder points.