Print

[Warpilein]

QUOTE(Taher @ Jul 20 2011, 05:58 PM)

I have a weird problem with this new version of JF.
I tried to flash a PHAT Lite-On with LT+ 1.9 on this new version of JF, when I erased the firmware using Lite-On Erase button, and then hit Write button, it stopped right there! it did nothing more and just stopped!
I went back to ver 1.84(250) of JF and wrote the firmware using that version.
What's wrong with this new version of JF ?!

The same thing here

[CelerionQ]

QUOTE(Geremia @ Jul 20 2011, 04:49 PM)

just a quick look:

0272 buggy fw? all realtime checks fails?!!!? seems too much strange, maybe i did something wrong, but sincerely who cares, even if you fix the realtime overall fails, you'll still have a few % of fails cause of overall jf bug.

Hi Geremia

We have talked about this on #fw today. It ended up by c4e saying that if the real time checks where failing we couldn't even play backups, because the checks are performed online and offline. Are backups working on your 0272 at all?

If they don't work you must have done something wrong, because for most people the 0272 is performing well. And if they do work - how can the checks be failing (Unless the statement by c4e is wrong..)

Thanks
Celerion

[GHR]

QUOTE(Geremia @ Jul 20 2011, 03:49 PM)

Seems the bugs are less important then the release time?
just a quick look:

0272 buggy fw? all realtime checks fails?!!!? seems too much strange, maybe i did something wrong, but sincerely who cares, even if you fix the realtime overall fails, you'll still have a few % of fails cause of overall jf bug.

0225 works, good realtime check timings

0225u buggy jf

now some uberidiot will pop out telling that i must provide evidence, but i'm sure they already have the evidence, just the fix is missing.

calibration data? maybe you dind't understand again what's that data for.
Aside the fact that "calibration data" in fat liteons was just a "manufacturer test log", here the "manufacture test log" is at 3F000,  and what you see at 1FF80 is "manufacturing tests commands"
Do you think that only 0225 has this 1FF80 different? nope! these are manufacturing tests commands, not all drive have been tested against the same sequence of commands. Also 9504 had different 1FF80.

Man thank you so much for the heads up!! Really appreciated.. Now I guess I'd go with the x360key.
BTW, I knew that TX decleration of 'rootkit improved so the timings are accurate' was a bit bold, but the fail of those checks? I'd rather stick with delayed challenge responses.

QUOTE(MVPd @ Jul 20 2011, 09:51 PM)

Same on mine too, just tried to flash BENQ back to stock and it froze on write, can't get the drive to show up at all now, or eject even. Any hints on getting it working again?

EDIT: Got it to show up again, the drive seems blank, i've closed the tray, and opened jungleflasher again and just done intro/device id and did the power off power on again and its back in vendor mode. I guess we should stay away from this version of JF. Im flashing back to stock with the old version.

QUOTE(gimpchop @ Jul 21 2011, 01:16 PM)

same here my 0225 stops at bank 0 wont go any further. 1.84 flashies my 0225 unlocked pcb but it dont work play dvd prob. I then tryed to flash a old liteon and it sent erase code then wouldnt go it stat 0x72 so went to 1.84 and it showed as liteon so it dint even erase in 1.85 even though it said it had  1.84 flashed it perfect just wondeing if its worth installig xp and trying that any thoughts on that is it worth a try.

All of you that read this post:
STAY CLEAR FROM JF 1.85 (257) - I couldn't get it to write to any drive at all! Both slims and Phats...
JF 1.84 Does the trick for me ATM...

[LkBurn]

This version of JungleFlasher does the same thing, it freezes when I try to write to a drive. The only way I got it to write was take my X360Pro out of my car and install it into this computer, then try again. Then, it started working!

[VivaLaMikey]

QUOTE(gimpchop @ Jul 22 2011, 12:16 AM)

same here my 0225 stops at bank 0 wont go any further. 1.84 flashies my 0225 unlocked pcb but it dont work play dvd prob. I then tryed to flash a old liteon and it sent erase code then wouldnt go it stat 0x72 so went to 1.84 and it showed as liteon so it dint even erase in 1.85 even though it said it had  1.84 flashed it perfect just wondeing if its worth installig xp and trying that any thoughts on that is it worth a try.

I dont really see what xp will do its obviously an overlooked bug. Seems that a few of us are having problems but there are thousands out there who arent.
Makes me wonder if we have anything in common by getting this specific error.

[an01523]

XBOX 360 MFD 2011-03-15
FW 0225 (Label 9504, June 2010)

Xecutor 360 USB PRO
WinXP Pro
JF 1.85

Made dummy.bin with JF 1.85 -> auto load lt19-0225.bin -> flashed with russian method -> "DVD Play" error with originals and backups
tryed lt19-0225u.bin -> still DVD Play

Is there a chance to fix this, because i have only a dummy.bin from my drive but not the retail firmware?

(another Xbox360Slim: FW 0225 and label 0225, no problem, work fine with russian method to unlock and flash lt19-0225.bin)

[Geremia]

i've not played any games on my slim, i dont' care to see a game booting. I send my realtime check and i look at answeres, lt0225 matches 0225orig, lt0272 totally fails, lt0225u fails on some checks (not all) cause of a bug of jf.

So, why i notice the fails and not the console?

3 possibilities:

- i screwed in making the lt0272, but i did more time, starting from my fulldump, inserting the orig 0272 file renamed as they tells...
- console does not "play dvd error" for a fail of pagecode23 (0272 are only checked against pagecode23), while 0225u fails sometimes (cause of jf bug) with a "play dvd" cause of a pagecode24 fail. in few words, could be console does not boot if pagecode24 fails but let you boot (and maybe banflag) for a pagecode23 fail.
- my checking app uses an initial seed that the rootkit does not like

[NoodlyAppendage]

QUOTE(an01523 @ Jul 21 2011, 09:56 PM)

XBOX 360 MFD 2011-03-15
FW 0225 (Label 9504, June 2010)

Xecutor 360 USB PRO
WinXP Pro
JF 1.85

Made dummy.bin with JF 1.85 -> auto load lt19-0225.bin -> flashed with russian method -> "DVD Play" error with originals and backups
tryed lt19-0225u.bin -> still DVD Play

Is there a chance to fix this, because i have only a dummy.bin from my drive but not the retail firmware?

(another Xbox360Slim: FW 0225 and label 0225, no problem, work fine with russian method to unlock and flash lt19-0225.bin)

Sounds like the 0225u JF bug might have bitten you. Not a difficult fix if you have a HEX editor, maybe Oggy will swing by and tell you how I better give "the team" a chance to clone the new Lizard release but if you're still waiting on Monday PM me or Geremia

[an01523]

QUOTE(Geremia @ Jul 21 2011, 09:35 PM)

i've not played any games on my slim, i dont' care to see a game booting. I send my realtime check and i look at answeres, lt0225 matches 0225orig, lt0272 totally fails, lt0225u fails on some checks (not all) cause of a bug of jf.

So, why i notice the fails and not the console?

3 possibilities:

- i screwed in making the lt0272, but i did more time, starting from my fulldump, inserting the orig 0272 file renamed as they tells...
- console does not "play dvd error" for a fail of pagecode23 (0272 are only checked against pagecode23), while 0225u fails sometimes (cause of jf bug) with a "play dvd" cause of a pagecode24 fail. in few words, could be console does not boot if pagecode24 fails but let you boot (and maybe banflag) for a pagecode23 fail.
- my checking app uses an initial seed that the rootkit does not like

i am not a coder...
i only can say, that flashing a 0225 FW (labeled as 9504) with JF 1.85 will ending in not booting any game (original and backups).

QUOTE(NoodlyAppendage @ Jul 21 2011, 09:40 PM)

Sounds like the 0225u JF bug might have bitten you. Not a difficult fix if you have a HEX editor, maybe Oggy will swing by and tell you how I better give "the team" a chance to clone the new Lizard release but if you're still waiting on Monday PM me or Geremia

sounds good - i have many HEX editors here on my desktop.

[Geremia]

QUOTE(CelerionQ @ Jul 21 2011, 02:58 PM)

Hi Geremia

We have talked about this on #fw today. It ended up by c4e saying that if the real time checks where failing we couldn't even play backups, because the checks are performed online and offline. Are backups working on your 0272 at all?

I told you 3 possibilities, but now i decided to sacrifice my slim and give you only 1 possibility

i took my original 0272 fulldump, i changed 0x100 bytes at 3F100, checked with my app and now all realtime checks fails. put drive in console, insert an original game and guess what?

game boots

reasuming:

realtime checks are 2 different kind, pagecode 23 and pagecode 24
dashboard reflashed drives (actually only 0272)  looses the possibility to bein checked with pagecode24, so console can only send pagecode23.
0225 and 0401 and...are checked with pagecode24.

- a pagecode24 fail results in "play dvd"
- a pagecode23 fail result in nothing visible, game just boot, don't know if you get flagged or not, i don't care

- all LT0272 fails on all the pagecode23 checks
- all the LT0225u fails in quite half the checks


just wondering what a betatester is there for, and what have been sent them to test  

[VivaLaMikey]

The way i see it, its got nothing to do with checks failing or response times its fully down to just a shit version of JF among the other problems i have encountered im even having trouble getting my benq to become visible on JF then its a whole other ball game trying to get it to vendor mode.

With build 184 i can hook my benq up flash it and have it back in my 360 running in around 5-7 minutes.

And dont even get me started on what i had to go through to vendor mode my 025.

I think for the time being im gonna stick with 184 until they release a nw update i dont have any drives i need 185 for anyway plus im booting games just fine.

So everyone just be aware only use 185 if you absolutely HAVE TO.

[cypher21]

QUOTE(VivaLaMikey @ Jul 22 2011, 06:51 AM)

The way i see it, its got nothing to do with checks failing or response times its fully down to just a shit version of JF among the other problems i have encountered im even having trouble getting my benq to become visible on JF then its a whole other ball game trying to get it to vendor mode.

With build 184 i can hook my benq up flash it and have it back in my 360 running in around 5-7 minutes.

And dont even get me started on what i had to go through to vendor mode my 025.

I think for the time being im gonna stick with 184 until they release a nw update i dont have any drives i need 185 for anyway plus im booting games just fine.

So everyone just be aware only use 185 if you absolutely HAVE TO.

there's a bug in 1.85 which causes write failures on onboard or via sata chipset.
X360usb works fine on all drives.

If you flash a non slim drive, just use 1.84
If you flash a slim drive, flash it with 1.84 and then lock it with 1.85

Fix is in the works and being thoroughly tested a.t.m.

This post has been edited by cypher21: Jul 22 2011, 11:13 AM

[an01523]

QUOTE(NoodlyAppendage @ Jul 21 2011, 10:40 PM)

Sounds like the 0225u JF bug might have bitten you. Not a difficult fix if you have a HEX editor, maybe Oggy will swing by and tell you how I better give "the team" a chance to clone the new Lizard release but if you're still waiting on Monday PM me or Geremia

Thanks for your help! Works good now with LT0225u.

[CelerionQ]

QUOTE(Geremia @ Jul 22 2011, 01:50 AM)

- a pagecode24 fail results in "play dvd"
- a pagecode23 fail result in nothing visible, game just boot, don't know if you get flagged or not, i don't care

- all LT0272 fails on all the pagecode23 checks
- all the LT0225u fails in quite half the checks
just wondering what a betatester is there for, and what have been sent them to test  

Thanks for all your work. Looks like a new LT+ 1.9 is needed. I will stay away from 9504 and 0225u LT+, and I guess everyone that cares about XBL should do so as well until there is a fixed version released. "The Team" and C4E will probably be denying or dodging questions related to this until c4 releases a new CFW with some "adjustments"...

[Geremia]

They call bugfixes "improvements"