-
JungleFlasher v0.1.86 (267)Posted by XanTium | August 5 19:03 EST | News Category: Xbox360 |
| |
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.91 -Lite-on Slim 0272, 0225, 0225u, 0401 -Lite-on Phat 02510C -Benq 04421C -Hitachi 78/79 * Bug fix for non USB MTK routines: Read, Write, Phatkey etc.... * Support for Sputnik/Russian MXIC unlock methods.
Official Site: http://www.jungleflasher.net Download: here
|
-
Thanks Team Jungle!
-
Can I flash a slim with via?
-
Deleted
This post has been edited by Grifter357: Aug 6 2011, 03:44 AM
-
QUOTE(pigbait @ Aug 5 2011, 08:40 PM)

Can I flash a slim with via?
Were you able to flash via VIA before using (184) or below? than yes
Actually as far as I know, VIA has always'd work with some tweaking and driver fixing and such.
-
Great work fellas keep up the great work.
-
Yay!
Thanx again Oggy! Really appreciate it mate!
Making our lives easier as always :-)
Brgds/Dan
-
I can tell with the dedication of the new firmware that the team wishes the method wasn't so, BUT kamikaze is working now with 1.86. Just intro'd and let the spi .... on my 0225 and after a 10 minutes with dremel, opened right up.
How the hell do you lock the thing back though? I've written the 1.91 to it, don't I have to lock it with sw? I still can't get it to go 72 with my via6421 so I can't use the unlockspi just as before. How do I lock the drive over usb now? Wanna try out my lighter..
Why don't I have an SPi button on jf? mine is just blank under write?
This post has been edited by ProphetOfPain: Aug 6 2011, 07:39 AM
-
seems to me that the SPI button is blacked out aswell
- i flashed a bunch of liteons and samsunsg with the new firmware no problem there no slims yet so cant say about the SPI
-
QUOTE(danthaman673 @ Aug 6 2011, 06:23 AM)

Yay!
Thanx again Oggy! Really appreciate it mate!
Making our lives easier as always :-)
Brgds/Dan
I do NOT write, nor even test JungleFlasher[/b]
-
flash to newest lt 1.91 on phat liteon drive need for speed an black ops does not read says unreadable disk
-
QUOTE(OggyUK @ Aug 6 2011, 10:16 AM)

I do NOT write, nor even test JungleFlasher[/b]
but but danthaman673 is a "scener" and knows everything thats going on behind closed doors!
/sarcasm
-
-
Does this support Geremia unlock or not?
The nfo in the officialt JF download doesnt mention JF.
(same as OP)
QUOTE
JungleFlasher 0.1.86(267)
========================================
Support for LT Plus 1.91
-Lite-on Slim 0272, 0225, 0225u, 0401
-Lite-on Phat 02510C
-Benq 04421C
-Hitachi 78/79
Bug fix for non USB MTK routines: Read, Write, Phatkey etc....
Support for Sputnik/Russian MXIC unlock methods.
Yet the one edited by someone else says different.
QUOTE
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.91
-Lite-on Slim 0272, 0225, 0225u, 0401
-Lite-on Phat 02510C
-Benq 04421C
-Hitachi 78/79
* Bug fixes for non USB MTK routines: Read, Write, Phatkey etc....
* Support for Sputnik MXIC & Windbond Unlock methods.
Source:- http://www.team-xecu...amp;postcount=1
Havent read the new userguide, been playing the 360.
-
QUOTE(skater411 @ Aug 6 2011, 10:29 AM)

flash to newest lt 1.91 on phat liteon drive need for speed an black ops does not read says unreadable disk
Sounds like you havent got the latest patched versions of the game , old ap25 patch as thats what happens if you put them in , unknown content error, flagged.
-
QUOTE(OggyUK @ Aug 6 2011, 11:56 AM)

Does this support Geremia unlock or not?
The nfo in the officialt JF download doesnt mention JF.
(same as OP)
Yet the one edited by someone else says different.
Source:-
http://www.team-xecuter.com/forums/showpos...amp;postcount=1Havent read the new userguide, been playing the 360.
JF seems to sit waiting for the flash status to change (be that MX/resistor or Winbond/drilling), also seen reports of people saying they have unlocked Winbonds with it.
-
Geez, I posted last night shortly after it came out that it works on winbonds. If you look in the Gecko thread people acting like i'm crazy because I was trying everything to get the stupid thing to unlock but I have a ck3 and x360usb.
UNLOCKED WINBOND with latest Jungleflasher no problem.
What i'm trying to do is lock it back? Maybe it will lock once back in the 360 is what I was thinking, but am unsure and well, im left hanging again (IMG:style_emoticons/default/smile.gif) will be soldering the board back in and testing it shortly.
This post has been edited by ProphetOfPain: Aug 6 2011, 02:26 PM
-
You mean you posted in the lizard OS for a standalone hardware flasher thread about a PC based utility and are now shocked that I asked in a JungleFlasher topic?
Sorry, I didn't think to look in that thread for the answer.
Anyway, seems it does work.
-
QUOTE(OggyUK @ Aug 6 2011, 04:00 PM)

You mean you posted in the lizard OS for a standalone hardware flasher thread about a PC based utility and are now shocked that I asked in a JungleFlasher topic?
Sorry, I didn't think to look in that thread for the answer.
Anyway, seems it does work.
Wow.... I posted in THIS THREAD.
Had been posting in the other just trying to get my drive into 72 so I could use unlockspi with my via card.
-
I expected some other bugfix notes, maybe you forgot?
Let me help you
- fixed the inquiry serial latest 3bytes bug, in reflashed drives it's 000000 but fw reports them as 202020 in inquiry command reply. Thanks unknown for the hint, whithout it we would have to tell people it was simply a bad dvdkey problem till jf 2.xx
- fixed the 1FF80 data, we don't know what's that but kids like to call it calibration data. We are very busy to drill mtk chips, so sorry if the complete 1FF80 area will be dumped somewhere near jf 2.xx release.
- fixed 3F000 for 0225u, without a method to unlock any locked spi we probably would have fixed that in near 2.xx release.
- still some other bug to spot out, but hey, a play dvd error here and there is acceptable, right? Just repower the console and the sporadic problem goes out.
-
I have a 0401 WB drive. Managed to unlock it.
When I try to read the firmware (original) with the new JF I get the following:
Can't open file
D:\JF\firmware\LTPlus-0272-v1.9.bin
Any idea why it would need the bin file??
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Drive Key.
............
Authorised !
Confirming sector 0x3E000.
................
-
QUOTE(Ferid @ Aug 6 2011, 04:24 PM)

I have a 0401 WB drive. Managed to unlock it.
When I try to read the firmware (original) with the new JF I get the following:
Can't open file
D:\JF\firmware\LTPlus-0272-v1.9.bin
Any idea why it would need the bin file??
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Drive Key.
............
Authorised !
Confirming sector 0x3E000.
................
Well, same here so I just put the firmware in it's folder. Now, I get fussed at when I ask for help, I don't know everything, but I'm thinking it needed the firmware loaded in so it can "CONFIRM" sector 0x3E0000. Perhaps it can't confirm it without double checking against the bin? Regardless, it did dump the OFW.
-
QUOTE(ProphetOfPain @ Aug 6 2011, 04:38 PM)

Well, same here so I just put the firmware in it's folder. Now, I get fussed at when I ask for help, I don't know everything, but I'm thinking it needed the firmware loaded in so it can "CONFIRM" sector 0x3E0000. Perhaps it can't confirm it without double checking against the bin? Regardless, it did dump the OFW.
correct
QUOTE(ProphetOfPain @ Aug 6 2011, 02:24 PM)

Geez, I posted last night shortly after it came out that it works on winbonds. If you look in the Gecko thread people acting like i'm crazy because I was trying everything to get the stupid thing to unlock but I have a ck3 and x360usb.
UNLOCKED WINBOND with latest Jungleflasher no problem.
What i'm trying to do is lock it back? Maybe it will lock once back in the 360 is what I was thinking, but am unsure and well, im left hanging again

will be soldering the board back in and testing it shortly.
in case you havent read the tutorial
after write, place in vendor mode again! then CTRL + SHIFT + F11 sends lock command
-
QUOTE(LittleBH @ Aug 6 2011, 05:03 PM)

correct
in case you havent read the tutorial
after write, place in vendor mode again! then CTRL + SHIFT + F11 sends lock command
Where do I send your christmas gift this year? ALL the drama, CRTL+SHIFT+F11. It sent the request, it didn't confirm that it was locked but I waited a few and then when I did an intro it indeed came up SW Locked! Thank you thank you thank you. And no, I didn't read the LATEST tutorial I guess with all the drama i was having, but why in the world would the SPI button be blanked and have to press key combo? Yea, I ASSUMED I could just click to lock
-
QUOTE(Ferid @ Aug 6 2011, 05:24 PM)

I have a 0401 WB drive. Managed to unlock it.
When I try to read the firmware (original) with the new JF I get the following:
Can't open file
D:\JF\firmware\LTPlus-0272-v1.9.bin
Any idea why it would need the bin file??
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0x0000
Serial flash found with Status 0x72
Reading Drive Key.
............
Authorised !
Confirming sector 0x3E000.
................
The strange thing is I have a 0401 drive and it's trying to load a 0272 firmware
-
i managed to flash my 0272 (original 9504) with 1.91 using kamikaze-method.
but i didnt do a slimkey on the original firmware, is this important?
i flashed it using the full dump (lite-ofw.bin) as the original firmware.
also, what is this mysterious sector 0x3e0000?
here my story:
1) i flashed the 9504 with LT+ 1.0
2) flashed back to original, but not using full dump or dummy.bin because i couldnt find my original dump any more.
3) thus i dumped the LT+ 1.0 so i have my key and restored the OFW using the CFW.
4) flashed OFW
5) upgraded to newest dash.
6) ms flashed my device with 0272.
questions:
1then i just dumped the original 0272 using full dump ("read") and flashed cfw.
when i was asked for the 0x3e000 ("it may be blank"), i chose _no_ because my device had 0272 on it, was that correct?
2) to be on the safe side i flashed the OFW i just dumped and used the slimkey method to get the dummy.bin, serial.bin, inquire.bin, etc.
was that useful or useless?
somebody tell me if what i did was correct, and what sector 0x3e0000 is good for please. 
i want to know if what i did is correct before i assemble my xbox.
thanks in advance,
p1lot
-
works for winbond unlock however prefer geremias tool as it has the sound when it unlocks to prevent you drilling too far, hard to keep an eye on the IC and the screen at the same time.
-
QUOTE(xboxer360 @ Aug 7 2011, 03:12 AM)

works for winbond unlock however prefer geremias tool as it has the sound when it unlocks to prevent you drilling too far, hard to keep an eye on the IC and the screen at the same time.
You can't have tried JF on a winbond, or read the guide
-
i have a slim with a 9504 drive and second latest dash. if i want to flash to 1.91 is it good to update to latest dash and the flash LT+ or updating the dash will lock the drive?
-
QUOTE(xboxer360 @ Aug 7 2011, 04:12 AM)

works for winbond unlock however prefer geremias tool as it has the sound when it unlocks to prevent you drilling too far, hard to keep an eye on the IC and the screen at the same time.
maybe jungleflasher makes a sound also, just a wild stab in the dark.
This post has been edited by boneym: Aug 7 2011, 12:14 PM
-
QUOTE(boneym @ Aug 7 2011, 12:13 PM)

maybe jungleflasher makes a sound also, just a wild stab in the dark.
It does.
-
That was his point.
-
did my phat liteon, worked great, rechecked my codbo with abgx for new ap25 fix since 13141 , reburned and works fine.
slim liteon 9504 with mx spi waiting on sputnik board before i try the update to 13599, got the full dump of the ofw just in case before update. stay tuned.
thanks c4e and everyone involved for your hard hard work.
This post has been edited by chris67rs: Aug 8 2011, 02:56 PM
-
thanks for the hint about the CTRL + SHIFT + F11 sends lock command
i was like why is the SPI button blanked out
now i see
-
So the CTRL + SHIFT + F11 do a Sofware Lock.
Maximus lizard has the feature of a software Lock or a Hardware Lock,
Hardware is recommended for XBL...
-
hi guys,
i have a slim here on dash 13146 with a liteon 9504 drive.i extracted the firmware from the slim (0272)and made a dummy bin.what i would like to know is this all i need to flash a new tx pcb replacement board,and would i be best to upgrade to dash 13599 with my original pcb board and swap with tx one after update?going to update with lt.1.9 as will only be using original ap2.5 games on xbl.
-
QUOTE(steplay29 @ Aug 10 2011, 07:59 PM)

hi guys,
i have a slim here on dash 13146 with a liteon 9504 drive.i extracted the firmware from the slim (0272)and made a dummy bin.what i would like to know is this all i need to flash a new tx pcb replacement board,and would i be best to upgrade to dash 13599 with my original pcb board and swap with tx one after update?going to update with lt.1.9 as will only be using original ap2.5 games on xbl.
Apply 13599 update with original PCB, then swap it with xecuter one
The xecuter pcb locks different then the original, so updating with the xecuter one will fail the update
-
hello
in this new JF i cant verify fat Liteon key. It keep saying key is not found.
but key is verified in JF 1.84.
use this new JF to flash despite key is unverifyed, its still success and can play games.
a bug?