|
Problem flashing liteon 83850c
|
|
|
MA5H3D
Newbie
|
20. November 2009 @ 23:23 |
Link to this message
|
Can someone tell me what i'm doing wrong here?
Using the xecuter ck3 conectivity kit i've I've gone through the process of flasing the liteon 83850c drive with jungle flasher and everything was going well.
I had a good key and created the dummy file then i spoofed it onto the ix16-liteon838 file and saved it. Then i went along to mtk flash 32 and clicked lite-on erase and followed the process. Everything was going fine untill it came to "Writing target buffer to flash". It then says "Writing Bank 2:" and the program froze up and all i could do was end the program.
Now the drive doesn't open or close and jungle flasher doesn't even see the drive anymore. I've also tried to find it with dos flash but i don't seem to be able to find the drive anymore.
I have 4 .bin files - Dummy, Identify, Inquiry and Serial, and I have a jf text file which seems to contain my DVD key. I'm really lost here! Have i done something wrong? Can I fix it? Should i be using a different program? Should I be buying a new Xbox?
Thanks.
|
|
Advertisement
|
|
|
|
Moderator
|
21. November 2009 @ 04:28 |
Link to this message
|
Thread teleported out of the old type xbox forums. Please be more careful where you post in future.
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules *** |
Senior Member
|
21. November 2009 @ 06:28 |
Link to this message
|
Originally posted by MA5H3D:
Can someone tell me what i'm doing wrong here?
Using the xecuter ck3 conectivity kit i've I've gone through the process of flasing the liteon 83850c drive with jungle flasher and everything was going well.
I had a good key and created the dummy file then i spoofed it onto the ix16-liteon838 file and saved it. Then i went along to mtk flash 32 and clicked lite-on erase and followed the process. Everything was going fine untill it came to "Writing target buffer to flash". It then says "Writing Bank 2:" and the program froze up and all i could do was end the program.
Now the drive doesn't open or close and jungle flasher doesn't even see the drive anymore. I've also tried to find it with dos flash but i don't seem to be able to find the drive anymore.
I have 4 .bin files - Dummy, Identify, Inquiry and Serial, and I have a jf text file which seems to contain my DVD key. I'm really lost here! Have i done something wrong? Can I fix it? Should i be using a different program? Should I be buying a new Xbox?
Thanks.
in mtkflash tab click on intro/device id and see if it will show the drive again.
you need to make sure you have all your drivers installed correct.
I have lost all and any respect i had for this site!
|
|
MA5H3D
Newbie
|
21. November 2009 @ 11:48 |
Link to this message
|
Ok,
As far as i can tell all my drivers are installed properly with the yellow explanation marks in the right place.
When i try the intro/device id button and power off/on, the status changes from 0xD2 to 0x52 but it still says "Vendor: no drive detected!"
Then under that in the white area it says:
"Sending Vendor Intro to port 0xD8B0
Status 0xD2
Re-sending Vendor Intro:
.................................................................... .................................................................... .................................................................... ....................................................................
Device Intro failed!"
I'm 100% sure i'm using the right sata port as it's the same as when it was at the start of all this.
If i click on erase liteon and do the power off/on i can sometimes get 0x72 status and then it goes into the correct mode, but the program just frezes again when i try to write.
Am i doing something wrong?
Can i use the same .bin files that jungle flasher has made (Dummy, Identify, Inquiry and Serial) with another program? If so whats the best way to find the drive again and actually erase/flash it?
Thanks in advance.
This message has been edited since posting. Last time this message was edited on 21. November 2009 @ 12:03
|
Senior Member
|
21. November 2009 @ 12:01 |
Link to this message
|
your drive is bricked,get it back in vendor mode,JF should pick it up and rewrite the firmware,just keep powering off and on,till it gets in the vendor mode
This message has been edited since posting. Last time this message was edited on 21. November 2009 @ 12:02
|
Member
|
21. November 2009 @ 12:03 |
Link to this message
|
JF will not detect your drive because it doesnt have any firmware on it. Open the try half way and click on Intro/Device ID. Drive properties box will says "Vendor:No drive detected!" because there is no firmware on the drive but Port properties will have info about the drive and in the Device line it should say VIA VT6421 RAID Controller if your using a VIA6421 SATA card. this means the SATA card has detected the drive. Now try sending the Intro.Device ID command and power cycle the drive,now you should get the 0x72 status
|
Senior Member
|
21. November 2009 @ 12:06 |
Link to this message
|
Originally posted by Farrukh49:
JF will not detect your drive because it doesnt have any firmware on it. Open the try half way and click on Intro/Device ID. Drive properties box will says "Vendor:No drive detected!" because there is no firmware on the drive but Port properties will have info about the drive and in the Device line it should say VIA VT6421 RAID Controller if your using a VIA6421 SATA card. this means the SATA card has detected the drive. Now try sending the Intro.Device ID command and power cycle the drive,now you should get the 0x72 status
if there is no firmware the tray cannot open,am i wrong?
|
|
MA5H3D
Newbie
|
21. November 2009 @ 12:10 |
Link to this message
|
|
ok,
If i click on erase liteon and do the power off/on i can sometimes get 0x72 (more often 0x7f) status and then it goes into the correct mode, but the program just frezes again when i try to write.
The intro device id button gives me lots of random numbers, lots of 0x52's or 0x80's but never a 0x72. Is it a matter of keep trying or is there another way to do this?
|
|
MA5H3D
Newbie
|
21. November 2009 @ 12:29 |
Link to this message
|
|
Ok,
If i do the liteon erase button, i can get it to go into vendor mode and 0x72 every time but not by just pressing intro/device id. BUT, when in vendor mode if i press write the program freezes on "Writing Bank 0."
What should i do?
Can i use a different program to do this bit? Is there anything as simple as jungle flasher that will work on a liteon 83850?
|
|
drmax
Junior Member
|
8. January 2010 @ 12:18 |
Link to this message
|
Originally posted by MA5H3D:
Ok,
If i do the liteon erase button, i can get it to go into vendor mode and 0x72 every time but not by just pressing intro/device id. BUT, when in vendor mode if i press write the program freezes on "Writing Bank 0."
What should i do?
Can i use a different program to do this bit? Is there anything as simple as jungle flasher that will work on a liteon 83850?
Hey, what did you find out? I have a liteon that is in the same boat. Mine froze up, when turning power off/on. I am using onboard nividia chipset, which i think/thought is conflicting with my setup. I'm ordering a pci vt6421. Let me know. Your drive is only bricked, until you are able to get into the vendor mode, so don't lose too much sleep over it yet. I had this happen with mine with my initial flash, and got it up again. DM
|
|
monkijin
Member
|
8. January 2010 @ 14:05 |
Link to this message
|
erase the drive and get 0x72 status and restart pc and use usb flash drive and write firmware using dosflash.
i have had that problem myself
normally pissed off
|
|
MA5H3D
Newbie
|
25. January 2010 @ 16:24 |
Link to this message
|
Hi all,
I couldn't be bothered replying before because i solved the problem and didn't come back to this site again. If anyone's having this problem, you MIGHT be able to solve it the way i did...
All i did was use a different sata port! Thats it!
When I decided to flash my 360, I bought a flahsing kit that came with all the bits and i bought a sata card port thing that went in my computer.
Basically i hooked it all up using the sata port that was now visable at the back of my computer with all the other sockets and started the process, but when it came to writing the new firmware back onto the 360 drive i couldn't get it to work. After trying everything everyone told me to try on here, I tried opening my pc and hooking up the 360 drive to an internal sata port (on the same card). Then it just worked!
I have no idea if this will help anyone else, maybe i just got lucky?? But thats how i solved this issue.
Be Lucky!
bye.
|
|
Advertisement
|
|
|
|
drmax
Junior Member
|
25. January 2010 @ 16:30 |
Link to this message
|
Originally posted by MA5H3D:
Hi all,
I couldn't be bothered replying before because i solved the problem and didn't come back to this site again. If anyone's having this problem, you MIGHT be able to solve it the way i did...
All i did was use a different sata port! Thats it!
When I decided to flash my 360, I bought a flahsing kit that came with all the bits and i bought a sata card port thing that went in my computer.
Basically i hooked it all up using the sata port that was now visable at the back of my computer with all the other sockets and started the process, but when it came to writing the new firmware back onto the 360 drive i couldn't get it to work. After trying everything everyone told me to try on here, I tried opening my pc and hooking up the 360 drive to an internal sata port (on the same card). Then it just worked!
I have no idea if this will help anyone else, maybe i just got lucky?? But thats how i solved this issue.
Be Lucky!
bye.
Yep, read about your issue you spk of. That rear port on a via vt6421 card (which I think you talking about) is not the same as the 2 intertal ports. I am still waiting on my via card to arrive. My usb flash drive will not even detect the drive, hooked up to my motherboard sata. Some are lucky with the nforce chipset...i was not.
|
