new freeboot released runs unsigned xex's!!

[maximilian0017]

xcuse my ignorance and wickwack's guide is great BUT...just want to know do I need follow these seps first to get a nand with KV bin, i.e. the initial steps I need to do to get a nand that is ready to go for XBR.  Is it:

Wickwack's guide is for Linux flashes only, no need for it if you flash with lpt/olimex/pic

1. Make sure you have an Xbox that can run the Jtag hack and that the jtag hack resistors are soldered correctly.
2. Make sure you understand that you can not use live on this xbox unles you restore it to its original NAND and remove the jtag hack resistors(failure to do this correctly results in BAN!!).
1. Make sure you get a good original NAND.bin from your xbox and keep at least 1 copy in a safe place
(please read up on this!!)
2. Follow the XBR readme
3. If it doesnt work (red/green leds flashing) repeat step 2 with fresh XBR.bin and OriginalNand.bin but without copying the config block

[SoloStyl]

Here's a Question:

He mentioned "Virtual Fuses",  might it be possible to use these "Virtual Fuses" to regain the CPU Key from a Falcon with 8955 Kernel

I saw this   http://beta.ivancover.com/wiki/images/9/92/Dump32_Finished_and_List.png

and noticed it showed lines 3 and 4 are the same , and lines 5 and 6 the same as well.
could someone try to see if its possible that perhaps those fuses have NOT been burnt?

might be just a theory, but will ALL these Amazing skills and exploits going on, who knows right.

I have made the "HDD JTAG" just to un-cripple the HDD, but didnt do the 3 resistors since its a Falcon and on 8955. But would running the exploited 8955 Kernel on MY 360 allow me to do anything? 

just want to know what else I can do with my Banned 360, thanks to all     

[jelle2503]

you haven't read anything on this forum have you?

[damox]

you haven't read anything on this forum have you?

Do you expect him to read that ?

[SoloStyl]

Actual,
YES , to both those comments.

I posted because I'm interested, not trying to waste my time, nor yours.

A simple reply would be suffice, and as I stated "Theory".

Not too long ago, we didn't know we could recover the DVD keys through our NANDs, yet in these days, we can.

Just asking if it would be possible to achieve finding an alternative method for the CPU/KV thru a Dumped NAND from(similiar to recovering the DVD Key).

Not to mention, now we have the ability to bypass the XEX,PIRS,Etc. Might be a way in the FUTURE.

Perhaps, someone with more knowledge than all 3 of US COMBINED can look into it.
Here's to hope, and friendlier replies.   

[parasven]

we always knew the drive key was in nand and can be recovered with the cpukey. cpukey is not in nand

[le_uberfry]

Virtual fuses are obsolete. They can only be achieved if you can reboot into another kernel... but they're unneeded.

[MastaG]

I have a small problem with freeBOOT 0.2

13. The freeBOOT image can now be built. Open a Cygwin shell and change to the

       directory where you extracted the contents of this archive into. Launch

       the Python build script with the following parameters:



       > python build.py bin/<console>_hack.bin smc.bin

I cannot generate a patched smc.bin because the Cygnos 1.05 toolbox does not support the zephyr console yet.
So I've flashed firmware 1.01 into my Cygnos and didn't specify a smc.bin.
So my syntax was simply: python build.py bin/zephyr_hack_updxell.bin

It does boot into 8955 when I power on my console, but it doesn't boot into XeLL when I power on with eject .
Instead of booting into XeLL it just gives me a blinking red light in the lower-right corner.

Also with the harddrive limit removed, does it mean I can simply buy a 500GB laptop drive, put it into the enclosure and use the format option in the dashboard to prepare?

It works flawless now, I beta-tested the new patched smc for Zephyr consoles.

[SoloStyl]

ahh, ok thanks for the replies sirs.

I'm just hoping someoen finds a workarround someday.

Where can i BUY (if even possible) a 360 that can be modded to achieve the JTAG mod?

Bought 2 360's a couple days ago, but both were August '09s (returned 'em).

oldest i saw was at a PawnShop ($200 for an elite 120gb HDD) , but the guy said no warranty or returns once it left the shop.

didn't get it because who knows what version MoBo and Kernel are on it,(not to mention what if it was RROD already)

cant really trust Ebay.  Heck I'm willing to try a GoodWill or thrift shop , as long as I can find 1 that can be modded.

[Icekiller]

ahh, ok thanks for the replies sirs.

I'm just hoping someoen finds a workarround someday.

Where can i BUY (if even possible) a 360 that can be modded to achieve the JTAG mod?

Bought 2 360's a couple days ago, but both were August '09s (returned 'em).

oldest i saw was at a PawnShop ($200 for an elite 120gb HDD) , but the guy said no warranty or returns once it left the shop.

didn't get it because who knows what version MoBo and Kernel are on it,(not to mention what if it was RROD already)

cant really trust Ebay.  Heck I'm willing to try a GoodWill or thrift shop , as long as I can find 1 that can be modded.

try to get your hands on the Halo packs.. they are 'older'..

[vintage_guitar]

Would it be alright to substitute the NTE519 diode in place of 1N4148? I've got a few of these laying around and it'd save me a trip.

[keine]

What is needed to be done to adapt this patch to the larger 256 and 512 mB nand's?
Do you think this is in the works?
Anything that people with 256/512 mB nand's can contribute?

What is the general scheme of porting this to the 256/512 mB nand.

Obviously different offsets for the patches, since these files have different structures?
We will see the rebooter's for larger nand's correct?

Thanks.

[lenselijer]

from freeboot v0.02:

VI. What's Next
===============

   - support for Opus consoles and Jasper consoles with large flashes

So we'll just have to wait.
But maybe Bliep can do its magic just like with the xell for jasper 256/512mb versions.
That release is not even posted on xbins.org but the files are on the ftp

[keine]

I guess I'd just like to know the general flow of how they will develop the patches over to the new sized nand.....
(I like Assembly Language)

[undertoe]

Hi guys, no matter what I try I can not get XBReebot to work on my Xenon. My nand dumps are reported fine by degrader 1.1 and all dumps match. I have injected the KV and CONF data into the XBR image. Also tried only the KV info in XBR. But with each flash the xbox gives a black screen and after 20 sec RROD. Is there something Im missing?  I can reflash the original Nand dump back to the 360 and it works fine. I have also tried erasing the nand

Degraged 1.1B  Info on orginal nand

CB version 1921 LDV 1
CD version 1921
CE version 1888
CF(0) Version 6683 LDV 2
CF(1) Version 7371 LDV 3


XBR_Xenon_8955_1.bin     XBR image Im using

going to try XBR_Xenon_1921_8955_1.bin  ,   just found it!

[Arakon]

There's a 1921 image for xenon around. try that.

[undertoe]

Thanks! I just realized that second when looking for a new XBR image incase it was corrupted!  Feel stupid now.

[undertoe]

All good now, thanks to all the people that have made this hack happen. Soon it will be time to retire my many XBOX classics!

[ddxcb]

Like I say in a old thread "Here Comes the illegal Sh*t".

[littlestevie360]

wondering if someone could make an obvious pointer to what im doing wrong here,
setup is xenon with CB: 1903 on orig nand image
3x330ohm resistor jtag bridge
bad block at 8C remapped to 3FF following arakon's instructions

when ever i flash the XBR_8895_1.bin (with keyvault and config injected) i either get E79 or RROD with secondary error 0022,
ive gone over it numerous times and cant see anything that is wrong, in the case of when i consistently got E79 i flashed back the xell image which worked, flashed back the XBR image and again E79.

any insights to what i could be messing up would be appreciated thanks

EDIT: also trying to boot into the backup xell ends with an E79