Jungle Flasher Tutorial for STOCK 83850C Lite-ON (pictures included)

I have done a bunch already and they worked out fine. I do have a via 6421 sata card. Have no clue why this one was giving me problems. My buddy just ended up returning it to futureshop can he's gonna grab another one. LOL.

 

did 6 today and came across
dg-16d2s09c
a0a2
83850c
july 2009

No ca do ,...i really wonder what it is ,..hope we can find out soon enough

 

Just reading from other forums with info on this, there has been some people with success on dumping the encrypted DVDkey of July manufactured Lite-ONs. If you have done 6 others, were any others July 2009 or just one?

 

i had 2 that where the same as this one ,..no idea why one would work and not the other.
In my area i talked with another modder and he had the same issue. If any1 finds what the issue is please advise us all

 

Hey Leerage. Do you have Tut in how to flash The Hitachi drive with Jungleflasher. All your tutorial are one of the best. I have learn how to flash all the drives exempt the Hitachi drive. No one has good tutorial at all. Thank you for your Help.

 

Thank you.

Unfortunately I haven't made a tutorial yet for Hitachi. There are many different firmware revisions and variables. Would take some time to make the tutorials. I would recommend the Jungle Flasher tutorial linked in my signature. Takes you to the PDF on http://www.jungleflasher.net

It is very very well put together. If you have any questions, don't hesitate to ask. If you read the tutorial and feel you have questions, you can start a thread or PM me.

 

If anyone can give me their lot # for their xboxes that are giving them the null key dump, that would be great. I have an Elite waiting to be opened and dont want to until I can verify its before the trouble starts.

 

360drives.com

 

I was asking the people who were unable to specifically flash their lite-ons due to the keys returning all 0's. I wanted to see what batch theirs was in before I open mine.

EDIT: A very relevant thread to the Post Aug/09 dump problem.

http://forums.xbox-scene.com/index.php?showtopic=692490&st=15

 

so if you have a lite-on made in or after august 2009 and your having trouble extracting the key. What do you? is there any solution yet?

 

Hey there people,

Have flashed my lite on drive with 1.6 in jf and i can c it in bios but i wanted to flash to 0800 and it cant be seen in jf anymore, although drive is working in xbox.

any ideas y cant c drive in jf

 

Not re flashing now as i shouldnt need to since you can start drive in 0800 by having it half open while booting pc,

But windows wont read it as a drive just my bios,

If anybody had the same prob or any ideas thanks

 

What type of SATA chipset are you using?

 

I greet all.
I am from the Poland and this is the text from the translator. I have the quite atypical problem. Namely was I reading the key Liteona 8385 the programme JungleFlasher 0.1.66beta and was I using power supply the console. I tried first to read the key single - time switching off reinforcing from the drive in the moment of closing and connecting him to the computer and then hand closing and opening klapki, but it was not successful to read the key.
I then already switched off power supply 2 some read times and key oneself, I hope that good, but there is no certainty to puki here he will not test him in some drive. But drive and console oddly behave now, namely the diode Power winks the whole time after the inclusion the console and he opens the drive alone if I try him to close this is closes on the moment and again opens. If I switch off the console the button power the drive is closes and opens with the return and the console one switches off with the open klapką of the drive.
I will add that I did not erase the firmwaru of the drive and did not in this new and did not even connect the cable sata from the console because I do not know as this will end.
What did I make and or this will give oneself to come unscrewed?

 

you might want to find a better translator. we would love to help you, but i cant understand a word you are saying.

 

I Thank for the interest approx.. Tomorrow I will try differently to translate this. Thanks.

 

welcome

 

First translator:
I greet again from the Poland. I described all from the beginning. I read the key from drive DVD. I used power supply the console. I disconnected two times while reading the key power supply from drive DVD. Dodge it was successful to read. I already have new ready firmware to the drive. I did not install him yet because I have the problem.
If I switch off the console this opens drive DVD and becomes so, in the open position. And 2 are cases now:
1.. If I turn on the console the button „Power” this is closes the drive first and he opens then alone. He so already becomes. „Opening”is shows at the TV. The diode „Power”winks the whole time.
2.. If I turn on the console the button „Eject” this is closes the drive. He is at the TV „Unlock the drive”. The diode „Power”winks the whole time.

What oneself could stand?

Second translator:
Hello again from the Polish. I described everything from the beginning. I read the key from the DVD drive. I used the power of the console. While reading the key twice disconnected power from the DVD drive. The key could be read. I have already finished a new firmware to the drive. Not yet Uploader because I have a problem.
If you turn off the console that opens the DVD drive and so is, in the open position. And now there are 2 cases:
1. If I turn the console by pressing the "Power" is the first drive and then closes itself opens. Already is. On TV shows are "Open". All the time blinking LED "Power".
2. If I turn the console by pressing the "Eject" the drive is closed. On TV is "Open Drive". All the time blinking LED "Power".

What oneself could stand?

 

Connect the drive back to the PC. Make sure the proper I/O port is selected (the one you have the Lite-ON connected to). Click Intro/ Device ID to gain access to the flash chip. Re-write the firmware.

 

Sending Vendor Intro to port 0x0960
Status 0xD0
Re-sending Vendor Intro:
......................................................................
......................................................................
......................................................................
......................................................................
......................................................................
......................................
Device Intro failed!