|
|
|
Samsung MS28 Flashing Green Light
|
|
|
Thosmos
Member
|
11. January 2011 @ 15:08 |
Link to this message
|
|
Hopefully this hasn't been posted resently. didn't find anything, but after flashing my MS28 to LT+, I am getting a flashing center light. Cannot eject. Reflashed to 1.51 thinking maybe it would make a difference, but no go. I had another MS28 with a bad laser, so I flashed it with the key and LT+ as well, with the same results. (Flash results in JF 1.78 all show good - hit outro to get out of vendor mode, and reports the drive)
I had an extra Liteon. I didn't flash it, but installed, and I don't get the flashing light. I'm going to try and spoof this Liteon for a more complete test... But this is strange.
Maybe the key is bad that I saved. I'll know more later. Anyone ever navigate this one?
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 11. January 2011 @ 15:12
|
|
Advertisement
|
 |
|
|
|
deepc266
Member
|
11. January 2011 @ 15:18 |
Link to this message
|
the flashing light means the xbox cant see the DVD drive. last time i saw it a cable wasn't plugged in good or was left off.
|
Senior Member
|
11. January 2011 @ 15:28 |
Link to this message
|
Originally posted by deepc266:
the flashing light means the xbox cant see the DVD drive. last time i saw it a cable wasn't plugged in good or was left off.
easy fix,to fix the samsung,use iprep to flash it,sometimes jf doesnt work perfect
|
|
Thosmos
Member
|
11. January 2011 @ 15:50 |
Link to this message
|
Originally posted by infam0us:
Originally posted by deepc266:
the flashing light means the xbox cant see the DVD drive. last time i saw it a cable wasn't plugged in good or was left off.
easy fix,to fix the samsung,use iprep to flash it,sometimes jf doesnt work perfect
Okay, but two drives I've installed, both MS28's with the same result. So, I think that would eliminate the hardware (drive) being bad. And installing the Liteon and not getting the light would eliminate the cable...
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
|
Senior Member
|
11. January 2011 @ 16:38 |
Link to this message
|
installing the liteon without you flashing it is the key here. It seems that the firmware is not staying on the drives after you flash them. If so, the drive would eject and you wouldn't have a green flashing light. Like infam0us mentioned above, try to use iprep on the samsung. Also, even if you have the wrong dvdkey, the drive will still eject as long as there is firmware on it (reason why the liteon is working but won't play games). If the 360's drive is originally a samsung, I would stick with it if you plan on playing on live. Instead of hitting the outro button, just try to power the drive off and then back on after re-flashing. If you can eject the drive after that, then it will work fine in your 360 as long as you've flashed the right dvdkey. I've had a few stubborn sammys in the last few years. Good Luck!
|
|
Thosmos
Member
|
11. January 2011 @ 20:06 |
Link to this message
|
Originally posted by BillB:
installing the liteon without you flashing it is the key here. It seems that the firmware is not staying on the drives after you flash them. If so, the drive would eject and you wouldn't have a green flashing light. Like infam0us mentioned above, try to use iprep on the samsung. Also, even if you have the wrong dvdkey, the drive will still eject as long as there is firmware on it (reason why the liteon is working but won't play games). If the 360's drive is originally a samsung, I would stick with it if you plan on playing on live. Instead of hitting the outro button, just try to power the drive off and then back on after re-flashing. If you can eject the drive after that, then it will work fine in your 360 as long as you've flashed the right dvdkey. I've had a few stubborn sammys in the last few years. Good Luck!
Thanks for the tip. I did not have the drive open when flashing though. (if this relays any info) I usually do this with Liteon drives, but discovering the device in JF by powering the CK3 seemed to work fine. (though the eject button has never worked) Erase and write seems to work fine as well.
I'll try JF with the 360 powering then, and see if I can eject while connected.
Then, if that doesn't work. Maybe try iprep.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 11. January 2011 @ 20:07
|
|
Thosmos
Member
|
11. January 2011 @ 21:00 |
Link to this message
|
Originally posted by Thosmos:
Originally posted by BillB:
installing the liteon without you flashing it is the key here. It seems that the firmware is not staying on the drives after you flash them. If so, the drive would eject and you wouldn't have a green flashing light. Like infam0us mentioned above, try to use iprep on the samsung. Also, even if you have the wrong dvdkey, the drive will still eject as long as there is firmware on it (reason why the liteon is working but won't play games). If the 360's drive is originally a samsung, I would stick with it if you plan on playing on live. Instead of hitting the outro button, just try to power the drive off and then back on after re-flashing. If you can eject the drive after that, then it will work fine in your 360 as long as you've flashed the right dvdkey. I've had a few stubborn sammys in the last few years. Good Luck!
Thanks for the tip. I did not have the drive open when flashing though. (if this relays any info) I usually do this with Liteon drives, but discovering the device in JF by powering the CK3 seemed to work fine. (though the eject button has never worked) Erase and write seems to work fine as well.
I'll try JF with the 360 powering then, and see if I can eject while connected.
Then, if that doesn't work. Maybe try iprep.
I flashed again, using the power of the 360. no change. but this is what i get in JF:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.78 Beta (183)
Session Started Tue Jan 11 15:41:29 2011
This is a 32 bit process running on a 32 bit CPU
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 1 Com Ports.
Found 1 windows drives C:
Found 0 CD/DVD drives
Sending Sammy_Un_Lock to Drive on port 0xD8A0
Stage 1, Complete!
Stage 2, Complete!
Stage 3, Complete!
Done!
Sending Vendor Intro
Requesting Device ID
Manufacturer ID: 0xBF
Device ID: 0xB6
Flash Name: SST(SST39SF020)
Flash Size: 262144 bytes
Loading firmware file C:\Users\Thos\Desktop\Franks Toshiba 360\SAM-OFW.bin
MD5 hash: 76c55cd6cb258377ebbc2a3e5d92ca5d
Inquiry string found
Identify string found
Drive key @ 0x40EC ****************************** (edited)
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Loading firmware file C:\Users\Thos\Desktop\New LT+ Firmware\iXtreme-LT_Plus_Firmware_Pack\Firmware\Samsung_iXtreme_LT_v1.0\ix-ltv1.0-sammy.bin
MD5 hash: 6f7dd0c34da043f4b5d29828b661bba0
Genuine iXtreme Samsung LT
Inquiry string found
Identify string found
Drive key @ 0x401A 00000000000000000000000000000000
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: iXtreme LT
Spoofing Target
DVD Key copied to target
ID strings already match
Serial data already matches
Getting Status from port 0xD8A0
Parallel flash found with Status 0x70
Writing target buffer to flash
Erasing Bank 0: ................
Writing Bank 0: ................
Erasing Bank 1: ................
Writing Bank 1: ................
Erasing Bank 2: ................
Writing Bank 2: ................
Erasing Bank 3: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !
Sending Vendor Outro to port 0xD8A0
Key found in KeyDB at record (11 - Franks Toshiba 360)
Key is: ****************************** (edited)
Key has been tested and verified, thanks C4eva !
Drive is Samsung..
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
|
|
Thosmos
Member
|
11. January 2011 @ 21:51 |
Link to this message
|
|
Okay, I could be ready for iprep. I've used it once with success, but cannot remember. If I have the OFW already, do I just put it on the root of the thumb drive? And is there a version of iprep that supports LT+? I have an older version for iextreme and it won't load LT.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 11. January 2011 @ 21:51
|
|
peluynati
Senior Member
|
12. January 2011 @ 00:02 |
Link to this message
|
first let me state the obvious there is no LT+ for samsung LT 1.0 is as far as it goes as stated by C4EVA there is no need for plus on samsung drives, the problem i see in you JF readout it that your drive key is not getting spoofed into the firmware if you look at the write sector it says the drive key is 000000000000000 make sure when you load your original firmware and then chose the lt 1.0 sammy you hit the spoof to target button so you get your key down at the bottom. the reason it is blinking is there is no key on it.
|
|
peluynati
Senior Member
|
12. January 2011 @ 00:03 |
Link to this message
|
LT_Plus_Firmware_Pack\Firmware\Samsung_iXtreme_LT_v1.0\ix-ltv1.0-sammy.bin
MD5 hash: 6f7dd0c34da043f4b5d29828b661bba0
Genuine iXtreme Samsung LT
Inquiry string found
Identify string found
Drive key @ 0x401A 00000000000000000000000000000000 <------------------------- THIS PART
|
|
Thosmos
Member
|
12. January 2011 @ 00:15 |
Link to this message
|
Originally posted by peluynati:
first let me state the obvious there is no LT+ for samsung LT 1.0 is as far as it goes as stated by C4EVA there is no need for plus on samsung drives, the problem i see in you JF readout it that your drive key is not getting spoofed into the firmware if you look at the write sector it says the drive key is 000000000000000 make sure when you load your original firmware and then chose the lt 1.0 sammy you hit the spoof to target button so you get your key down at the bottom. the reason it is blinking is there is no key on it.
Sorry, double post.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 12. January 2011 @ 00:26
|
|
Thosmos
Member
|
12. January 2011 @ 00:24 |
Link to this message
|
Obviously, I am spoofing target firmware with my OFW. And it shows the key when done. But it's not saving by the time I hit write. For some reason. I did spoof a Liteon (the one with the bad laser that I have) with the OFW MS28 key, and wrote. When installing, I no longer get the flashing light. (Though I cannot test completely, because I have yet to replace the laser.) so, I cannot try and read disks.
But I am using the Sammy 1.0. Which I believe is the latest, downloaded with Xauto.
My method thus far has been:
Intro or unlock for device discovery, getting the x70.
Seeing vendor mode.
Then load OFW, 1.0 Sammy (LT_Plus_Firmware_Pack\Firmware\Samsung_iXtreme_LT_v1.0\ix-ltv1.0-sammy.bin), spoof. Compare keys.
Go to erase, then write. Then outro.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 12. January 2011 @ 00:32
|
|
peluynati
Senior Member
|
12. January 2011 @ 00:47 |
Link to this message
|
|
try once just hitting write and not the erase, its worth a try and do not outro the sammy causes problems just power the drive off and back on
|
|
Thosmos
Member
|
12. January 2011 @ 01:41 |
Link to this message
|
Originally posted by peluynati:
try once just hitting write and not the erase, its worth a try and do not outro the sammy causes problems just power the drive off and back on
I have tried just writing -- since it erases each bank before writing anyway. And I have tried erasing then writing. I am having the same issue with both of the MS28 drives that I have tried on this machine. I guess the key is not comming through in the write process. I'm going to try iprep tomorrow. Does anyone know what version supports the 1.0 Sammy? -- and if I have the key already, do I just save the SAMOFW.BIN to the root of the thumb drive? It's been a few months since I used this method, and I've only done it onece. though it was on a stubborn Liteon!
Though I will try your method, of no outro, and powering the drive off then on again. Anything is worth a try. I've done one Samsung before, and it was all without a hitch. (With JF 1.71, I think... Maybe I should try an older version of JF... Hmmm) Though it seems that as soon as you get semi okay with one drive, you're onto another, and forget how you did the one before it. :)
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 12. January 2011 @ 01:46
|
Senior Member
|
12. January 2011 @ 07:58 |
Link to this message
|
Originally posted by Thosmos:
Originally posted by peluynati:
try once just hitting write and not the erase, its worth a try and do not outro the sammy causes problems just power the drive off and back on
I have tried just writing -- since it erases each bank before writing anyway. And I have tried erasing then writing. I am having the same issue with both of the MS28 drives that I have tried on this machine. I guess the key is not comming through in the write process. I'm going to try iprep tomorrow. Does anyone know what version supports the 1.0 Sammy? -- and if I have the key already, do I just save the SAMOFW.BIN to the root of the thumb drive? It's been a few months since I used this method, and I've only done it onece. though it was on a stubborn Liteon!
Though I will try your method, of no outro, and powering the drive off then on again. Anything is worth a try. I've done one Samsung before, and it was all without a hitch. (With JF 1.71, I think... Maybe I should try an older version of JF... Hmmm) Though it seems that as soon as you get semi okay with one drive, you're onto another, and forget how you did the one before it. :)
Load SAMOFW.BIN as source with jungleflasher to confirm that you have the right key and not just a bunch of zeros. One of the reasons that the samsung might not be taking the firmware is that the tray is not halfway open. You might have to take one of the samsungs apart and manually eject the tray to the halfway position. Try flashing again after that with JF and hopefully it will work for you. It could be something that small that makes you pull your hair out lol.
|
|
Thosmos
Member
|
12. January 2011 @ 10:43 |
Link to this message
|
Originally posted by BillB:
Originally posted by Thosmos:
Originally posted by peluynati:
try once just hitting write and not the erase, its worth a try and do not outro the sammy causes problems just power the drive off and back on
I have tried just writing -- since it erases each bank before writing anyway. And I have tried erasing then writing. I am having the same issue with both of the MS28 drives that I have tried on this machine. I guess the key is not comming through in the write process. I'm going to try iprep tomorrow. Does anyone know what version supports the 1.0 Sammy? -- and if I have the key already, do I just save the SAMOFW.BIN to the root of the thumb drive? It's been a few months since I used this method, and I've only done it onece. though it was on a stubborn Liteon!
Though I will try your method, of no outro, and powering the drive off then on again. Anything is worth a try. I've done one Samsung before, and it was all without a hitch. (With JF 1.71, I think... Maybe I should try an older version of JF... Hmmm) Though it seems that as soon as you get semi okay with one drive, you're onto another, and forget how you did the one before it. :)
Load SAMOFW.BIN as source with jungleflasher to confirm that you have the right key and not just a bunch of zeros. One of the reasons that the samsung might not be taking the firmware is that the tray is not halfway open. You might have to take one of the samsungs apart and manually eject the tray to the halfway position. Try flashing again after that with JF and hopefully it will work for you. It could be something that small that makes you pull your hair out lol.
I will try that, you never know... Has anyone ever had this happen because the disk wasn't open half way?
And getting zeros from my key... That's not the issue. I have cracked my share of drives... That's something that I would have caught back when I did my first flash... But, as I can attest -- there's always something someone knows a fix for that they came across, that can end your frustrations. This repair is for someone at work. A favor. Fixing a RROD and flashing. Since I'm able to get all of this done at work, I never charge anyone. He has said something about taking it appart before, but I saw no signs of tampering. Even the DVD tape was still holding the unit in the tray. Seal wasn't broken on the case. He mentioned upgrading the hard drive and having to take it appart... Obviously he was confused.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 12. January 2011 @ 10:59
|
|
Thosmos
Member
|
12. January 2011 @ 13:31 |
Link to this message
|
I tried iPrep, and I couldn't get the drive to be seen. Using the Via card. Tried flashing with tray half open, no change. Bypassed the Via card, and went with SATA. Discovered the drive and wrote, I'll test it, but still getting this:
Inquiry string found
Identify string found
Drive key @ 0x401A 00000000000000000000000000000000
Even though I also get this:
Key found in KeyDB at record (11 - Franks Toshiba 360)
Key is: ****************************** (edited)
Key has been tested and verified, thanks C4eva !
Drive is Samsung..
(The edited portion had the drive key numbers.)
So, same as before.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
This message has been edited since posting. Last time this message was edited on 12. January 2011 @ 13:32
|
|
peluynati
Senior Member
|
12. January 2011 @ 14:59 |
Link to this message
|
have you tried reading the drive and see what kind of key it comes up with after the flash, also i'm just curious what is the manufacture date on the back of the xbox, also did you say that you had flashed that drive before? or is that the first time you are flashing that box? another thing even though you can get the liteon to start without blinking have you tried replacing the sata, and power cables to make sure they are not bad? the reason for the blinking light is because the xbox does not recognize the drive, this can be caused by many different things, such as no firmware, wrong firmware, bad cables, bad trace, or simply just drive still in vendor mode. when i have this kind of problem i start with the easiest first, IE the cables, if you are sure that the flash is not the problem, then you should start checking there, if you reflowed the board, do it again using wooleys method.
|
|
Thosmos
Member
|
12. January 2011 @ 16:14 |
Link to this message
|
Originally posted by peluynati:
have you tried reading the drive and see what kind of key it comes up with after the flash, also i'm just curious what is the manufacture date on the back of the xbox, also did you say that you had flashed that drive before? or is that the first time you are flashing that box? another thing even though you can get the liteon to start without blinking have you tried replacing the sata, and power cables to make sure they are not bad? the reason for the blinking light is because the xbox does not recognize the drive, this can be caused by many different things, such as no firmware, wrong firmware, bad cables, bad trace, or simply just drive still in vendor mode. when i have this kind of problem i start with the easiest first, IE the cables, if you are sure that the flash is not the problem, then you should start checking there, if you reflowed the board, do it again using wooleys method.
Manufacture date is 6/2006.
First time I've flashed it.
I did it again just now, and noticed that I don't get the:
Drive key @ 0x401A 00000000000000000000000000000000
if I load the LT FW, then the OFW, then spoof. It shows the key number. So, after doing that, and flashing again, when I hit outro, it did finally say drive not found afterwords, which it wasn't doing before. It would send outro, and still show MS28, though the data regarding ports under the connection method would dissapear, and the vendor mode would change back. Only difference, but it's something.
I'll try another sata.
Funny thing -- looking at my saved keys, I did just do another MS28 flash last week. Though I had to get a drive replacement for the DVD -- but it was quite easy.
I ordered the same drive that time around, another MS28.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
|
|
Thosmos
Member
|
12. January 2011 @ 16:26 |
Link to this message
|
Okay, I swapped out the sata and power cable, and am getting the same thing. Blinking center light, won't open.
When replacing with the Liteon, I don't get the light, and it does eject.
I may try and spoof the key to a liteon and see how it goes.
Can I spoof the LT 1.0 Samsung? Or is it just the LT+ that won't spoof? Thought I read that somewhere.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
|
|
peluynati
Senior Member
|
12. January 2011 @ 16:48 |
Link to this message
|
ok do the tray half closed, first tab open source firmware, which is the ofw of the samsung, then JF should say do you want to automatically load LT you say yes, make sure the key is showing on the top and the bottom and they are the same, now go to the third tab, and hit sammy unlock, once the drive is in vendor mode hit write, once the drive has finished writing power cycle the drive, then hit the refresh button and see if it shows back up in the properties, i'm sure you have spent too much time looking at it, and you are just missing something simple, if your computer is seeing the drive then the drive itself is not bad.
|
|
Thosmos
Member
|
12. January 2011 @ 16:56 |
Link to this message
|
I have done this, and the only difference that I see in what you're saying is that I do the unlock before going to the first tab and loading the OFW and the 1.0 or the 1.51 (I've tried both.)
Now I've tried a few other things. I restored to original firmware, and actually got key numbers in the flash detail, and not the 000000000. But this too gave the same results.
Trying to isolate if it's just a bad saved OFW, I loaded the OFW from the MS28 that I did last week, and again got the same thing.
Next I am going to replace the laser on this Liteon, and spoof it with the Sammy OFW.
Now I'm pretty set on trying to get through this, to be able to share the ultimate Sammy horror story! :)
Thanks again all, with suggestions. Of course, I'll keep you posted.
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
|
|
peluynati
Senior Member
|
12. January 2011 @ 17:01 |
Link to this message
|
i'll make one suggestion, when you do the liteon i would not spoof it as samsung firmware just save the key from your sammy firmware and write that key to the liteon, i have had a lot of success by doing that and not spoofing the drive itself as something its not, meanwhile i will hookup some samsung drives and see if i can maybe catch something that may be causing that problem, i have 9 or 10 sammy drives here.
|
|
Advertisement
|
|
|
|
Thosmos
Member
|
12. January 2011 @ 19:27 |
Link to this message
|
Originally posted by peluynati:
i'll make one suggestion, when you do the liteon i would not spoof it as samsung firmware just save the key from your sammy firmware and write that key to the liteon, i have had a lot of success by doing that and not spoofing the drive itself as something its not, meanwhile i will hookup some samsung drives and see if i can maybe catch something that may be causing that problem, i have 9 or 10 sammy drives here.
I will have to remember that method -- I've never tried that.
I did spoof before getting your message though, with success. Guess that rules out a bad key, which is what I was worried about.
Replaced the laser in the Liteon.
Plays originals and back ups.
Thanks to all of you for the help!
Lite-On 74850, Ben-Q 64930, Hitachi 47DJ, Samsung MS28.
|
|
