|
New JungleFlasher v0.0.43b released - Old dump methods flawed! Possible Fix.
|
|
|
drybrdl
Junior Member
|
28. January 2009 @ 08:43 |
Link to this message
|
|
bhetrick, when you load a .26 dummy in .43 what does is give you in the serial information?
|
|
Advertisement
|
|
|
|
AfterDawn Addict
|
28. January 2009 @ 11:06 |
Link to this message
|
|
When I load the .26 dummy in .43, what do you mean "serial information"?
Under the FirmwareTool 32 tab it only shows the source and target info. Where are you looking?
|
|
drybrdl
Junior Member
|
28. January 2009 @ 12:30 |
Link to this message
|
Originally posted by bhetrick:
When I load the .26 dummy in .43, what do you mean "serial information"?
Under the FirmwareTool 32 tab it only shows the source and target info. Where are you looking?
Tick the box that says Advanced View 
This message has been edited since posting. Last time this message was edited on 28. January 2009 @ 13:08
|
AfterDawn Addict
|
28. January 2009 @ 13:45 |
Link to this message
|
|
|
|
drybrdl
Junior Member
|
28. January 2009 @ 13:50 |
Link to this message
|
|
Thats the target, its the source you need to look at
|
AfterDawn Addict
|
28. January 2009 @ 14:12 |
Link to this message
|
Ah hell... alright, here's what it looks like in both .26 & .43.
|
AfterDawn Addict
|
28. January 2009 @ 14:13 |
Link to this message
|
|
That is the same drive, read with both versions of Jungleflasher. So, it still looks like both .26 and .43 read the same info.
|
|
drybrdl
Junior Member
|
28. January 2009 @ 14:15 |
Link to this message
|
|
very similar to mine, lots of FF FF FF , id say that confirms theres info missing if its the same in .26 and .43 wouldnt you?
Can you load a dummy file dumped using .43 please so i can compare, i dont have one :(
This message has been edited since posting. Last time this message was edited on 28. January 2009 @ 14:17
|
|
Donaldo
Senior Member
|
28. January 2009 @ 14:40 |
Link to this message
|
|
yes mine looks nearly identical lots of FF's...
BTW on the target drive serial tab... you can see where it is copying the first bit from the source, the D608CG..... but where is it getting the rest of the data that follows those characters?? is it randomly generating it or is it the same for everyone ??
using the ix15-liteon.bin as the target my data following the D608.... string is::
8G31075017E414XXA0..S4P881400000114443
after i did that i exited JF and loaded the files again and it generated the exact same string of characters so it must not be completely random
|
AfterDawn Addict
|
28. January 2009 @ 14:40 |
Link to this message
|
Those 2 pics are of the same drive, dumped with .26, and the .26 dummy opened with both JF.26 and JF.43.
This pic is the same drive, but dumped with .43 and the dummy read with .43.
It would appear that .26 does, in fact, seem to be missing data.
BUT... looking at this and the logs I posted in my previous post, this serial data does match the .43 log... and the .43 serial data matches the .26 log.
So this just adds to the problem. The log from JF.26 clearly shows that the data was read and is there. So this comes right back to whether it's a coding problem and JF43 is just reading old dummy's wrong.
|
|
drybrdl
Junior Member
|
28. January 2009 @ 14:48 |
Link to this message
|
|
yes but .26 also shows it as missing, from what i can work out .26 never actually saved the serial info, and aslong as your pc didnt lock up in the erase process your ok, but if you had to reboot your pc then you lost your serial and its gone forever.
|
AfterDawn Addict
|
28. January 2009 @ 14:59 |
Link to this message
|
|
Yep, it seems possible that while .26 did read the info, some of it may have gotten lost in translation, so to speak.
I think we need some clear input the the Jungle team.
Also, does this mean that those who did it in DOS with the old version of dvdkey32 (same version as what was in JF.26) may have also lost that info?
This message has been edited since posting. Last time this message was edited on 28. January 2009 @ 15:03
|
|
drybrdl
Junior Member
|
28. January 2009 @ 15:13 |
Link to this message
|
Originally posted by Donaldo:
yes mine looks nearly identical lots of FF's...
BTW on the target drive serial tab... you can see where it is copying the first bit from the source, the D608CG..... but where is it getting the rest of the data that follows those characters?? is it randomly generating it or is it the same for everyone ??
using the ix15-liteon.bin as the target my data following the D608.... string is::
8G31075017E414XXA0..S4P881400000114443
after i did that i exited JF and loaded the files again and it generated the exact same string of characters so it must not be completely random
i think It gets the rest of the serial from the Target (hacked) fw if theres anything missing it just doesnt change it on the target
|
|
Donaldo
Senior Member
|
28. January 2009 @ 15:31 |
Link to this message
|
Originally posted by bhetrick:
Also, does this mean that those who did it in DOS with the old version of dvdkey32 (same version as what was in JF.26) may have also lost that info?
yes that is how mine was dumped... using DVDkey32 even before JF was released... i was running a spoofed samsung using that information...
then when JF .26 was released with the iXtreme 1.5 i flashed my liteon with that information.... so there is no hope of recovery...
|
|
Donaldo
Senior Member
|
28. January 2009 @ 15:34 |
Link to this message
|
Originally posted by drybrdl:
i think It gets the rest of the serial from the Target (hacked) fw if theres anything missing it just doesnt change it on the target
well if that's the case... that everyone who was missing this data is now sharing one "default" serial ...
my god microsoft must be partying with champagne and caviar right now ... if they can release a quick security patch which can read the serial # ... could see 1,000,000 xbox's banned overnight .... well maybe not that many =) but ya get my point
|
AfterDawn Addict
2 product reviews
|
28. January 2009 @ 15:55 |
Link to this message
|
Originally posted by Donaldo:
Originally posted by drybrdl:
i think It gets the rest of the serial from the Target (hacked) fw if theres anything missing it just doesnt change it on the target
well if that's the case... that everyone who was missing this data is now sharing one "default" serial ...
my god microsoft must be partying with champagne and caviar right now ... if they can release a quick security patch which can read the serial # ... could see 1,000,000 xbox's banned overnight .... well maybe not that many =) but ya get my point
I don't think that is the case. My dump from .26 has a lot of FF's in it but it doesn't EXACTLY match the dump from bhetrick .26 dump with a lot of FF's.
|
|
Donaldo
Senior Member
|
28. January 2009 @ 16:52 |
Link to this message
|
Originally posted by leerage:
I don't think that is the case. My dump from .26 has a lot of FF's in it but it doesn't EXACTLY match the dump from bhetrick .26 dump with a lot of FF's.
what i'm talking about is the data that it fills in for those FF's ... not the data that is actually there in the source.
load your dump in the source and load ix15-liteon.bin as the target... now in the TARGET drive serial tab if your data matches mine we're screwed... i seriously hope it doesn't....
|
AfterDawn Addict
2 product reviews
|
28. January 2009 @ 17:46 |
Link to this message
|
Originally posted by Donaldo:
Originally posted by leerage:
I don't think that is the case. My dump from .26 has a lot of FF's in it but it doesn't EXACTLY match the dump from bhetrick .26 dump with a lot of FF's.
what i'm talking about is the data that it fills in for those FF's ... not the data that is actually there in the source.
load your dump in the source and load ix15-liteon.bin as the target... now in the TARGET drive serial tab if your data matches mine we're screwed... i seriously hope it doesn't....
No, mine doesn't. Anybody else want to post serial data so we can compare?
Here is mine:
0000: 44 36 30 38 43 47 38 34 - 32 38 30 38 30 30 57 4E D608CG84280800WN
0010: 30 20 20 20 FF FF FF FF - 38 4A 30 38 30 38 39 32 0 ....8J080892
0020: 31 37 47 32 31 34 58 58 - 41 30 FF FF 53 34 50 38 17G214XXA0..S4P8
0030: 41 31 35 30 30 30 30 30 - 31 33 38 38 31 32 00 00 A1500000138812..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
|
|
drybrdl
Junior Member
|
28. January 2009 @ 18:53 |
Link to this message
|
|
Which lite-on tutorial did u all follow?
|
AfterDawn Addict
2 product reviews
|
28. January 2009 @ 18:58 |
Link to this message
|
Here is serial info from somebody else...
0000: 44 36 30 38 43 47 38 32 - 32 39 31 32 30 34 30 4A D608CG822912040J
0010: 31 20 20 20 FF FF FF FF - 38 45 31 39 30 32 30 38 1 ....8E190208
0020: 31 37 30 36 31 34 58 58 - 41 30 FF FF 53 34 50 38 170614XXA0..S4P8
0030: 35 32 35 30 30 30 30 30 - 30 30 36 31 31 32 00 00 52500000006112..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
I'd say they aren't the same so we should be ok in that aspect. But the problem im afraid I am going to run into is that the dump i did, is missing the majority of that info and giving a lot of FF's. I hope this doesnt cause a problem with xbl.... :(
|
|
drybrdl
Junior Member
|
28. January 2009 @ 19:19 |
Link to this message
|
|
dont worry guys, we can use al those FF FF`s later when we get banned from xbl. uck uck uck uck!
Which tut did u all use??
|
AfterDawn Addict
2 product reviews
|
28. January 2009 @ 19:48 |
Link to this message
|
Originally posted by drybrdl:
dont worry guys, we can use al those FF FF`s later when we get banned from xbl. uck uck uck uck!
Which tut did u all use??
It was a mix and match from a couple of tuts but mainly the xecuter one for me.
|
|
drybrdl
Junior Member
|
28. January 2009 @ 19:55 |
Link to this message
|
|
the xecuter tut is wrong, at step 5 you are suppose to click the open dummy as source button and it creates the dummy file for u,
|
|
Donaldo
Senior Member
|
29. January 2009 @ 04:02 |
Link to this message
|
Originally posted by leerage:
I'd say they aren't the same so we should be ok in that aspect. But the problem im afraid I am going to run into is that the dump i did, is missing the majority of that info and giving a lot of FF's. I hope this doesnt cause a problem with xbl.... :(
yes i feel a lot better after reading your results... the fact that the data isn't identical is reassuring ...
as far as XBL goes... the admin guy from JF said it could lead to easier detection... i have no reason not to believe him... but at the same time there is absolutely nothing i can do about it at this point...
its just regretable that we didn't know this sooner... there's no way i would have flashed my liteon knowing that drive-specific unique information was being lost ...
|
|
Advertisement
|
|
|
AfterDawn Addict
2 product reviews
|
29. January 2009 @ 17:53 |
Link to this message
|
Originally posted by Donaldo:
Originally posted by leerage:
I'd say they aren't the same so we should be ok in that aspect. But the problem im afraid I am going to run into is that the dump i did, is missing the majority of that info and giving a lot of FF's. I hope this doesnt cause a problem with xbl.... :(
yes i feel a lot better after reading your results... the fact that the data isn't identical is reassuring ...
as far as XBL goes... the admin guy from JF said it could lead to easier detection... i have no reason not to believe him... but at the same time there is absolutely nothing i can do about it at this point...
its just regretable that we didn't know this sooner... there's no way i would have flashed my liteon knowing that drive-specific unique information was being lost ...
Agreed, I guess we will have to sit and wait. By the way, where is the Jungle Flasher IRC, I know where the #fw is but would like to contribute to that IRC also.
|
