Print

[iateshaggy]

http://www.ixtreme.n...x-tutorial.html

[iglitare]

as i allready said, i am no noob-idiot ...
off course the games are patched with abgx360 to the right version 13461

all the patched ap 2. games work flawlessly on all other consoles with LT+1.9 and 13461 dash (appr. 2 per day)

i managed to change the drives serial info via hexeditor.
Any chance to change the drives inquiry and identify data in the LT+1.9 firmware?

[iateshaggy]

the only thing that carries over to the new firmware is the dvd key.  you probably loaded the wrong ixtreme.

[iglitare]

no off course not. as i said before, i am no noob idiot.
how can i load the wrong firmware? JF is on auto... i flash about 10 drives per week, all works flawlessly. and of course i double and tribble checked it, its the right lt+1.9... and yes its 11461 dash, and yes all games are right abgx patched

The Problem is:
all 02510C drives SHOULD have same identity, inquiry and serial data.
That why LT+1.9 for 02510C don´t take the data from the original Firmware. Cause it SHOULD be all the same.

My Xbox hat some wrong or missing inquiry, identify and serial stored in its nand, and in the original 02510C fw.
I think thats is the problem.
When i then flash the LT+1.9, it autoloads the standard inquiry, serial and identify.
Then the xbox discovers this in any way, because it has stored different values (most missing) in its nand.
This stops AP2.5 games from working. I dont know how and why, but believe me, i checked any other scenario. That must be the solution
So i must change the identify and inquiry data in the lt+1.9 firmware for this drive.

here is the original 02510C firmware for this drive.
You will see, identify, inquiry and serial are partly missing:

https://rapidshare.c...76835/Dummy.bin

[iateshaggy]

this is easy, update dash, flash drive, patch iso.  if the game doesn't load, u screwed up one of those steps and until you swallow your pride and admit to yourself that you did something wrong, u won't figure out where you screwed up.  if you are smart enough to hex edit, you should be able to figure out how to check what dash you are on, start there.  that error you keep on about is nothing.  all drives from ms refurb are missing data and give that error, it has nothing to do with your situation.

[iglitare]

ok, i checked it again.

my AC:BC Ap2.5 game worked on a LT+1.9 elite with 13416 dash, so game is ok

the Xenon is on 13416, checked it, even inserted USB Update stick again (as is said and geremia approfed, the console came with 13461 dash and 02510c drive), so dashboard is ok.

flashed original firmware on the drive, all originals work. so key is ok.

flashed lt+1.9 (which shows error because of identify, serial and inquiry different) all original worked, all copies worked, only AP2.5 AC:BH wont work.

so i swallowed my pride and i am here again to ask for help.

i think ms has flashed partly missing inyquiry,serial and identify data in nand and original 02510C firmware, then i flash LT+1.9 with standard inquiry,serial and identify data.
Then, i dont know how, console compares the data from the nand with standard LT+1.9 data, its not equal, so AP2.5 wont boot.

Isn´t it the case case, that with 13461 das and spoofed Drive, AP2.5 games wont work?
So that could be the same here.

[iateshaggy]

run the disk in abgx, not another console.

[iglitare]

omg. why do you treat me like this? ok i know, there are many noobs and iditots out there, but i am not one of them. I know what to do.

THis AP2.5 copy of AC:BH worked on all 7 consoles i modded this week. All off course with lt+1.9 AND 13461 dash. so game is ok.

But just for you i checked it with agbx and guess what?
All ok and green "AP 2.5 replay sector is currently verified"

it would be very nice an d very helpy of you if you tell me whats the dae.bin is and how i get it and how i check it.

Also it would be nice if you tell me how to change identify and inquiry on lt+1.9

edit:

i just quickly soldered nand/SPI-flasher in and read nand out.
Extracted dae.bin with 360_flash_tool_v097, opened it with hex editor, but i dont know what to look for...:
https://rapidshare.c...3480162/dae.bin

[Khaine]

I'm not being funny, but just to eliminate the possibility of the patch not being quite right, or the drive being a bit off or something like that...

REPATCH the ISO and REBURN the game on a different disc. I understand you say it works fine in other consoles with LT+ 1.9... but do it anyway just to eliminate the possibility of a bad disc or something like that.

[blackopsftw]

QUOTE(iateshaggy @ Jul 6 2011, 01:20 AM)

this is easy, update dash, flash drive, patch iso.  if the game doesn't load, u screwed up one of those steps and until you swallow your pride and admit to yourself that you did something wrong,

Jesus christ, just shut up will you, he's clearly not inexperienced with this so stop being so condescending.

@iglitare, very odd issue you're having, it reminds me of what Tiros said about new dash checking inquiry string/barcode etc, but then the new f/w made all of those details the same so that theory went out of the window... or did it

[iateshaggy]

believe it or not, i am trying to help him.  it is just up to him to follow the steps to figure out what when wrong, or cry and bitch that he isn't a noob like the other 7589430758490321 threads about ap25 not working.

[iglitare]

QUOTE(Khaine @ Jul 6 2011, 03:23 AM)

I'm not being funny, but just to eliminate the possibility of the patch not being quite right, or the drive being a bit off or something like that...

REPATCH the ISO and REBURN the game on a different disc. I understand you say it works fine in other consoles with LT+ 1.9... but do it anyway just to eliminate the possibility of a bad disc or something like that.

? all works, all crappy odl copies work, i checked AP2.5 AC:BH with agbx, all ok, it works on all other boxes, no need to burn it again, and of course i use verbatim...

QUOTE(Weezy F Baby @ Jul 6 2011, 03:29 AM)

Jungle Flasher auto loads lt+1.1, btw. You have to manually select lt+1.9.

thats not right, try it.
use JF 0.1.84
if you load a pre 13461 firmware as source like
- LT+1.1 for Lite-ons
- 7,8,9 original LIte-On firmware
only then it loads lt+1.1 auto

if you open post 13461 firmware as source
- 02510C for lite-on
- all other post 13461 firmwares
it loads lt+1.9 auto

guys, i am no noob, neither an idiot. I flash min. 10 Xboxes a week.
I really know what i am doing.
The problem must be the missing inquiry, identify and serial in the origonal firmware, or better in the dae.bin in the nand of the console.

I guess this Problem is to complicated for 90% of the users here..
i see. sad.


edit:
@ shaggy, i checked all that you asked. Just believe me, i guess its because MS stored wrong data in the nand (dae.bin does not match standard 0251C firmware

[iateshaggy]

that missing info error happened on every liteon i ever did.  that is just how ms flashes drives.  they don't spoof either, they change the mobo's osig.  since they are ms, they can do that, until we get the sig keys, we can't.  reguardless of your experience, i have to treat this just like every other thread, if i showed u some of the work i have done for "pro's" u would understand.  post your jf log w/ key edited out, we know that isn't the problem anyway.  also, how long ago was this refurbed by ms.

[blackopsftw]

If you're convinced it's an Inq issue, have you tried hex editing the inq and serial informations to all FF?

[edit]just reading your post now

you can't alter/change dae.bin in nand on latest dash as it's signed, and yeah I think drive fw is encrypted as I can't find the inq strings with a hex editor :/

[iglitare]

QUOTE(iateshaggy @ Jul 6 2011, 03:48 AM)

that missing info error happened on every liteon i ever did.  that is just how ms flashes drives.  they don't spoof either, they change the mobo's osig.  since they are ms, they can do that, until we get the sig keys, we can't.  reguardless of your experience, i have to treat this just like every other thread, if i showed u some of the work i have done for "pro's" u would understand.  post your jf log w/ key edited out, we know that isn't the problem anyway.  also, how long ago was this refurbed by ms.

omg... and no, you are not right.
if MS delivers a box with 13461 das and 02510C firmware, its always there the identify, inquiry and serial, and its always the same, and always the same like in LT+1.9

And why the hell should i flash the drive for the fourth time? I flashed this drive 4 times, i flashed other lite-on all with LT+1.9
I even spoofed a benq with LT+1.1
always the same, reads originals, reads copies, wont read AP2.5 copy.
i checked, yes it is 13461 dash.
i checked, yes it was lt+1.9
i checked, yes game is agbx checked, yes with the newest patch

i checked, game works on all other consoles with lt+1.9 an 13461 dash.

Tell me how to check dae.bin.
That would be helpfull.
and please, please stop treating me like a noob.
What person are you, that you still, at this point, haven`t realized, that i know what i do?
Maybe you are the noob. The social noob  

@blackopsftw

thank you very much, at least one guy who try to help.
I guess, i just will accept it.
Its not mine, and its an old xenon...
Or maybe i send it to ihateshaggy the überpro who knows all and fixes all.
so easy, just update dash, pmt key and flash LT+1.9, patch games with agbx and it will work.  
shaggy, i think you know no more, thats the point, thats why you cant help.
But instead of just saying nothing, you call me a noob, and betray your ignorance.

that sentence from blackopsftw helped:
" it reminds me of what Tiros said about new dash checking inquiry string/barcode etc, but then the new f/w made all of those details the same so that theory went out of the window... or did it"

ihateshaggy with his agbx, JF logs and other noob stuff haven´t helped at all.
very sad.