Topic: C4Eva iXtreme LT v1.9 for Samsung and LT+ v1.9 for Benq and phat Lite- (Read 1004 times)

.:Dino:. · « **Reply #75 on:** June 16, 2011, 02:10:00 AM »

As far as i know, the issue was not so much legal as it is suitable. Firmware flashing involves an element of risk, and it was considered that ms flashing drive firmware would be considered a risky one for those without modded consoles. A corrupt firmware write means a lot of money for ms with repairs and people sending their consoles in due to issues with the update.

EpsilonMirror · « **Reply #76 on:** June 16, 2011, 02:15:00 AM »

QUOTE(.:Dino:. @ Jun 16 2011, 09:10 AM)

As far as i know, the issue was not so much legal as it is suitable. Firmware flashing involves an element of risk, and it was considered that ms flashing drive firmware would be considered a risky one for those without modded consoles. A corrupt firmware write means a lot of money for ms with repairs and people sending their consoles in due to issues with the update.

I can understand that about flashing, but I was mainly referring to dumping the firmwares, that specifically is what I remember being a legal problem(again I could be completely wrong about that). The thought came up because so many people seem to be worrying about the 360 sending back a dump of their pre-update firmwares and suggesting flashing back to stock before updating.

pt6 · « **Reply #77 on:** June 16, 2011, 02:33:00 AM »

hey,

I successfully flashed LT 1.9 on my phat LiteOn, but I wanted to report somethings strange i encountered...

I was on LT Plus and wanted to flash back to stock firmware before updating the dash and then flashing to LT Plus 1.9...

So I tried to flash my orig fw dump... the flash went through and appeared to be successful but I could not eject the dvd tray anymore...

so I flashed the fw in the OW folder in LiteOn_Post_13141... I know it's the wrong fw since i was pre dash update...

the flash went through successfully (was able to eject tray)...

I then updated the dash successfully, and here's the strange thing:

I inserted my original Halo Reach and the dvd drive did not recognize it and displayed PLAY DVD. I tried my original Halo ODST, same thing... I tried a backup, same thing...

very strange to me since the dash update flashed a stock fw onto the drive and originals should work... no idea what happened here...

I then flashed LT Plus 1.9 successfully and now originals and backups work...

anyways, thanx C4Eva - great work !

kuiponok · « **Reply #78 on:** June 16, 2011, 03:07:00 AM »

QUOTE(death69inc @ Jun 16 2011, 07:05 AM)

because i dl from there didnt know the gui was still stating 1.0.2
and i was in middle of a convo so i asked

Download this: http://www.megaupload.com/?d=CP36Q2GG

Extract en replace (make backup first!) the abgx360gui.exe with the one you downloaded, and then de GUI shows up as v.1.0.5 also.

Doesn't change anything else, but it looks nicer

I didn't made this myself, but downloaded it a while ago...

driftfox · « **Reply #79 on:** June 16, 2011, 03:08:00 AM »

QUOTE(Yafeu @ Jun 15 2011, 04:54 AM)

If you have your drive key, load your drive's version of LT 1.9 (Post 13141 Folder) into the target FW and paste in your drive key, then flash..

QUOTE(Ryououki @ Jun 15 2011, 06:35 AM)

Is this safe since it doesn't copy any of the other data? Or is the other data not needed any longer?

QUOTE(.:Dino:. @ Jun 15 2011, 01:57 PM)

From what i understand, the serial/barcode data is no longer present in the firmware the update writes, and so is no longer needed in the new firmware series. It was previously considered to be information left on from manufacturer, and true to this it seems it is not needed.

All you need then is the drive key, as 1.9 does not use calibration data, same as with the new ofw.
Hope that helps

I was wondering the very same thing and wanted to do some tests to see if I could find out just how true this was, so I created several custom firmwares (Phat Liteon LT+ 1.9) using different methods and compared the output files (both CRC and with HxD). This is what I found out:

MY SETUP:
Liteon 83850c V2
JungleFlasher 0.1.84 Beta

CUSTOM FIRMWARES:
Source 1: File dumped from OFW pre-13146 using MRA
Output file CRC: 88359E84

Source 2: File dumped from OFW post-13146 using MRA
Output file CRC: 88359E84

Source 3: Dummy file dumped from OFW post-13146 using PMT
Output file CRC: 88359E84

Source 4: Dummy from KeyDB
Output file CRC: 88359E84

Source 5: Just pasting in my key in JungleFlasher
Output file CRC: 88359E84

From what I can tell, Yafeu and .:Dino:. are correct. For anyone who cares, does it seem like these findings actually support their statements, or have I overlooked something in my tests?

pudink · « **Reply #80 on:** June 16, 2011, 04:05:00 AM »

guys is there an UPDATED WALKTHROUGH to flash your drive,i am gonna do this for the first time and a noob friendly one would be good.
thanks

Rammieone · « **Reply #81 on:** June 16, 2011, 04:34:00 AM »

Yes just follow the one Inc in the JungleFlasher Package mate

astr4twin · « **Reply #82 on:** June 16, 2011, 01:24:00 PM »

QUOTE(EpsilonMirror @ Jun 16 2011, 08:28 AM)

I don't think I've seen anyone mention anything like this, but I had a thought. And please anyone more knowledgeable, feel free to chime in and correct me if I'm wrong. I seem to remember someone saying that MS couldn't dump drive firmware because of legal reasons, something about them not owning the firmware.(I honestly can't remember who said it, but I think it was a scene dev)
If this is the case, and knowing that the new stock firmwares don't have anything to do with xgd3 since the hitachis can still read the discs, is it possible that these new firmwares are completely written by MS using technical docs supplied by the drive manufacturers? It seems like that would get them around the legal issue of reading the firmwares(if it even exists), thus allowing them to do so in future updates. I feel like that would explain the lack of a new firmware for the hitachis, since they are apparently a pain and there are probably very few left in the wild that aren't either in banned or rrod consoles.
Again, It was just a thought I had and I'm not entirely sure it is correct at all.

I was being a little paranoid myself with a thought i had. I was thinking how nearly everyone would be reflashing and accepting the new dashboard update on the same day. I would guess M$ could log to see all those consoles that stayed off live suddenly accept their update and start playing on live again on the same day. Of course this wouldnt be proof for them as someone who has always been on stock could also be updating on the same day but it just makes me think, maybe were all on the watch list

.:Dino:. · « **Reply #83 on:** June 17, 2011, 03:10:00 AM »

Nice work driftfox, thanks for testing this. So as of this update, only the drive key differentiates between any liteon firmware

sminitis · « **Reply #84 on:** June 17, 2011, 06:43:00 AM »

just flashed my benq drive after the update.its working great.also repatched assassins creed brotherhood with abgx360 and its working.thanks c4eva

Hitokiri-Snake · « **Reply #85 on:** June 17, 2011, 10:20:00 AM »

QUOTE(pt6 @ Jun 16 2011, 04:33 AM)

hey,

I successfully flashed LT 1.9 on my phat LiteOn, but I wanted to report somethings strange i encountered...

I was on LT Plus and wanted to flash back to stock firmware before updating the dash and then flashing to LT Plus 1.9...

So I tried to flash my orig fw dump... the flash went through and appeared to be successful but I could not eject the dvd tray anymore...

so I flashed the fw in the OW folder in LiteOn_Post_13141... I know it's the wrong fw since i was pre dash update...

the flash went through successfully (was able to eject tray)...

I then updated the dash successfully, and here's the strange thing:

I inserted my original Halo Reach and the dvd drive did not recognize it and displayed PLAY DVD. I tried my original Halo ODST, same thing... I tried a backup, same thing...

very strange to me since the dash update flashed a stock fw onto the drive and originals should work... no idea what happened here...

I then flashed LT Plus 1.9 successfully and now originals and backups work...

anyways, thanx C4Eva - great work !

Did you remember to use your DVD key when you flashed the firmware from the LiteOn_Post_13141 folder? No DVD key = Play DVD. That's the only thing I can think of

jedijakeyboy · « **Reply #86 on:** June 17, 2011, 03:33:00 PM »

Thanks for the release C4e......

I am a little confused if this is live safe or not. I thought it was not and that the 2.0fw will be..??

If this is safe what will the difference be from 1.9 to 2.0?

X4life3 · « **Reply #87 on:** June 17, 2011, 04:01:00 PM »

QUOTE(jedijakeyboy @ Jun 17 2011, 05:33 PM)

Thanks for the release C4e......

I am a little confused if this is live safe or not. I thought it was not and that the 2.0fw will be..??

If this is safe what will the difference be from 1.9 to 2.0?

Yes it is live safe, that is why C4E made 1.9 so people could go back online using backups, if it wasnt live safe there would be no point to it as LT+ 1.1 isnt live safe and you can use it to play on the new dash but you will most likely get flagged for a ban. I think 2.0 is the same thing but will allow you to play using the new disk format.

sugarshane · « **Reply #88 on:** June 17, 2011, 07:47:00 PM »

Ok..... Some insight would be really helpful here. I have the old LT+ firmware and haven't updated yet. Should I update first and then flash? Or should I just flash now and then do the update?

xD34DL1N3Rx · « **Reply #89 on:** June 17, 2011, 08:58:00 PM »

QUOTE(sugarshane @ Jun 17 2011, 08:47 PM)

Ok..... Some insight would be really helpful here. I have the old LT+ firmware and haven't updated yet. Should I update first and then flash? Or should I just flash now and then do the update?

I believe the preferred method is re-flash to stock fw, update, flash to lt+ 1.9.

Author Topic: C4Eva iXtreme LT v1.9 for Samsung and LT+ v1.9 for Benq and phat Lite- (Read 1004 times)