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
Related
Hi guru's,
Seeking some guidance re: an S2 which won't play with Odin3 nicely... Been thru all the associated threads I can find, still no luck...
History:
- went from v2.3.3 to v4.0.3 some time ago on my Virgin S2
- phone has been crappy ever since. Apps lock up, reboot it several times weekly to fix it
- got d*ck of that, so tried using Odin3 to roll it back
- couldn't get my hands on a Virgin v2.3.3 ROM, so chose the 'generic' brand (see below) v2.3.3
What have I tried:
- followed the thread of How To: hxxp://androidfirmwares.net/Guide/Details/2
- 2 x puters. 1st is XP, no KIES installed. 2nd is Win7 with KIES installed (stopped it's processes first)
- have tried Odin3 v1.85 & v3.04 on both puters with same results
- tried a couple of different good quality HTC USB cables in different USB ports on both puters
- have turned anti-virus & windows firewall OFF during all this
Keep getting this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_NEE_I9100XWKF3_I9100XXKE7_I9100OXXKF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone is stuck on: ODIN MODE
Downloading.... Do not turn off target!!!!!!!
Phone details before I started:
Android Version: 4.0.3
Base: I9100XXLPS
Kernel: [email protected]
Build: IML74K.XWLP8
I've pulled out the USB several times to move USB ports etc, but I've not been game to try re-start the phone yet!! or even attempt to.... Is it safe to try??
WHAT TO DO GURU'S????????? Not sure how long the phone will last - not sure if it's charging currently...
Sing out if you need more info - but I've tried to lay it all out here...
JTS
jts999 said:
Hi guru's,
Seeking some guidance re: an S2 which won't play with Odin3 nicely... Been thru all the associated threads I can find, still no luck...
History:
- went from v2.3.3 to v4.0.3 some time ago on my Virgin S2
- phone has been crappy ever since. Apps lock up, reboot it several times weekly to fix it
- got d*ck of that, so tried using Odin3 to roll it back
- couldn't get my hands on a Virgin v2.3.3 ROM, so chose the 'generic' brand (see below) v2.3.3
What have I tried:
- followed the thread of How To: hxxp://androidfirmwares.net/Guide/Details/2
- 2 x puters. 1st is XP, no KIES installed. 2nd is Win7 with KIES installed (stopped it's processes first)
- have tried Odin3 v1.85 & v3.04 on both puters with same results
- tried a couple of different good quality HTC USB cables in different USB ports on both puters
- have turned anti-virus & windows firewall OFF during all this
Keep getting this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_NEE_I9100XWKF3_I9100XXKE7_I9100OXXKF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone is stuck on: ODIN MODE
Downloading.... Do not turn off target!!!!!!!
Phone details before I started:
Android Version: 4.0.3
Base: I9100XXLPS
Kernel: [email protected]
Build: IML74K.XWLP8
I've pulled out the USB several times to move USB ports etc, but I've not been game to try re-start the phone yet!! or even attempt to.... Is it safe to try??
WHAT TO DO GURU'S????????? Not sure how long the phone will last - not sure if it's charging currently...
Sing out if you need more info - but I've tried to lay it all out here...
JTS
Click to expand...
Click to collapse
Don't restart the phone, just hold the power button until the phones off. You might want to try a different firmware. Have you tried 4.0.4? It's miles better from 2.3.3 and 4.0.3
PS, don't mess with the phone until you've got a firmware downloaded and ready to flash, then boot it into download mode.
Sent from my GT-I9100 using xda premium
i360* said:
Don't restart the phone, just hold the power button until the phones off. You might want to try a different firmware. Have you tried 4.0.4? It's miles better from 2.3.3 and 4.0.3
PS, don't mess with the phone until you've got a firmware downloaded and ready to flash, then boot it into download mode.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for the power-off info. - wasn't sure what I was going to do... Upon startup, this time it was happy to behave properly according to the script... except that now we have some type of boot-loop going on... Pretty sure I recall seeing this along my research travels so will look that up now... For now, I've just used the ROM I had... if it all goes well from here and I can get rid of the looping, I'll try v4.0.4 soon
Thanks i360u*
edit: where to find v4.0.4? i can't see it where I got my orig. one from: hxxp://androidfirmwares.net/PhoneFirmware
jts999 said:
Thanks for the power-off info. - wasn't sure what I was going to do... Upon startup, this time it was happy to behave properly according to the script... except that now we have some type of boot-loop going on... Pretty sure I recall seeing this along my research travels so will look that up now... For now, I've just used the ROM I had... if it all goes well from here and I can get rid of the looping, I'll try v4.0.4 soon
Thanks i360*
edit: where to find v4.0.4? i can't see it where I got my orig. one from: hxxp://androidfirmwares.net/PhoneFirmware
Click to expand...
Click to collapse
Heres some advice, don't trust a firmware from a site that isn't Samfirmware or XDA.
Try XWLPU.
Thread
This is totally stock but if you're looking for a better, rock stable version, try XWLPU NeatRom Lite. You need CWM for this.
i360* said:
Heres some advice, don't trust a firmware from a site that isn't Samfirmware or XDA.
Try XWLPU.
Thread
This is totally stock but if you're looking for a better, rock stable version, try XWLPU NeatRom Lite. You need CWM for this.
Click to expand...
Click to collapse
Cheers for the tip :good:
Getting LPU now will see how it goes... gheesh - no Swype in v233!!! aaaaaaaaaaaarrrrrrrrrrgggggggggggggggghhhhhhhhhhhhh!!! dunno how i eva lived without it :laugh:
cheers again mate
jts999 said:
Cheers for the tip :good:
Getting LPU now will see how it goes... gheesh - no Swype in v233!!! aaaaaaaaaaaarrrrrrrrrrgggggggggggggggghhhhhhhhhhhhh!!! dunno how i eva lived without it :laugh:
cheers again mate
Click to expand...
Click to collapse
Try Swiftkey, I was an ex-Swyper myself. Swiftkey is way better
i360* said:
Try Swiftkey, I was an ex-Swyper myself. Swiftkey is way better
Click to expand...
Click to collapse
+1 to Swiftkey! :good::laugh:
《SOLVED》Okay, so I was stuck in some sort of boot loop... after reading several posts on this site as well as many others I felt confident in my ability to repair it using Odin. Big Mistake!!! Now my phone will not go into recovery mode, or download mode it just shows me "phone--!--PC" As far as I can tell it is now hard bricked, my computer will not recognize it and I cannot not get away from the "phone--!--PC" screen to save my life. If anybody can help me I would be eternally grateful. Thanks!!
Which firmware are u on now?
Which files did u flash?
Try downloading a stock firmware for ur device from sammobile.com and flash it via odin.
"To err is human, to forgive is divine"
Sent from my SGS II
Which firmware are u on now?
Which files did u flash?
Try downloading a stock firmware for ur device from sammobile.com and flash it via odin.
I tried to follow the directions given here http://forum.xda-developers.com/showthread.php?t=1619571
Now I cant even get Odin to recognize my phone. I've tried everything and still can't get it into download mode anymore.
Used a USB jig?
"To err is human, to forgive is divine"
Sent from my SGS II
He doesn't need a jig. Phone---!---PC (or whatever order it's in) is download mode. Forced download mode. It's just a matter of getting the phone & PC to recognise each other like any other example of Odin not working.
MistahBungle said:
He doesn't need a jig. Phone---!---PC (or whatever order it's in) is download mode. Forced download mode. It's just a matter of getting the phone & PC to recognise each other like any other example of Odin not working.
Click to expand...
Click to collapse
Thanks for clearing that up! I remember gastonw saying it was a kind of download mode, that's why I suggested flashing first.
"To err is human, to forgive is divine"
Sent from my SGS II
I was finally able to get ODIN to recognize my phone, but still I can't get it to work. This is the message I'm getting and a big FAIL lol.
Any other advice???
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
GTI9100G stuck in in boot and not charging!!!!!!!
AmadaWgnd said:
I was finally able to get ODIN to recognize my phone, but still I can't get it to work. This is the message I'm getting and a big FAIL lol.
Any other advice???
Click to expand...
Click to collapse
hello friends my phone is stuck in boot and not charging after updating through philz touch and ODIN is not recognising it!
what to do with it????
For boot loop, try wiping cache and dalvik cache I'm recovery.
For Odin fail, did your rom come with a pit file ? Did you check repartition ?
It is recommended not to repartition, but if the ROM contains a pit file, you may have to use it...
Anyway, you can try to reflash, change your USB port, use another USB cable, etc...
Envoyé depuis mon Nexus 10 avec Tapatalk
You stuck between those .img files? No choice. Go find .pit file with your stock firmware. You said you only get the pc and alert sign on the phone, right? Once you get the correct .pit, it will flash successfully. Wrong file, it will always stuck at .img, even if you wait for 2hours.
Sony Xperia Tipo ST21i
Turns out all I had to do was check repartition necause yes I did havr a PIT file with my rom... works great now. Thank u guys so much for all ur help!!
AmadaWgnd said:
Turns out all I had to do was check repartition necause yes I did havr a PIT file with my rom... works great now. Thank u guys so much for all ur help!!
Click to expand...
Click to collapse
Please add [SOLVED] to the title of ur post so that others may see ur solution.
"To err is human, to forgive is divine"
Sent from my SGS II
You're welcome!
Glad I was able to help and getting the right to post in the development thread doing so!
Have a nice day!
Envoyé depuis mon GT-I9100 avec Tapatalk
S2 GT I9100G Bricked
I (soft) bricked my GT-I9100G (following an attempt to install Slim ROM with CWM ROM Manager). I thought I was following instructions to the letter, but obviously hosed it up (somehow).
Background: This phone was rooted, with stock ICS ROM installed.
1. Phone only goes to “Samsung” screen,
2. Can only depower by removing the battery,
3. Cannot enter “Recovery” or “Download” modes,
4. Could not establish connection between Kies and phone - completely removed Kies,
5. Is recognized by Odin, and computer (with errors in Device Manager),
6. Drivers start to load, each time phone is connected but end up with “Driver Software was not successfully installed – Please consult with your device manufacturer…”,
7. I get Code 10 error when updating drivers in Windows 7,
8. I’ve tried flashing stock ROM (I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5)using Odin PDA, but it goes to “Connection Setup..” and stops, leaving same “Samsung” screen image,
9. Then I flashed a stock PIT (omap4_all_20110627_emmc.pit), with the ROM – still only gets to “Connection Setup..” in Odin,
10. Followed all options in XDA thread: [SOLUTION] Samsung Mobile MTP Device -- CODE 10 error at Devicemanager – no change
Here are the messages that are on Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_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..
<OSM> All threads completed. (succeed 0 / failed 1)
Have Removed/Updated Drivers (per #10, above). Used every possible combination of Ports and cables. Removed battery for one hour (replacing with fully charged battery).
I have been Googling for three days now without any solutions that fix this. Any assistance/advice will be most gratefully appreciated!!!!!
S/F Phillip
If you insist you've tried everything, then it's a service centre or local mobile repair shop job.
Or...You can find Hopper8's 'Odin troubleshooting' thread stickied in General & keep trying the stuff in that thread over & over & over. There's nothing else which isn't in the thread that can be suggested in these situations. They're either fixed with perseverance if they're recoverable, or they're NAND corrupted & require a motherboard replacement to fix.
Edit - And before you insist you've tried 'everything', you haven't tried multiple PC's yet, nor some other stuff in Hopper's thread.
<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.
How it started:
A pop message appears asking to format the phone, I accidentally hit okay, after 10 seconds I realized it, I immediately stopped the process by hitting the back button which caused my phone to go blank screen and freeze. so I pressed and hold power button, and the phone shuts off turns back on then it get stuck on the Samsung Logo/screen and won't go through no matter how long I wait.
So with that said I may have corrupted my Operating System so I went online to try to look for solutions to recover my Note.
i have downloaded Odin v1.85 and v3.07
i have downloaded the latest OS Jellybean from samsung:
(KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5)
i have downloaded the latest USB software and currently using the original cable that came in the box.
I open Odin v1.85 on my Windows 7 Ultimate Desktop
i put my phone in Odin download mode (power + volume down)
I pressed volume up
I plugged in my phone to the USB
I clicked start
and then I get stuck
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> amss.bin
<ID:0/005> NAND Write Start!!
Please see my screenshot as attachment.
Please help!
Thank you!
http://forum.xda-developers.com/showthread.php?t=2240096
okay thank you i am reading it now.
i will report back with the outcome.
thanks once again.
okay before i go further if you look at my attachment
first box says "MODEM"
is this normal?
i saw a vid on youtube shows "SYSTEM"
I have read your guide and installed the latest samsung USB driver
I rebooted my computer opened ODIN as admin
followed instructions and i am back to my original post
i think it has something to do with the fact mine shows "MODEM"
this is what i'm talking about.
the difference is on this pic it shows "SYSTEM"
while mine says "MODEM"
does that mean my phone can no longer be recovered?
Am I missing something here? seems like I have a more technical issue/problem other than common Odin problems.
any help would be appreciated.
What it says is what yrs currently flashing. That's just where it's getting stuck
studacris said:
What it says is what yrs currently flashing. That's just where it's getting stuck
Click to expand...
Click to collapse
so is there any solution to this?
i tried it over again on another PC (Laptop)
i still get the same error where I get stuck:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> amss.bin
<ID:0/003> NAND Write Start!!
stuck here... no matter how long I wait i have been up all day long and found no solution online
I will send $10 paypal donation to the website or to somebody that can help me revive my phone back to normal.
i am that desperate now. i have been up for almost 12 hours trying everything i could.
i am currently looking for a .pit file for Samsung Galaxy Note AT&T SGH-i717 cannot find it anywhere!
Are you using the same .tar everytime?
Try another package and see what happens.
Or... just flash a twrp.tar and just flash a custom Rom on that thing.
studacris said:
Are you using the same .tar everytime?
Try another package and see what happens.
Or... just flash a twrp.tar and just flash a custom Rom on that thing.
Click to expand...
Click to collapse
Yes: KIES_HOME_I717UCMD3_I717ATTMD3_1117019_REV02_user_low_ship.tar.md5
i'll download an older version (ice cream sandwich)
i have not tried twrp.tar nor custom ROM
can you point me to a link to DL it?
If another stock package doesn't work here's Twrp
http://forum.xda-developers.com/showthread.php?t=1647575
Then you put a custom Rom of your choice I your sdcard and flash that within recovery.
studacris said:
If another stock package doesn't work here's Twrp
http://forum.xda-developers.com/showthread.php?t=1647575
Then you put a custom Rom of your choice I your sdcard and flash that within recovery.
Click to expand...
Click to collapse
tried it i'm still stuck.
please see screenshot
are you running Odin as admin?
as long as you can still get into download mode and have odin recognize you, you are in good shape. Dont do something to put yourself in qualcomm download mode. Else, you will be sending your phone to be jtagged. . .
In my guide it mentioned trying different cables and cleaning the usb port.
Have you taken those steps?
sinasiadat said:
are you running Odin as admin?
as long as you can still get into download mode and have odin recognize you, you are in good shape. Dont do something to put yourself in qualcomm download mode. Else, you will be sending your phone to be jtagged. . .
Click to expand...
Click to collapse
yes
studacris said:
In my guide it mentioned trying different cables and cleaning the usb port.
Have you taken those steps?
Click to expand...
Click to collapse
yes tried 3 diff cables and tried 4 MB ports and 3 laptop ports
I meant cleaning the port on the device itself
jeffcarp003 said:
yes tried 3 diff cables and tried 4 MB ports and 3 laptop ports
Click to expand...
Click to collapse
what is device manager showing you when your phone is plugged in? what does it enumerate as . .
do you have a copy of QPST? (you work for qualcomm right?)
I Hard Bricked Galaxy note i7i7
Hello
I was flashing a kernel in order for this jellybam rom to work.So when i put my phone into custom recovery mode and installed the custom kernel through custom recovery a quick message appeared and my phone just shut off. My phone hasn't turned on since and i have no clue to unbrick my phone. I talked to a guy at att and he said that he unbricked his hard bricked phone without a jig or a jtag is that possible?
jeffcarp003 said:
I have read your guide and installed the latest samsung USB driver
I rebooted my computer opened ODIN as admin
followed instructions and i am back to my original post
i think it has something to do with the fact mine shows "MODEM"
this is what i'm talking about.
the difference is on this pic it shows "SYSTEM"
while mine says "MODEM"
does that mean my phone can no longer be recovered?
Am I missing something here? seems like I have a more technical issue/problem other than common Odin problems.
any help would be appreciated.
Click to expand...
Click to collapse
Sounds like corrupted download. Look for another source and let me know how it goes.
Sent from my XT894 using Tapatalk
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.