Post by: Xbox-Scene on July 19, 2011, 07:45:00 PM
| As always with a new C4E iXtreme release, Team Jungle also comes with a new version of JungleFlasher to add full support for the new firmwares. What's new/fixed: * Support for LT Plus 1.9 Liteon(slim): -0272 -0225 -0225u (factory updated 9504 to 0225) -0401 * Support for set Spi Lock status register on: - XECUTER DG-16D4S UNLOCKED PCB - XECUTER DG-16D4S PRO INSTALL KIT * Support to extract and patch calibration data at 0x1FF80. * In some cases 0225 may give "Play DVD" error randomly, without this data. Official Site: http://www.jungleflasher.net Download: here |
Post by: deilzfcjk on July 19, 2011, 09:11:00 PM
Howcome is only available for Team X Dg-164s unlockd pcb?
Is jungle flasher just Xoring until the bit pattern matches the vendor specific control code from factory.
So is there a XOR to get the individual bits to identify as 0x72?
Post by: Zoneout on July 19, 2011, 09:57:00 PM
Post by: klbarnes1 on July 19, 2011, 10:20:00 PM
Post by: VivaLaMikey on July 20, 2011, 01:50:00 AM
I really appreciate the work these guys do and i thank them all for it, BUT hopefully someone important reads this and it can be rectified.
Reason i say that is i just tried to flash my BENQ 04421C back to stock so i can do the recent update to 13599 but on erase it hangs so i hit erase to do it manually but all i get is a "Blank Test Failed" message.
Messed round for nearly an hour then thought id try JF 184 (250) and it worked straight away without a hitch.
So yea just for the sake of information gathering and bug reporting thought id share my knowledge in case anyone else has this error.
EDIT: Right so i just tried flashing my Lite-On to stock on my other console as well so i can update and that did the same thing hung on the write blah blah blah
so i went back to JF 184 (250) once again and it worked.
Is it just me that has the retarded version or is anyone else having this same problem?
This post has been edited by VivaLaMikey: Jul 20 2011, 09:05 AM
Post by: dbdsneaky on July 20, 2011, 03:31:00 AM
This post has been edited by dbdsneaky: Jul 20 2011, 10:32 AM
Post by: modguru.gr on July 20, 2011, 05:58:00 AM
(IMG:http://i53.tinypic.com/15xsvx2.jpg)
i am try to download the pdf from the new jungleflasher but i am taking error in the download page
This post has been edited by modguru.gr: Jul 20 2011, 01:32 PM
Post by: Geremia on July 20, 2011, 08:49:00 AM
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.
Post by: Taher on July 20, 2011, 09:58:00 AM
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 ?!
Post by: NoodlyAppendage on July 20, 2011, 11:22:00 AM
QUOTE(Geremia @ Jul 20 2011, 04: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.
0225u JF definitely _still_ has bug. Oggy, did you not read my 2nd PM?
Post by: OggyUK on July 20, 2011, 11:27:00 AM
I don't work with "the team" any more.
I just relayed messages on behalf of you as they seemed of great importance.
I was told it was 'in hand'so left it at that.
Post by: VivaLaMikey on July 20, 2011, 01:11:00 PM
Post by: Twis7eD on July 20, 2011, 02:27:00 PM
Post by: MVPd on July 20, 2011, 02:51:00 PM
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.
This post has been edited by MVPd: Jul 20 2011, 09:55 PM
Post by: gimpchop on July 21, 2011, 06:16:00 AM
Post by: Warpilein on July 21, 2011, 06:16:00 AM
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
Post by: CelerionQ on July 21, 2011, 07:58:00 AM
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
Post by: GHR on July 21, 2011, 10:32:00 AM
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...
Post by: LkBurn on July 21, 2011, 12:24:00 PM
Post by: VivaLaMikey on July 21, 2011, 01:16:00 PM
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.
Post by: an01523 on July 21, 2011, 01:56:00 PM
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)
Post by: Geremia on July 21, 2011, 02:35:00 PM
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
Post by: NoodlyAppendage on July 21, 2011, 02:40:00 PM
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 GeremiaPost by: an01523 on July 21, 2011, 02:43:00 PM
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 Geremiasounds good - i have many HEX editors here on my desktop.
Post by: Geremia on July 21, 2011, 05:50:00 PM
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
Post by: VivaLaMikey on July 22, 2011, 12:51:00 AM
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.
Post by: cypher21 on July 22, 2011, 04:12:00 AM
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
Post by: an01523 on July 22, 2011, 05:18:00 AM
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 GeremiaThanks for your help! Works good now with LT0225u.
Post by: CelerionQ on July 22, 2011, 06:44:00 AM
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"...
Post by: Geremia on July 22, 2011, 07:05:00 AM
Post by: an01523 on July 22, 2011, 08:36:00 AM
both 0225 (labeled as 0225) and 0225 (labeled as 9504) have sometimes "play dvd" problem.
After flash it works first time, after some power on/off the xbox -> "play dvd"
Another power on/off few times and it works again.
Something is fault here!
Post by: NoodlyAppendage on July 22, 2011, 09:04:00 AM
QUOTE(an01523 @ Jul 22 2011, 04:36 PM)
Next problems:
both 0225 (labeled as 0225) and 0225 (labeled as 9504) have sometimes "play dvd" problem.
After flash it works first time, after some power on/off the xbox -> "play dvd"
Another power on/off few times and it works again.
Something is fault here!
Sounds like there is still some incorrect data in the dummy.bin. That would suck because you have overwritten the flash with junk from JF
Post by: Geremia on July 22, 2011, 10:06:00 AM
PM sent
Post by: an01523 on July 22, 2011, 11:43:00 AM
It seems my 0225 (Label 9504) is not a 0225u? If i flash LT0225u.bin (sent me in PM, and also the original one), then no booting at all. If i flash LT0225.bin (made with fixed DUMMY.bin), it boots sometimes and sometimes not.
Pady in gulli forum figured out, that you have to read after flash. This is very tricky, because you have to connect and disconnect resistor to read FW and then restore/erase/write sector 0xE3000 (automaticaly by JF after reading).
After read/dump the FW, sector E3000 is written again - and then no more "play DVD".
Post by: BxBrotha730 on July 22, 2011, 06:27:00 PM
i have a slim drive stock 0225 and i am using x360usb pro........i retrieved the key......but im tryng to flash drive.....it doesnt auto load for some odd reason, so i go and manually had the firmware for 0225 and click spoof. when i click write it immediately hands where it says "sending chip erase"..happens on both my desktop and laptop..can someone help n provide valid info on what i need to do?
Post by: LittleBH on July 22, 2011, 07:19:00 PM
QUOTE(Geremia @ Jul 20 2011, 03:49 PM)
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.
Tested this one myself - Geremia, you have more technical know how than me - however - you are wrong on this one!
Post by: OggyUK on July 23, 2011, 12:59:00 AM
Post by: an01523 on July 23, 2011, 05:31:00 AM
Post by: VivaLaMikey on July 23, 2011, 06:43:00 PM
QUOTE(OggyUK @ Jul 23 2011, 06:59 PM)
Did anyone actually test v0185 (257) on non USB?
I dont use the usb and it still bugging out for me, im still using sata + maximus 360 xtractor
Post by: 0x13h on July 23, 2011, 08:27:00 PM
Im trying to flash my drive with last c3v4 release and JF 1.85 (257)
Y retrieve a error: Slim-Un-Lock command returned a error.... Unlock Failed
What is that?... how to solve?
thanks!
Post by: OggyUK on July 24, 2011, 04:48:00 AM
QUOTE(VivaLaMikey @ Jul 24 2011, 01:43 AM)
I dont use the usb and it still bugging out for me, im still using sata + maximus 360 xtractor
I meant efore it was released, everyone has a USB, sems they all only tested it on USB only.
Last JF I used (and still do) Is 1.85 build 252 - I only use a laptop now so USB only for me.
QUOTE(0x13h @ Jul 24 2011, 03:27 AM)
i've LiteOn 16D4S 0225
Im trying to flash my drive with last c3v4 release and JF 1.85 (257)
Y retrieve a error: Slim-Un-Lock command returned a error.... Unlock Failed
What is that?... how to solve?
thanks!
Read the guide, maybe?
You slimkey an 0225, not unlock.
Post by: VieS on July 28, 2011, 01:09:00 AM
Will my DG-16D4S 9504 be locked, if i flash it with 0225 orig, and update dashboard to new version?
This post has been edited by VieS: Jul 28 2011, 08:09 AM
Post by: skater411 on July 29, 2011, 10:28:00 PM
This post has been edited by skater411: Jul 30 2011, 06:08 AM
Post by: skater411 on July 29, 2011, 11:07:00 PM
This post has been edited by skater411: Jul 30 2011, 06:19 AM
Post by: gsm88 on August 02, 2011, 03:48:00 PM
I have a 0225 drive (labeled as 9504), I flashed LT+1.9 0225 and 0225u with x360 usbpro, and I get everytime "Play DVD". I use TX unlocked pcb and I have original pcb with original firmware.
Please help me, how to fix it this problem?
Thanks!
Post by: LyNDe666 on August 24, 2011, 06:09:00 PM
How it's possible that the pagecode 23 doesnt affect the check process ?? what the pagecode returns so it's not important for the boot process?
Thanks!
Post by: an01523 on September 20, 2011, 09:33:00 AM
Dummy is from Liteon FW 0225, labeled as 0401.
I tried allredy ixtreme LT+ 1.91, 1.91u, 1.92, 1.92u - no one work - allways "play dvd" error.
Here is this dummy.bin:
http://www.megaupload.com/?d=A49ES4GI
I do not have the orig.bin, only the dummy.bin.