Post by: iateshaggy on July 05, 2011, 05:40:00 PM
Post by: iglitare on July 05, 2011, 05:50:00 PM
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?
Post by: iateshaggy on July 05, 2011, 06:00:00 PM
Post by: iglitare on July 05, 2011, 06:16:00 PM
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
Post by: iateshaggy on July 05, 2011, 06:20:00 PM
Post by: iglitare on July 05, 2011, 06:40:00 PM
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.
Post by: iateshaggy on July 05, 2011, 06:48:00 PM
Post by: iglitare on July 05, 2011, 07:11:00 PM
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
Post by: Khaine on July 05, 2011, 07:23:00 PM
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.
Post by: blackopsftw on July 05, 2011, 07:30:00 PM
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
Post by: iateshaggy on July 05, 2011, 07:35:00 PM
Post by: iglitare on July 05, 2011, 07:38:00 PM
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
Post by: iateshaggy on July 05, 2011, 07:48:00 PM
Post by: blackopsftw on July 05, 2011, 07:53:00 PM
[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 :/
Post by: iglitare on July 05, 2011, 07:59:00 PM
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.
Post by: iateshaggy on July 05, 2011, 08:18:00 PM
Post by: iglitare on July 05, 2011, 08:27:00 PM
ihateshaggy.
i have a console shop, and i do it, and only it, for living.
And i live good with it.
I am a professional electronics technician and i know how to solder.
You could show me 100 pics like this, i dont know what its have to to with this issue.
It´s so far solved.
You haven´t helped this time. Looks like it was too complicated for you this time.
No Problem, there are still thousand noobs with thousand noob issues out there you could help.
Here you have obviously nothing interesting to say.
Post by: Takashi on July 05, 2011, 08:29:00 PM
QUOTE(iglitare @ Jul 5 2011, 09:27 PM)
It´s so far solved.
it is?
Post by: iateshaggy on July 05, 2011, 08:51:00 PM
Post by: Weezy F Baby on July 05, 2011, 09:24:00 PM
Post by: smuddge37 on July 05, 2011, 09:56:00 PM
Post by: iglitare on July 06, 2011, 07:31:00 AM
@ Weezy F Baby
for what do you need the log?
to check that i really autoloaded lt+1.9?
i did it 5 times with the original drive, 1 time with other lite-on, 1 time i spoofed a benq in it.
And it was always the right lt+1.9 (worked flawlessly in other consoles with ap2.5 an 13461 games)
So please tell me why?
I am no noob who loaded lt+1.1 or old ixtreme, or has not the 13461 dash, or hasen´t agbx patched ap2.5, nor did i made other "noob" mistakes.
Please tell me why you need the log?
But ok, for christs sake here is it (before i -lo-erased and flashed i got this error "drive serial, identify and so on does not match with firmware"
"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.84 Beta (250)
Session Started Tue Jul 05 20:06:02 2011
This is a Wow 64 process running on 4 x 64 bit CPUs
portio64.sys Driver Installed
portio64.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 1 Com Ports.
Found 8 windows drives A: C: D: E: F: G: X: Z:
Found 1 CD/DVD drives D:
Working folder 'C:\Work\XBOX_Flash\xxxxxxxxxxxxxxx_lite-on_core' created.
Drive is Lite-On..
Sending Vendor Intro to port 0xCF00
Serial flash found with Status 0x52
Extracted drive key passed Verification !
key returned: 859248310E4FE9166EBFB8E53C9D4D23
Key data saved to C:\Work\XBOX_Flash\xxxxxxxx_lite-on_core\Key.bin
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 30 32 35 31 30 43 41 30 - 41 30 20 20 20 20 20 20 02510CA0A0
0030: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
Inquiry String saved to C:\Work\XBOX_Flash\xxxxxxxx_lite-on_core\Inquiry.bin
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 30 32 35 31 30 43 20 20 - 00 00 00 00 00 00 00 00 02510C ........
0030: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 20 20 20 20 - 20 20 20 20 20 20 20 20 ....
0020: 20 20 20 20 20 20 20 20 - 00 00 00 00 00 00 32 30 ......20
0030: 31 35 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 15C0 LPSD GD
0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2
0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..
0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......
0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 00 00 ............h...
00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00B0: 20 20 00 00 ..
Identify String saved to C:\Work\XBOX_Flash\xxxxxxx_lite-on_core\Identify.bin
0000: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
0010: 20 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 30 FF FF ............A0..
Identify String saved to C:\Work\XBOX_Flash\xxxxxx_lite-on_core\Serial.bin
Dummy.bin file saved to C:\Work\XBOX_Flash\xxxxx_lite-on_core\Dummy.bin
Loading firmware from buffer
Inquiry string found
Identify string found
Drive key @ 0xA030 859248310E4FE9166EBFB8E53C9D4D23
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: PhatKey Extract
Key added to database
Auto-Loading firmware file C:\Work\JungleFlasher\firmware\LTPlus-025v1.9.bin
MD5 hash: 71cfb6569fd42a1d4eb243dbd4d3b159
Genuine LT plus v1.9
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: LT-Plus 1.9
Spoofing Target
DVD Key copied to target
Target is LT - ID strings not copied to Target
Target rev is LT 02510C, serial info not copied
Target Key verified, thanks C4eva !
Proceeding with LO-Erase
Sending Lite-On-Erase request to port 0xCF00
..............
Drive returned Status 0xD0
.........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
Sending Chip Erase to Port 0xCF00
Erasing:
Writing target buffer to flash
Writing Bank 0: ................
Writing Bank 1: ................
Writing Bank 2: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !"
Post by: digipimp75 on July 06, 2011, 08:00:00 AM
Post by: Takashi on July 06, 2011, 09:03:00 AM
QUOTE(iglitare @ Jul 6 2011, 08:31 AM)
i did it 5 times with the original drive, 1 time with other lite-on, 1 time i spoofed a benq in it.
Why did you spoof anything?
Anybody paying real attention in this game knows that's a horrible waste of time,
even more than pasting jf logs.
Post by: iglitare on July 06, 2011, 09:08:00 AM
But anyway, a slim with 0272 drive does work with 9504 LT+1.1 even not spoofed and new dash and AP2.5 games.
NExt i check Hitachi an samsung with LT+ NonSpoofed with only key
wheren´t there any old xenons outh there which dont have a dvd-drive check?
I mean, these boards accept any drives with out spoofing.
I remember, there where something.
Post by: Dra60nSlayer on July 06, 2011, 09:11:00 AM
if an original AP2.5 does work... everything you need is in your original firmware.
Post by: Defosho on July 06, 2011, 09:48:00 AM
iglitare: your dae.bin is version 5 from dash 12611. This contains challenge set 1 for AC:B which is why your challenge set 2 patched backup won't boot.
You need to create backups with the older challenge set 1 patches for the AP25 games to boot. You can find some older patches here.
Your console probably came back from repair with 12611 dash installed. When you updated to 13146 the dae.bin did not get updated which is known to occur from time to time. Similar behavior occurs with the old AP25 bypass method.
The dae.bin will be replaced with an updated version when the next System Update is installed at which point current backups will need to be re-burned if the challenges change.
Post by: iglitare on July 06, 2011, 12:31:00 PM
it was really it.
I have a xbox with 13461 dash AND ap2.5 challenge set 1 activated! Not challenge set 2 as expected.
I don´t think this is very common...
Patched AC:BH with old patch and ppf-o-matic and it now works!
Thank you very much!! And i will thank all others, too.
Especially those who havent treated me like a noob...
edit:
funniest thing of all:
i just had a call with the owner of the xbox, that sent it to me for repair. Or better, he sent it too me, for that i should send it to MS...
I told him his console is ready and told him about flash problems.
Guess what. That guy never wanted a flash
all for nothing!
Post by: blackopsftw on July 06, 2011, 04:44:00 PM
Post by: Khaine on July 06, 2011, 05:25:00 PM
Only console I've ever seen do that is my black elite because it's got one of the drive types that didn't get updated with dash 13146.