hello,
please help me
i cant flash any of rom in odin
all the time i recive this result in odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA1_I9300ITVEMA1_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
i cant install from recovey because it say me e: can't mount sd card
i try in anoter computer,and with another USB cable but it again all time
koblomi said:
hello,
please help me
i cant flash any of rom in odin
all the time i recive this result in odin
i cant install from recovey because it say me e: can't mount sd card
i try in anoter computer,and with another USB cable but it again all time
Click to expand...
Click to collapse
did you try all the usb ports on the computer? loose usb connections caused me same problems sometimes!
i try all usb port
and try in anoter computer
is usb debugging enabled on your phone? is kies program closed in the background processes? drivers of your phone installed?
i had CWM so, i think usb debugging enable
drivers installd, and i close all kies agent
usb debugging cannot possibly have any effect on flashing. also, it's not the drivers problem, read the log - it connects successfully, just fails to flash it. so no use trying other ports either. try a different file
Sent from my GT-I9300 using Tapatalk 4 Beta
Restore your backed up EFS folder .
jje
Related
Hi Guys
I was having some trouble connecting my Galaxy S2 to my comp this evening to transfer some photos. Downloaded and installed Kies and it said there was a software update. Went through with it, upgrading to Icecream Sandwich (or w/e its called) but during the installation process it failed (can't remember the exact error message).
My phone is now unable to switch on, just showing the error message:
"Firmware upgraded encountered an issue. Please select recovery mode in Kies and try again."
Unfortunately, Kies will not locate my device and will not go through with recovery.
After some searching I came accross this forum, and specifically http://forum.xda-developers.com/showthread.php?t=1449771]this thread.
I've worked my way through that. I can flash the kernel succesfully through Odin (says pass) but when I try and flash the firmware it fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_NEW_BOOTLOADER.tar.md5 is valid.
<OSM> I9100PBVKL2_I9100PORALB1_I9100PBVKL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Get the same trying to use Bootloader aswell.
Now I'm guessing my warranty is now voided, so is there anything I can do to save my phone or is it completely b0rked?
Help much appreciated.
Some details from under my battery
Model GT-I9100P
SSN: I9100PGSMH
Any other details you need?
Bare in mind i cannot get into the phone at all.
Is it possible that I need to use the ICS recovery package rather than the Gingerbread?
i think u need full rom with pit and ur phone will work
Hi, thanks for your reply.
Unfortunately I'm in work and don't have a comp with full access. Any chance you could possibly link the files I need or at least point me in the right direction.
Many thanks.
Right
I attempted to upgrade to ics last night through Kies, operation failed and phone locked at screen advising need to be redone, have done research and downloaded odin and UK version of firmware but odin keeps failing
Phone is registered with T-mobile in UK
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am becoming rather irritated as dont see any other way of getting phone working again
Any help would be appreciated
Odin and Kies don't play well together. Uninstall Kies and try Odin again.
****Non of this is of any importance. Just chill the f**k out and relax****
Keis removed ands still no joy from Odin - Wife getting a bit paniky now
ilovecheesypuffs said:
Keis removed ands still no joy from Odin - Wife getting a bit paniky now
Click to expand...
Click to collapse
try with a different USB port/cable and see ma8 if the same doesnt wrk then try with a diff computer and check.
ilovecheesypuffs said:
Right
I attempted to upgrade to ics last night through Kies, operation failed and phone locked at screen advising need to be redone, have done research and downloaded odin and UK version of firmware but odin keeps failing
Phone is registered with T-mobile in UK
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am becoming rather irritated as dont see any other way of getting phone working again
Any help would be appreciated
Click to expand...
Click to collapse
When you flash via PC odin don't use .pit file and don't tick repartition (leave all options in odin default). Rom file open as PDA. It should work.
Regards
Sun90 said:
try with a different USB port/cable and see ma8 if the same doesnt wrk then try with a diff computer and check.
Click to expand...
Click to collapse
3 different cables and 5 different ports tried, no other pc in house .
is there nothing else or am i buggered and forever frowned at by my wife for breaking her phone
ilovecheesypuffs said:
3 different cables and 5 different ports tried, no other pc in house .
is there nothing else or am i buggered and forever frowned at by my wife for breaking her phone
Click to expand...
Click to collapse
If you can go into download mode, you can flash another firmware from other regions.
Sent from my potato.
preseodymium said:
If you can go into download mode, you can flash another firmware from other regions.
Sent from my potato.
Click to expand...
Click to collapse
ok bit noobish, i can use say USA i9100 firmware and try that?
ilovecheesypuffs said:
ok bit noobish, i can use say USA i9100 firmware and try that?
Click to expand...
Click to collapse
Yes. So long as it is for your firmware.
Sent from my potato.
Sorry, currently a new member but being the noob I am- it seems I flashed my International I9300 to a different device (SGH-I747)...
My device is stuck on the Samsung start-up (no biggie), and I believe it's soft-bricked but currently I have no idea what to do.
I've been on Odin and followed many guides to get it back to stock but to no avail. It all fails. I believe something with the MTP failing to install is also a problem. I've done the CMD command and went into regedit and a number of other things.
Right now Kies can't even do an Emergency Firmware Recovery won't pick it up.
Also when I get it in Recovery Mode it exits out and turns to a black screen after a couple of seconds.
I follow this : http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
As the PIT seems to PASS but from there all the other PDA's I try to start fail.
---
I can get it into Odin Mode.
And currently has
Product Name : SGH-I747
Custom Binary Download: Yes (7 counts)
Current Binary : Custom
System Status : Official
QualComm SecureBoot: Enable
---
Help would be much appreciated.
How did this occur? Well actually, I just did a Factory Reset when it worked and then it got stuck loading for hours... Then tried to flash something in... Apparently got the wrong one. And here I am.
simonheros said:
Sorry, currently a new member but being the noob I am- it seems I flashed my International I9300 to a different device (SGH-I747)...
My device is stuck on the Samsung start-up (no biggie), and I believe it's soft-bricked but currently I have no idea what to do.
I've been on Odin and followed many guides to get it back to stock but to no avail. It all fails. I believe something with the MTP failing to install is also a problem. I've done the CMD command and went into regedit and a number of other things.
Right now Kies can't even do an Emergency Firmware Recovery won't pick it up.
Also when I get it in Recovery Mode it exits out and turns to a black screen after a couple of seconds.
I follow this : http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
As the PIT seems to PASS but from there all the other PDA's I try to start fail.
---
I can get it into Odin Mode.
And currently has
Product Name : SGH-I747
Custom Binary Download: Yes (7 counts)
Current Binary : Custom
System Status : Official
QualComm SecureBoot: Enable
---
Help would be much appreciated.
How did this occur? Well actually, I just did a Factory Reset when it worked and then it got stuck loading for hours... Then tried to flash something in... Apparently got the wrong one. And here I am.
Click to expand...
Click to collapse
it seems I flashed my International I9300 to a different device (SGH-I747)??? what does this mean? flashed SGH-I747 firmware in I9300? just want to make sure that what i understood is right because your post is making some confusion..
Can you tell me if your device is 16GB or 32GB or 64GB? pit file for all three of them is different. if you will use correct one than this should not fail.. i dont think that mtp has to do anything with odin but if it does than uninstall all the drivers that are currently install(your device drivers) and download and install samsung drivers from here: http://www.mediafire.com/?7iy79emc0bf1fb4 and then try to connect the device again.. I hope this helps you..
suyash1629 said:
it seems I flashed my International I9300 to a different device (SGH-I747)??? what does this mean? flashed SGH-I747 firmware in I9300? just want to make sure that what i understood is right because your post is making some confusion..
Can you tell me if your device is 16GB or 32GB or 64GB? pit file for all three of them is different. if you will use correct one than this should not fail.. i dont think that mtp has to do anything with odin but if it does than uninstall all the drivers that are currently install(your device drivers) and download and install samsung drivers from here: ----------- and then try to connect the device again.. I hope this helps you..
Click to expand...
Click to collapse
Thank you for the response.
Yes I flashed I747 firmware in I9300. I apologize for the poor wording. My device is 16 GB. The one from the thread I linked is said to be used by 16 GB variant, so I believe it works. (Passes)
I don't get that MTP driver error anymore, but now when I try to put a Bootloader in it says that it's an unsupported dev type.
A person got a similar problem here : s3forums.com/forum/galaxy-s3-help/5772-stuck-download-mode-diffrent-device-type-9300-sgh-i747 ( can't post link) but it appears to be bricked flat out...
simonheros said:
Sorry, currently a new member but being the noob I am- it seems I flashed my International I9300 to a different device (SGH-I747)...
My device is stuck on the Samsung start-up (no biggie), and I believe it's soft-bricked but currently I have no idea what to do.
I've been on Odin and followed many guides to get it back to stock but to no avail. It all fails. I believe something with the MTP failing to install is also a problem. I've done the CMD command and went into regedit and a number of other things.
Right now Kies can't even do an Emergency Firmware Recovery won't pick it up.
Also when I get it in Recovery Mode it exits out and turns to a black screen after a couple of seconds.
I follow this : http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
As the PIT seems to PASS but from there all the other PDA's I try to start fail.
---
I can get it into Odin Mode.
And currently has
Product Name : SGH-I747
Custom Binary Download: Yes (7 counts)
Current Binary : Custom
System Status : Official
QualComm SecureBoot: Enable
---
Help would be much appreciated.
How did this occur? Well actually, I just did a Factory Reset when it worked and then it got stuck loading for hours... Then tried to flash something in... Apparently got the wrong one. And here I am.
Click to expand...
Click to collapse
I think mate you should check if your bootloader in locked or unlocked. As you mention above about QualComm Secure boot :Enable. may be before you was using gt-i9300 firmware it must be unlocked but after you flashed wrong firmware may be your bootloader got locked.
try to download complete stock 4.3 firmware from sammobile.com for correct variant i.e GT-I9300.
Download it and extract it and you will get .tar files
download latest Odin ( google it ) and open it.
put your phone in download mode by pressing volume down + home key + power key for few deconds until download mode screen appear.
press volume up key to goto download mode. connect your phone to your computer and wait till it install all the necessary driver. if you drivers are not installed properly then you have to manually installe the driver for your phone. download galaxy toolkit for s3 from xda and install it. search for the folder name galaxy toolkit in your computer. basically it will be in c:/ drive. open that folder and you will find driver folder under it. Inside the driver folder there will .exe file of driver. but before installing disconnect your phone computer and then install the driver. after the installation of your driver plug in again and wait till it install all the drivers.
Inside odin you must have to see that there is COM ID in 1st box and below it is written attached. if you dont see that then your driver are not installed correctly. uninstall and install it again.
after the driver install click on AP and select the AP .tar file that we extracted after downloading. select the appropriate file associated with it.
click on start and wait few minutes till the process gets complete.
If all things goes right you may get your phone back again.
Mustakim_456 said:
I think mate you should check if your bootloader in locked or unlocked. As you mention above about QualComm Secure boot :Enable. may be before you was using gt-i9300 firmware it must be unlocked but after you flashed wrong firmware may be your bootloader got locked.
try to download complete stock 4.3 firmware from sammobile.com for correct variant i.e GT-I9300.
Download it and extract it and you will get .tar files
download latest Odin ( google it ) and open it.
put your phone in download mode by pressing volume down + home key + power key for few deconds until download mode screen appear.
press volume up key to goto download mode. connect your phone to your computer and wait till it install all the necessary driver. if you drivers are not installed properly then you have to manually installe the driver for your phone. download galaxy toolkit for s3 from xda and install it. search for the folder name galaxy toolkit in your computer. basically it will be in c:/ drive. open that folder and you will find driver folder under it. Inside the driver folder there will .exe file of driver. but before installing disconnect your phone computer and then install the driver. after the installation of your driver plug in again and wait till it install all the drivers.
Inside odin you must have to see that there is COM ID in 1st box and below it is written attached. if you dont see that then your driver are not installed correctly. uninstall and install it again.
after the driver install click on AP and select the AP .tar file that we extracted after downloading. select the appropriate file associated with it.
click on start and wait few minutes till the process gets complete.
If all things goes right you may get your phone back again.
Click to expand...
Click to collapse
Thank you for the response.
Drivers work and it's been able to connect to ODIN but it fails regardless of the stock firmware I flash via PDA.
I get this :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
For Bootloader
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----
It would help to mention that I have a second i9300 that works and hasn't been touched or anything. Can I do something with that?
edit* It says unsupported dev type on my screen when it fails..
simonheros said:
Thank you for the response.
Drivers work and it's been able to connect to ODIN but it fails regardless of the stock firmware I flash via PDA.
I get this :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
For Bootloader
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----
It would help to mention that I have a second i9300 that works and hasn't been touched or anything. Can I do something with that?
edit* It says unsupported dev type on my screen when it fails..
Click to expand...
Click to collapse
Looks like your Nand maybe corrupt try flashing the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735 <<
tallman43 said:
Looks like your Nand maybe corrupt try flashing the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735 <<
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
SECURE CHECK FAIL : PIT
Unsupport: dev_type
---
None of the PIT's work now... And pretty much none of the files passed... D:
simonheros said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
SECURE CHECK FAIL : PIT
Unsupport: dev_type
---
None of the PIT's work now... And pretty much none of the files passed... D:
Click to expand...
Click to collapse
Any progress??
suyash1629 said:
Any progress??
Click to expand...
Click to collapse
None what so-ever. I hit a dead end and had to get a replacement.
I'm just not going to mess with the new one anymore...
Hello there XDA expersts, i was running CyanogenMod 13.0 (Snapshot).And all of the sudden my phone starts to keep on restarting .I tried to Factory Reset it through the Latest TWRP Recovery but it got stuck at Factory Reset Process.Now i can only goto the DOWNLOAD MODE.If i try to goto the RECOVERY MODE,the phones just bootup and show Black and White screen.
So decided to Flash a Stock ROM with ODIN but still no luck.That's the ERROR i am getting while Flashing the Stock ROM with Odin.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Note:
1)Device GT-i9300
2)I was running CM 13.0 Snapshot
3) Now I can ONLY goto the Download Mode.
Any help would be appreciated
You have the USB drivers installed? Tried using different USB cables and USB ports? Try Odin 3.07?
audit13 said:
You have the USB drivers installed? Tried using different USB cables and USB ports? Try Odin 3.07?
Click to expand...
Click to collapse
USB Drivers - Yes Installed
Odin 3.07 - Yes that's the version i am using
And finally tried a different Data Cable and Got a New Error :|
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
The data cable is not good. Use an original Samsung USB cable.
audit13 said:
The data cable is not good. Use an original Samsung USB cable.
Click to expand...
Click to collapse
Well sir, tried with a different Data cable,still getting the same error
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you use a Samsung cable? I used to get the same pit error when flashing other Samsung phones. The cables seemed fine for charging and copying files, just not flashing with Odin.
audit13 said:
Did you use a Samsung cable? I used to get the same pit error when flashing other Samsung phones. The cables seemed fine for charging and copying files, just not flashing with Odin.
Click to expand...
Click to collapse
Yes i have used 2 Original Samsung Data cables but still same error
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Do a adb shell test. CMD -> adb -> adb devices and check if it reads the phone.
GU37 said:
Do a adb shell test. CMD -> adb -> adb devices and check if it reads the phone.
Click to expand...
Click to collapse
Sir i have no idea how to do that.Could you be more specific please
1. Get the samsung drivers: SAM_USB_Driver_for_Mobile_Phones_v1.5.55.0. (I'm using this one)
Uninstall current one, restart your pc, and install this one if necessary.
2. Go to adbshell.com/downloads and get the ADB kits or google ADB kits.
3. Locate your folder with the adb kit and do a right in the blank space and look for "command prompt here"
4. Use: 'adb devices' command when you get it all set up.
GU37 said:
1. Get the samsung drivers: SAM_USB_Driver_for_Mobile_Phones_v1.5.55.0. (I'm using this one)
Uninstall current one, restart your pc, and install this one if necessary.
2. Go to adbshell.com/downloads and get the ADB kits or google ADB kits.
3. Locate your folder with the adb kit and do a right in the blank space and look for "command prompt here"
4. Use: 'adb devices' command when you get it all set up.
Click to expand...
Click to collapse
tried that and this happend
Try flashing the ROM with a pit file. Tried all USB 2.0 ports on the computer?
audit13 said:
Try flashing the ROM with a pit file. Tried all USB 2.0 ports on the computer?
Click to expand...
Click to collapse
Yes sir i have Tried all USB 2.0 ports on two different Laptops.
And could you be more specific,i don't know how to Flash ROM with Pit file,
You would need to located a pit file specifically for the i9300. It is a file that is used to partition the internal memory to bring it back to factory settings.
This may help even though the thread is very old: https://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
audit13 said:
You would need to located a pit file specifically for the i9300. It is a file that is used to partition the internal memory to bring it back to factory settings.
This may help even though the thread is very old: https://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Click to expand...
Click to collapse
Tried to Flash the PIT file with ODIN and this happened
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:|
GU37 said:
Do a adb shell test. CMD -> adb -> adb devices and check if it reads the phone.
Click to expand...
Click to collapse
I have exactly the same problem with the same mobile phone, I do not know how to do this can help me ??
Maybe the emmc chip is damaged which means a replacement motherboard is necessary.
sbessa10 said:
eu tenho exactamente o mesmo problema com o mesmo telemovel, não sei fazer isto consegue me ajudar??
Click to expand...
Click to collapse
Please post your questions in English per XDA rules. Use Google translate if you have to or any other translator.
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
Regards,
Razvan
Forum Moderator
I call sudden death syndrome. But before you call time of death you should try this driver: https://drive.google.com/file/d/0B4vTiHTBB629TGNDbzY2bVNDbDg/view?usp=drivesdk
That is the driver that ALWAYS saved my phone so maybe it can help you.
My other stuff for the btu variant of this phone is here: https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
Beamed in by telepathy.
shivadow said:
I call sudden death syndrome. But before you call time of death you should try this driver: https://drive.google.com/file/d/0B4vTiHTBB629TGNDbzY2bVNDbDg/view?usp=drivesdk
That is the driver that ALWAYS saved my phone so maybe it can help you.
My other stuff for the btu variant of this phone is here: https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
Beamed in by telepathy.
Click to expand...
Click to collapse
Already tried those drivers,still no luck
Hello
First sorry for my bad english i am from Germany!
I have a Problem with my s3 I9300 . It dont start anymore
THe Phone make Problem with original Rom so i decide to make lineage-os . After i done this it works well...
A new update was availeble so i do it. After this the phone works any more . I try some Flash with Odin an know i have bigger Problems.
normal start is:
Firmware upgrade encountered an issues.Please select recovery mode in Kies and try again.
Download Modus:
Odin Mode
Product Name: GT-I9300
Custom Binary Download:10
Current Binary: Samsung Official
System Status: Custom
If i try Flash with Odin :
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
or
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me
Try using different USB cables and USB 2.0 ports.
I try diffrent cable but it is the same
Try to flash official Rom (4 Files) by odin .
has78 said:
Try to flash official Rom (4 Files) by odin .
Click to expand...
Click to collapse
Single package is just as good. I'd call this a dead phone.
Beamed in by telepathy.
argon08 said:
I try diffrent cable but it is the same
Click to expand...
Click to collapse
a different usb port (not just a different cable) is recommended, also try an Older Odin Version like 3.09 or 3.07
MigoMujahid said:
a different usb port (not just a different cable) is recommended, also try an Older Odin Version like 3.09 or 3.07
Click to expand...
Click to collapse
I do but it doesnt work ... i Change the Motherboard and know it works
thanks a lot