I was updating my Samsung Galaxy SII i777 to 4.0.4 with kies, but I have some issues and it says that i should do an emergency recovery and after several tryings it worked but it erase all the info in the phone... even the unlocked code... so now it doesn't read my sim card. I was looking for the solution and a lot of programs were recomended, i instaled one for unlocking and it asked me for root it and for some busybox that didn't worked either because the phone wasn't rooted so theeeeen i try to root it by following some steps with Odin 1.85 and a link that i should extract later with the odin... it seems it was an old link? because in the steps it says "I'll take 10 seconds to be done" and it passed 6 hours and nothing.... so I unplugged the USB cable and the phone continued working normally but still couldn't read my sim card... so I searched for moooooore help and i downloaded link that was 335mb and try it again... It was working, a blue bar was advancing in the phone's screen with all the rest of the "downloading please bla bla" but it continued that way (the bar kept the same size) and it passed 5 hours... so I unpluuged... and removed the battery.. and then search more, downloaded Odin 3.7, put the battery back and a emergency sign appeared with an "Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again" so i open kies and nothing... it didn't recognized the phone... even clicking in troubleshoot connection (several times and nothing) so I tried the Odin's new version and after 20 minutes a big FAILED sign appears and all this info:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLK3_I777ATTLK3_I777UCLK3_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.
<OSM> All threads completed. (succeed 0 / failed 1)
Please Help I've tried pressing the volume and home as before and nothing, no rebooting and the "firmware upgrade encountered issue" still... even if i remove the battery and but it back....
BTW I buy the phone on ebay in January 2012, and the seller give it to me unlocked... so i don't have the unlocked code either.... he's not answering me... I tryed all this for not buying a new code..
Had the same issue dealing with kies, twice with my own devices, and at least 3 or 4 on friends'. Get into download mode, head to the stickies, use the most up to date odin for return to stock. Might take a try or two, but it'll take. Priority is making sure you have the most current material.
Sent from my Galaxy Nexus using Tapatalk 2
Cmoore0965 said:
Had the same issue dealing with kies, twice with my own devices, and at least 3 or 4 on friends'. Get into download mode, head to the stickies, use the most up to date odin for return to stock. Might take a try or two, but it'll take. Priority is making sure you have the most current material.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That is the latest stuff
Sent from my GS4 running CM11 Kandy Kane
Then that step is complete lol, I maintain, download mode, odin return to stock, may take several attempts. I haven't played with my s2 in a little while, so I didn't presume to know what was current
Sent from my Galaxy Nexus using Tapatalk 2
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:
<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.
Hello,
I've only been on this forum to read stuff and never posted anything before. But I can't figure this out myself anymore, so I'm asking some help.
Alright the story. I have a rooted s3 which is just running with the standard ROM, never installed a custom ROM. Yesterday my phone randomly shut down a few times so I had to boot it up again, that was already quite strange. Then in the evening it shut down again, but when I tried to boot it up it was stuck at the bootscreen which says "Samsung Galaxy S3 I9300". Removed battery and tried again, nothing.
So then I went searching what might fix this problem. I came across some threads which told me to go in download mode and connect with odin to try and reinstall the ROM. Well that didn't work out, i get some strange error about a Pit partition. I searched what the problem was on the internet and I tried to run a .pit file through odin. Now the error didn't appear anymore, but still I couldn't install the new ROM. It just did nothing..
Some background information where it might have gone wrong: The day before the phone broke I installed ROM manager and did some things there like try to install the new clockworkmod, strange error appeared and I left it for what it was.
I hope I provided you guys with enough information to give me some advice, if not just ask and I'll post everything you need! I read on the internet that it might be a problem with the motherboard.
P.S.: Sorry if my english sucks
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEME2_I9300PHNEME2_I9300CEELL1_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Xtreme144 said:
Hello,
I've only been on this forum to read stuff and never posted anything before. But I can't figure this out myself anymore, so I'm asking some help.
Alright the story. I have a rooted s3 which is just running with the standard ROM, never installed a custom ROM. Yesterday my phone randomly shut down a few times so I had to boot it up again, that was already quite strange. Then in the evening it shut down again, but when I tried to boot it up it was stuck at the bootscreen which says "Samsung Galaxy S3 I9300". Removed battery and tried again, nothing.
So then I went searching what might fix this problem. I came across some threads which told me to go in download mode and connect with odin to try and reinstall the ROM. Well that didn't work out, i get some strange error about a Pit partition. I searched what the problem was on the internet and I tried to run a .pit file through odin. Now the error didn't appear anymore, but still I couldn't install the new ROM. It just did nothing..
Some background information where it might have gone wrong: The day before the phone broke I installed ROM manager and did some things there like try to install the new clockworkmod, strange error appeared and I left it for what it was.
I hope I provided you guys with enough information to give me some advice, if not just ask and I'll post everything you need! I read on the internet that it might be a problem with the motherboard.
P.S.: Sorry if my english sucks
Click to expand...
Click to collapse
did you tick the re partition option in odin
Please advise what it says on screen in download mode
Sent from my GT-I9300 using Tapatalk 2
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 3.185 will install this ROM successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated. I have also tried other Odin versions including 3.07.
Thank you!
jvaldez33 said:
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 185 will install this rom successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated.
Thank you!
Click to expand...
Click to collapse
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Note II Won't boot.
dragonstalker said:
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Click to expand...
Click to collapse
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Warranty costs if phone has been rooted
jvaldez33 said:
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Click to expand...
Click to collapse
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
jvaldez33 said:
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
Click to expand...
Click to collapse
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
miketoasty said:
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Update on events
mikelikesbikes said:
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I have been in the IT business for nearly 25 years and have seen many problems resolved if you have the time and desire to put forth the efforts to investigate the problem every day with a clear head. With that being said I for some unknown ADD moment and decided I wanted to troubleshoot my sons girlfriend's Note II that was having problems. Now here I am wrestling with a problem like a drug addict looking for their "next fix". I am very stubborn and extremely capable of diagnosing hardware and software problems but this one truly has me stumped!
With this being a problem I decided to purchase another Note II off EBay to experiment with and was listed with similar problems, Red Light and wouldn't boot.. I figured for $125 the worst that could happen is I could disassemble it and part out the LCD/Digitizer and recuperate my investment. There are some problems I like researching and resolving and this is one. I personally believe the problems on both Note II's may both related to the charging board based on the information on the following post on another forum: http://forum.xda-developers.com/showthread.php?p=45678812#post45678812. I will elaborate a little more shortly.
Let's go over my three day 50 hour marathon. Here is the only download that successfully downloads but the phone will only splash the "GALAXY NOTE II" screen and turn off after a successful install. I have downloaded Odin 3.185 and 3.07 and get the same results:
sch-i605-16gb.pit
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
Unless the problem resides on my laptop I think I have eliminated the issue of having a good cable(s) by using official Samsung cables, NEW RocketFish cables and they all seem to work fine for viewing and transferring files via USB. I also have an external battery charger and can guarantee an excellent charge on the battery(s). The current files I was recommended to use came from a single Zipped file: GalaxyNote2UnlockVerizon. Please let me know if there are a different set of files I should be using?
Unless I have downloaded the wrong files? I have attempted to install the following bootloader with Odin versions 3.07, 3.13 and 3.185 and they all fail: BootloaderBaseline2.tar.md5. All I know at this moment i am stuck at a point that I have the Note II in a state that will not allow me to boot.
Lets discuss some hardware issues that I need to explore a little further. Since I have a spare phone to test with I thought I would swap logic/motherboards and see if I had any different results. Unfortunately they are exactly the same on both Note II's. Now comes an interesting issue I stumbled upon. When I VERY CAREFULLY reassembled it on an ESD Mat I somehow dislodged or did not securely fasten the display cable to the logic board and when the power was pressed the phone seemed to start booting but there was no display. The sound and the blue light came on normally. I had hoped the original ROM was now installing. I powered off the phone, removed the battery and disassembled it to discover my mishap, so I reconnected the display cable and reassembled the phone only to see the original problem was still present.
Has anyone else had a charging port issue that caused similar problems? I was planning on ordering a new charging port off Amazon today just to try. Any additional information would be greatly appreciated.
Thank all of you that contribute to this site. It is amazing how many problems can be resolved when great minds are put together.
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
No Red Light
droidstyle said:
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
Click to expand...
Click to collapse
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
jvaldez33 said:
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
Click to expand...
Click to collapse
look for a n7100 tar, or maybe "I think, can't remember" there was a stock tar in the I605 mega roll thread somewhere. flash one of them. Try not to use the kies tar as i've had problems with them being corrupted before. Know you've tried both the methods already. Just a suggestion in case you have not. Also check and make sure you have the right pda file.
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.