<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I've disabled kies from the task manager. Even changed the cable and computer. Tried reinstalling kies/rebooting etc. Nothing seems to work.
Help please
Also I have the international version of the s2 if that makes any difference.
It's probably something really obvious/simple that's not happening here. Com port issue says it's an issue with the USB ports on the PC you're using. I suggest you find one of the many 'Odin won't work' threads we have on here every week; there's a set of troubleshooting steps you need to try, I suggest you find that list of steps & keep trying them.
MistahBungle said:
It's probably something really obvious/simple that's not happening here. Com port issue says it's an issue with the USB ports on the PC you're using. I suggest you find one of the many 'Odin won't work' threads we have on here every week; there's a set of troubleshooting steps you need to try, I suggest you find that list of steps & keep trying them.
Click to expand...
Click to collapse
I actually found another cable and tried it earlier. Surprisingly, Odin worked...sort of, it moved further ahead of the steps. Though I couldn't recall what it said, and after that one time where it got further ahead in Odin. The process has actually been stuck at Setup Connection .
WOOHOO
After a 6 hour battle. I finally got this stubborn computer and phone to work together. It turns out that in order for it to work was to do the following:
1. Rebooting the phone back into download mode
2. Plug it into a fresh port/fresh computer
3. Open Odin
4. Plug in your phone.
5. Watch the magic happen before your eyes (My actual installation only took 2:49)
The stock rom has been completely installed. Now I'm just waiting for the samsung logo to disappear and finally turn on. I hope this doesn't get stuck as well....
After going into recovery mode and wiping out all of my data. I was able to turn on my phone completely after only 30 seconds of loading. Thanks for reading and I hope these tips will help someone in the future who was in the same position as I was.
Related
Hi forum,
I'm having big problems with my galaxy tab 10.1 p7510. I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot. Went into android recovery and wiped cache, some errors appeared and I wasn't able to turn on the tab for about a day. I held down the power button for a really long time and it went into a boot loop. Was able to get into recovery again, wiped cache again; since then I couldn't get into recovery any longer. But, I have been able to get into download mode. I downloaded the latest ROM (and the one before it) from sammobile.com; tried flashing both using odin 1.83, 1.85, and 1.87. Tried two different computers and various usb ports for each computer. installed drivers and kies, made sure kies was disabled when attempting flash. Result is always the same:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7510XABLPL_P7510UELPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I really don't know what else to do.
Should note, when i power off and power on, some red text appears quick (can't see it) and it automatically goes into download mode. At the top it says, "reason no kernel"
Please help!
Jim
focusbob said:
I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot.
Click to expand...
Click to collapse
What exactly were you transferring? Were you flashing a new ROM, restoring a backup or adding an update?
No, I was just transferring videos from pc to tab via usb. It froze, but I think it was when I tried to clear cache in android recovery that things went down hill. There are some known problems with factory resets with galaxy tabs due to a faulty chip. Maybe it was that? who knows. I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
focusbob said:
I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
Click to expand...
Click to collapse
In that case, congratulations and better luck next time.
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Which version of ODIN did you use? What kind of file(s) were you trying to flash?
Sent from my GT-I9300 using Tapatalk
I'm not sure but think it was Mobile Odin 3.65 and I was trying to flash CWM touch from xda.
Additionally, I think my battery charge may now be low after many attempts to recover it but will that matter bearing in mind I'm using Odin on my PC and the phone is connected to the PC by USB cable?
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
JJEgan said:
One flash Philz recovery and format system data cache and sd card .
Two check your USB drivers for Odin and make sure Kies is not running .
What do you mean Odin sticks at setup connection ??
If its before flashing its drivers or try another version of Odin .
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
matrixmainframe said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.00.8-i9300.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..
and it stops there
Click to expand...
Click to collapse
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
JJEgan said:
I am reading that as fail before install .
wo check your USB drivers for Odin and make sure Kies is not running .
try another version of Odin .
Click to expand...
Click to collapse
Kies is not installed on my computer and I have tried Odin versions 1.83, 1.85, 3.04, 3.06, 3.07 and 3.09.
I have also tried 'Samsung_USB_Drivers_1.5.27.0.exe' and 'SAMSUNG_USB_Driver_for_Mobile_Phones.exe' and remembering to uninstall then reboot and then install.
On one occasion it got as far as (can't remember the exact words) "Get PIT Mapping" but then just stopped there.
I cannot believe I have done anything other than corrupt the CWM recovery because all I did was try to flash CWM Touch and as soon as I pressed OK the screen went black with the word "Samsung Galaxy SIII GT-I9300". Those words just stay there because since then I can't switch the phone off. I thought that if I just reflashed CWM via Odin on my computer I would be able to get back into recovery mode and just restore my backup.
Appears I am mistaken and have ruined a very new and vey expensive phone.
The only other thing I seem to recall is that before I tried the Mobile Odin flash the battery was below 50% charge but I'm not sure if that's relevant?
This is usually a wrong file flash symptom .
JJEgan said:
This is usually a wrong file flash symptom .
Click to expand...
Click to collapse
Do you mean I'm trying to flash something I shouldn't?
Initially I tried to flash CWM Recovery but then decided just to try and get it back the way it was by trying to flash Android 4.1.2 again.
The file I have been using is "KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5" which I believe is from Sammobile and which is, I believe again, the ROM that the Galaxy S3 comes pre-installed with. Do you think it worthwhile me trying some other ROM?
I have been doing a lot more web research and some say that the battery charge should be more than 80%. Does this matter?
Won't the battery have been charging all the while the phone was plugged into into the Computer via the USB lead?
If I buy a separate charger and charge my battery to 100% do you think the Odin reflash will work then?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL5_I9300VFGELL1_I9300BUELK1_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
so close
matrixmainframe said:
I have a Galaxy S3 GT-I9300 running the Samsung Stock 4.1.2 ROM.
It was rooted and I tried to flash CWM Recovery using Mobile Odinbut as soon as I did that the only thing that now appears when I try to boot the phone is the initial black screen with the "Samsung Galaxy SIII GT-I9300" words.
I cannot get into Recovery mode.
I can get in to download mode but no matter what I try with Odin it sticks at setupconnection. I have used Odin to try and re flash CWM to try and get back into Recovery mode but get stuck at setupconnection.
I have used Odin to try and re flash the stock ROM but again get stuck at setupconnection.
I get this whether I try using Odin on my laptop or my desktop PC
I did wonder if this would happen if my battery charge was low so I plugged the phone in the charger to see what the battery level was when it appeared but the battery will not appear and again I see only the words "Samsung Galaxy SIII GT-I9300" on the black background.
Can anyone suggest a way out of this?
Thanks
Click to expand...
Click to collapse
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
llcoolveer said:
Same here,and i have to load my battery 100% before it gets into 'download mode'again...
Lets see if we can get it up and running again...your not alone...
Click to expand...
Click to collapse
Nice to know I'm not alone but sorry you're having the same problem. Have sat down to do some more web searching and will let you know if I find a solution
Service centre new motherboard .
JJEgan said:
Service centre new motherboard .
Click to expand...
Click to collapse
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
llcoolveer said:
Fixxed it by going in the OG recovery....did a hard factory reset and vavooom....fixxed it....:good:
btw,was it a problem that you rooted your phone....? Due to extra costs,or did they bring it under warranty...?
Thanx in advandce for the reply.....
Sincerely ,LLCOOLVEER
Click to expand...
Click to collapse
Please can you tell me what is "OG Recovery"?
Thanks
matrixmainframe said:
Please can you tell me what is "OG Recovery"?
Thanks
Click to expand...
Click to collapse
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
llcoolveer said:
the Original Recovery....or Stock revovery.....http://www.youtube.com/watch?feature=player_detailpage&v=UvD6ZCENlJA
Click to expand...
Click to collapse
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
matrixmainframe said:
Thanks for that but as I stated in my original post I cannot get into Recovery Mode
Click to expand...
Click to collapse
I couldn't also....only when my battery was full charged....:good:
Succes....
The end
Okay, I started this thread so will end it now as follows:
1 Thank you to all those who offered help/advice/suggestions.
1a Some people do not read posts properly because even though I had specifically stated that I could not get into recovery mode some people proceeded to tell me to go into recovery mode and restore my rom.
2 Whilst I have recovered the full use of my phone I can no longer root it but that's ok because at least I have a phone that is comparable to the vast majority who choose not to root.
3 I will explain how I rescued it but obviously I don't really understand what the result is other than a usable phone so please don't copy.
4 Whilst I have no doubt one could damage a motherboard, that could only be done with very specialist software that most people would not have so the advice of some that I needed a new motherboard was ill informed. If you don't know the answer don't offer an unhelpful answer. Recommending a new motherboard is like a motorist taking his car into a garage with a blown fuse and the mechanic saying the only cure is a new car.
5 After a lot of research I found one lone website that explained that from July 2013 Samsung introduced a change to their ROMs which introduced an efs 2 file. Additionally it appears that once you have flashed/upgraded to an efs2 ROM you cannot then go back to an efs ROM.
6 This is above my understanding but I do know I did go from efs to efs2 and when I then encountered a problem I thought it a good idea to go back to my original (efs) ROM which I now believe caused my problem.
7 I did not know if I had found the answer but as I believed my phone was a paperweight at that point anyway I had nothing to lose and downloaded the GT-I9300.pit file and flashed with repartition selected. I then flashed Android 4.3 knowing it would be an efs2 ROM and my phone is now working again.
8 However, although my phone is now working again, I find that I cannot install a custom recovery nor can I root the phone but that is a small price to pay to have a brand new S3 working again.
9 Whilst it may not be wise to mess about with the pit file, it seems nothing can be lost to give it a go because even if it doesn't work you can still go for the new motherboard option happy in the knowledge you have tried everything.
10 I may start a new thread for advice on that matter but for the time being I'm just relieved to have my phone back and I stress again that it did work for my specific problem and whilst it might work for you please only do it knowing it may not work for your problem.
hi all.
first off i would like to say that i have searched forums here and there for w few days and i have tried so many things but all with the same result
i have a samsung galaxy s2 that runs 2.3.6 and i wanted to upgrade to a higer os.
but i keep getting the following error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS3_I9100XXMS4_I9100FOPLS6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
i have tried all from removing battery for 20 minutes , different tar files different versions of odin , shorter usb cables different pc's different usb ports
all give me the same problem.
i hope you can show me in the right direction .
thx
Hopper8's 'Odin troubleshooting' thread stickied in the General section has all the info you need to get a successful flash; try as much of the stuff in the thread as many times as you need to & you should be fine.
MistahBungle said:
Hopper8's 'Odin troubleshooting' thread stickied in the General section has all the info you need to get a successful flash; try as much of the stuff in the thread as many times as you need to & you should be fine.
Click to expand...
Click to collapse
i have tried it all
on 3 different pc's on even a clean install of windows. i have tried 4 samsung cables which i have used with succes before.
i just tried to load 2.3.6 again ( current version on my sgs2) but same problem
i get complete (write) operation failed right after boot.bin
and when i just turn on the telephone now i get a firmware upgrade encountered an issue error
Service centre then. Your other option is perseverance. There is no easy fix.
MistahBungle said:
Service centre then. Your other option is perseverance. There is no easy fix.
Click to expand...
Click to collapse
thx for the swift replies ,
but that means the end for me
i live in Suriname and we do not have a service centre here .
thx anyway
Then I strongly suggest you keep trying the stuff in that thread, that's the only option you have. And the experience on here is phones in this situation which are indeed recoverable & do not have a corrupted NAND are fixed with perseverance.
aquah2o said:
thx for the swift replies ,
but that means the end for me
i live in Suriname and we do not have a service centre here .
thx anyway
Click to expand...
Click to collapse
Change ur usb cable n retry... as I said previously ..I always have a flashing error wid my stock usb cord but works properly wid nokia usb cord
doctor_droid said:
Change ur usb cable n retry... as I said previously ..I always have a flashing error wid my stock usb cord but works properly wid nokia usb cord
Click to expand...
Click to collapse
I will try a nokia cable or blackerry cable later.
For now i used odin 3.09 and it doesnt fail yet it just stops at sbl.bin and stays ther
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Use this if it fails it needs service repair >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Happened the same too me and i have CM11 too... If you get a fix contact me please
emnt said:
Happened the same too me and i have CM11 too... If you get a fix contact me please
Click to expand...
Click to collapse
Try the above rescue firmware as suggested above make sure you know what you are doing before flashing.. Exactly same advice if that doesn't work service required partition corrupt..Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
blackbeardtwenty said:
The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen,
Click to expand...
Click to collapse
Hardware issue, either damaged or corrupt emmc chip.
tallman43 said:
.Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
Click to expand...
Click to collapse
Yeah, that was a desperate attempt at trying another root file which was recommended in another post. I initially used:
I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5
and this worked fine last month, but now I'm back to square one again. Any ideas on other PIT files or root files I can download which might do the trick?
Thanks for your comments so far, you're all a bunch of wizards...
Hello peeps
Can you help.? I imported My phone (an S6 Edge 128gb ) from the far East so its full of Chinese. I wanted to replace the firmware with UK unlocked or UK EE (I'm on EE).
I downloaded ODIN no problem, followed all the instructions buy it starts then fails. Any suggestions please?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCY_G925FEVR1AOC1_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1005)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Graham
graham.phillips said:
Hello peeps
Can you help.? I imported My phone (an S6 Edge 128gb ) from the far East so its full of Chinese. I wanted to replace the firmware with UK unlocked or UK EE (I'm on EE).
I downloaded ODIN no problem, followed all the instructions buy it starts then fails. Any suggestions please?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCY_G925FEVR1AOC1_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1005)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Graham
Click to expand...
Click to collapse
OK so leave phone unconnected then load file in odin. Let it do its checks. Connect you phone and wait for roughly 5secs and then it should flash.
Good Luck
Thanks.. I tried that but it didn't work.. any other suggestions? Thanks.. really appreciate your expertise
Graham
Duncan1982 said:
OK so leave phone unconnected then load file in odin. Let it do its checks. Connect you phone and wait for roughly 5secs and then it should flash.
Good Luck
Click to expand...
Click to collapse
grahamxphillips said:
Thanks.. I tried that but it didn't work.. any other suggestions? Thanks.. really appreciate your expertise
Graham
Click to expand...
Click to collapse
OK are you in odin mode by powering down and then holding-power,home, volume down and then volume up?
If so try a few times, first time with the above instructions doesn't always work (in my experience) but usually repeating on the second or third will result in success.
Good Luck
Please keep in mind that flashing a wrong firmware can end badly. Especially using a wrong Bootloader csn result in a paperweight. And Odin flashables include a bootloader.
I don't know what the result will be if the phone is just a different variant, but you should always be careful with that. What you are doing might not be free of risks, thats what I mean.
I wouldn't recommend doing what you are doing. Odin failing is usually a bad sign.
mythos234 said:
Please keep in mind that flashing a wrong firmware can end badly. Especially using a wrong Bootloader csn result in a paperweight. And Odin flashables include a bootloader.
I don't know what the result will be if the phone is just a different variant, but you should always be careful with that. What you are doing might not be free of risks, thats what I mean.
I wouldn't recommend doing what you are doing. Odin failing is usually a bad sign.
Click to expand...
Click to collapse
Hi and thanks for this. I did try a few more times but with the same result. Any suggestions? The phone in its current format really doesn't work at all well for me...
You could also try a different USB cable or a different USB port.
Have you installed the Samsung drivers for your device?
Trying to switch variants sounds pretty risky to me. perhaps it's a blessing that you've not yet been successful.
It might be cheaper/better for you to sell your current phone and get a 925F on eBay?
Sent from my SM-G925I using Tapatalk