Post by: lord^infamous on October 26, 2006, 01:10:00 AM
Post by: Textbook on October 26, 2006, 09:20:00 AM
This is a common problem among Xbox 1 Samsung drives as well. It is in fact a mechanical problem with the motor or motor belt. The motor that controls the tray opening/closing is the same motor that lowers the laser assembly. When this speed gets slower for some reason or because the rubber band stretches out, we run into two problems.
1. Tray getting stuck while ejecting. This motor lowers the laser assembly. When it cannot lower it fast enough, the tray is trying to eject while the assembly is still "up." The laser assembly is still stuck to the drive lid's magnet that holds the discs in place. That's why if your tray is getting stuck, if you get it a good whack on the lid of the drive, it opens. You "unstuck" the magnet, making the laser assembly move down, which then let your tray continue opening. If you don't believe me, take off your lid and you'll never get the tray getting stuck.
2. The other problem is what you stated, the drive refusing to stay closed. You try to close the drive and the motor doesn't close it hard enough. When this happens, the tray pops back out. I was having the same problem and can be seen on a video tutorial I made where I close the tray and it pops back out and I mutter "my stupid drive."
My drive was having both problems. My friend's drive is only having the first, where his drive gets stuck while opening. You seem to be only having problem 2. Thing is, they are related and when it gets worse, both problems will show up. Here is how I fixed both of my problems.
By using the rubber band instead of the belt motor, my drive has yet to get stuck once and has yet to close one time. Before this, I had a 0% eject rate while the console was vertical and at times I had to eject the tray in 9 times before it would stay closed. Now, I can open the tray every time, even in vertical. And I haven't had it refuse to close once. Just give it a try, might work for you. It did for me.
Post by: stowelly on October 27, 2006, 01:57:00 AM
anyone in the uk think they can repair this? or at least point me in the right direction, thanks
Post by: stowelly on October 27, 2006, 04:39:00 AM
Post by: stowelly on October 27, 2006, 06:29:00 AM
Post by: stowelly on October 28, 2006, 12:21:00 AM
Post by: majik655 on October 28, 2006, 01:14:00 AM
QUOTE(stowelly @ Oct 27 2006, 11:28 PM) 
anyone?
well since you tried the rubber band thing.. (maybe a different band size again???) but if you are sure that did not work.. maybe try this thing... even though I think you are right.. it is stuck in a mode of some sort.
here is the link (click on the picture for bigger pictures... kinda bad quality though)
http://forums.xbox-s...howtopic=550832
Also.. you state you got it going like 1 out of 20... you should have an original disk laying around.
TRY to get that disk in the drive some how...you want it to read it.. but thats gonna be the problem..but there was some threads way back that said something to the effect of sticking in a original game to get it out of mode b. type of thing...so this is what I did one time.. with something that kinda seems like your issue too.
Its like the drive is backwards somehow huh? so try to trick it back.. like manually opening the drive then shutting off power.. see what happens.. more than likely it just sits open..but put in an original game.. and then turn on.. maybe it closes?
maybe at some point stop it from going in automatically... see what happens then when you shut it manually again from there??
my point is.. try all ways to trick it back.. different things etc etc.. just to see what happens.
Post by: stowelly on October 29, 2006, 01:17:00 AM
Post by: ntloser on October 29, 2006, 01:26:00 AM
If the drive is not physically damaged from the Xecuter trash.. maybe using the bad flash recovery method will help;
The firmgaurd in the 4.x firmware is the same "protection" used in the ms 28 firmware. Hence, you can flash a drive with 4.x firmware withOUT it being in 0800 mode using the bad flash recovery method. This may be the thing to try since you can't be sure you are getting the drive into 0800 mode. Hopefully, once you get your original firmware back on, the drive will behave normal and you can try to reflash.
Only use the xecuter trash on hatachi drives.
Good luck
Post by: stowelly on October 29, 2006, 01:48:00 AM
Post by: ntloser on October 29, 2006, 01:54:00 AM
Post by: mr-smith on October 29, 2006, 05:04:00 PM
Post by: stowelly on October 29, 2006, 11:46:00 PM
Post by: ntloser on October 30, 2006, 01:07:00 AM
QUOTE(stowelly @ Oct 30 2006, 02:53 AM)
nah im using nforce
You need to use a SATA card or onboard SATA controller, with a VIA chipset in order to do a bad flash recovery with an MS 28 / xtreme 4.x based T-S drive.
What concerns me is that the drive isn't detected at all. I think it should at least be detected on the nforce based sata controller. Either way the VIA card you need is 9 - 15 dollars and would definitely be worth your while. If you do successfully get your drive flashed and want to flash it again again without 0800 mode. You need that card. Or, say you do the swappy swap and get a system with an MS 28 based drive you can flash that without having to solder.
Post by: stowelly on October 30, 2006, 01:14:00 AM
QUOTE(ntloser @ Oct 30 2006, 08:14 AM)
You need to use a SATA card or onboard SATA controller, with a VIA chipset in order to do a bad flash recovery with an MS 28 / xtreme 4.x based T-S drive.
What concerns me is that the drive isn't detected at all. I think it should at least be detected on the nforce based sata controller. Either way the VIA card you need is 9 - 15 dollars and would definitely be worth your while. If you do successfully get your drive flashed and want to flash it again again without 0800 mode. You need that card. Or, say you do the swappy swap and get a system with an MS 28 based drive you can flash that without having to solder.
i get 2 different error code when i esc out of mtkflash 00 for when its not powered on and i think its 51 (cant remember exactly) when expecting 70, so its obviously there it just gets a different status code.
whats the reason the nforce wont work for the bad flash recovery?
Post by: ntloser on October 30, 2006, 01:23:00 AM
QUOTE(stowelly @ Oct 30 2006, 04:21 AM)
i get 2 different error code when i esc out of mtkflash 00 for when its not powered on and i think its 51 (cant remember exactly) when expecting 70, so its obviously there it just gets a different status code.
whats the reason the nforce wont work for the bad flash recovery?
I don't know why a VIA chipset is required, but the tutorials and huge threads on flashing ms28 using bad flash recovery method says it is.
I would also like to know the details of why VIA is needed.
Post by: akz on September 27, 2007, 04:56:00 PM