Related
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
Hi guys, not entirely sure if this is in the correct place but I believe it is, sorry if it is not.
Today i plugged my Samsung S2 into the laptop and Kies proceeded to connect and everything seemed fine. I then saw that there was a firmware update, I then proceeded to download and try to install it, this failed some how and it then tried to do an emergency recovery which also failed. So i turned the phone on and off again and the screen that appeared was a phone..warning triangle...computer.
I tried plugging it back up but Kies was not connecting with it anymore, and everything i have search about it talks about something called "Odin" and rooting, neither of which i have tried or read about in any great depth.
I contemplated going up to the local shop and seeing if they could do anything although i think they would be just as good as me.
Before today i hadn't updated any firmware at all since getting the phone in January, i have just been using it straight out the box. So my question is, can i fix it? And how would i go about fixing it?
Im am in the UK and on the O2 network if that is any use?
bigredreed said:
Hi guys, not entirely sure if this is in the correct place but I believe it is, sorry if it is not.
Today i plugged my Samsung S2 into the laptop and Kies proceeded to connect and everything seemed fine. I then saw that there was a firmware update, I then proceeded to download and try to install it, this failed some how and it then tried to do an emergency recovery which also failed. So i turned the phone on and off again and the screen that appeared was a phone..warning triangle...computer.
I tried plugging it back up but Kies was not connecting with it anymore, and everything i have search about it talks about something called "Odin" and rooting, neither of which i have tried or read about in any great depth.
I contemplated going up to the local shop and seeing if they could do anything although i think they would be just as good as me.
Before today i hadn't updated any firmware at all since getting the phone in January, i have just been using it straight out the box. So my question is, can i fix it? And how would i go about fixing it?
Im am in the UK and on the O2 network if that is any use?
Click to expand...
Click to collapse
Can you try turning the phone off, then simultaneously press the Down Volume Key + Home Button + Power Button, keeping same depressed for about 10 seconds to see if the phone will boot and enter Download mode?
If it does, then you may be able to use ODIN as per this thread http://forum.xda-developers.com/showthread.php?t=1075278 to properly reload an image.
Better send it to your near Samsung service center to have it replaced if it still under warranty.
if download mode works then jus flash stock rom via odin...an kies dosnt update the device if the space on main drive(ex--c drive )dosnt hav enough space i think around 30 or 60gb is required...an if u wan to update via kies only then flash old stock rom an connect to kies hope all goes well...if none work then try the jig (search on forums)well i made my own jig tht jus pushs the phone to dounload mode........cheeeeerz
ok well here it is ive been the very proud owner of my galaxy note since launch date well ive been too chicken to root but after recieving my stock ics update yesterday i decided to look into rooting it so i came on here seen a couple threads and seen they were saying that the old root method with gingerbread would work with the ics so i attempted it downloaded odin v1.85 ran the tar file it looked liked it worked odin said pass well it rebooted and now it is stuck on the second samsung logo with the blue glowing behind it well i searched many threads and cant find a answer on rootgalaxynote.com another guy had the same problem and i seen they told him to factory data reset so i di but with no luck it is still lokking at me stuck on the samsung logo man and i dont have insurance effin atnt screwed me on that one so wat are my options here or do i have none im prayiung this is not a hardbrick please help
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
You MUST have Kies full installed on the desktop/laptop and make sure you're updated to the latest version.
1) Boot your note into download mode(hold down volume button at the same time as the power button, let go of power button when you feel
your phone vibrate but keep holding down button until you see a prompt to push up volume button to continue or down volume button to
cancel, hit the up button your are now in download mode.)
2) Connect your Note to the laptop with factory USB cable
2) Launch Kies on your desktop (full version)
4) Choose Tools, Firmware upgrade & initialization
a) While in download mode, pull battery and enter the S/N & model name (ALL CAPS!!)
b) It will prompt to initialize to original settings. Click "YES"
c) It will prompt to initialize the latest version. Click "YES"
d) It will download the firmware upgrade components (DO NOT DISCONNECT THE DEVICE!!)
5) It will prompt for firmware upgrade and initialization.
a) Click check box for reading above information
b) Click your choice if you want your information saved on Samsung Kies corporate servers (I choose WITHOUT saving).
Just kick back, wait and the phone will update to the original out of box software with the latest updates already applied. No issue with anything, no tripping of the flash counter, and Samsung/AT&T knows now different (if you tripped the counter back before performing this, or performed the process of installing CWM recovery through ADB as to NOT trip the flash counter when changing recovery).
This is the EXACT process I did, and had an AT&T tech verify and it's not detectable I was rooted, and was running a custom ICS ROM. Now, I will qualify that I DID the Recovery installation with ADB so that I didn't trip the counter with the Recovery installation. So if they are able to check the binary information to detect modification even with flash counter reset, that's out of my hands and can't confirm or deny.
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
isimme said:
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
You MUST have Kies full installed on the desktop/laptop and make sure you're updated to the latest version.
1) Boot your note into download mode(hold down volume button at the same time as the power button, let go of power button when you feel
your phone vibrate but keep holding down button until you see a prompt to push up volume button to continue or down volume button to
cancel, hit the up button your are now in download mode.)
2) Connect your Note to the laptop with factory USB cable
2) Launch Kies on your desktop (full version)
4) Choose Tools, Firmware upgrade & initialization
a) While in download mode, pull battery and enter the S/N & model name (ALL CAPS!!)
b) It will prompt to initialize to original settings. Click "YES"
c) It will prompt to initialize the latest version. Click "YES"
d) It will download the firmware upgrade components (DO NOT DISCONNECT THE DEVICE!!)
5) It will prompt for firmware upgrade and initialization.
a) Click check box for reading above information
b) Click your choice if you want your information saved on Samsung Kies corporate servers (I choose WITHOUT saving).
Just kick back, wait and the phone will update to the original out of box software with the latest updates already applied. No issue with anything, no tripping of the flash counter, and Samsung/AT&T knows now different (if you tripped the counter back before performing this, or performed the process of installing CWM recovery through ADB as to NOT trip the flash counter when changing recovery).
This is the EXACT process I did, and had an AT&T tech verify and it's not detectable I was rooted, and was running a custom ICS ROM. Now, I will qualify that I DID the Recovery installation with ADB so that I didn't trip the counter with the Recovery installation. So if they are able to check the binary information to detect modification even with flash counter reset, that's out of my hands and can't confirm or deny.
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...[/QUOT
well thanku friend im doing it now and every time i get to 69 percent it says ther was a problem with the download file and starts over again this happened wen i originaly did the ics update but after it restarted it wold go to 100 but this time it has already been 3 times it stoped at 69 percent trying again wellit got past the 69 percent and got to 85 percent and said unzip error and closed the whole operation i had to enter in the s/n n model again and start over hopefully it works im trying again
Click to expand...
Click to collapse
getting stuck
every time i get to 69 percent it says error in donload file wt hell
you r amazing
yes it worked after 15 trys but it did work you r the man i c its getting past the sam logo
You cannot root an ice rom with a gb kernel. You need to find a rooted ics kernel and flash it with Odin. Keep in mind it needs to be an Odin flashable .tar. if you need help finding one pm me and I will direct you to one.
Sent from my SAMSUNG-SGH-I717 using xda premium
Rooting is very easy and quite low risk as long as your getting your information from reliable sources. The xda community is very knowledgeable and generous. MOST of the information you find here can be taken to heart.
Sent from my SAMSUNG-SGH-I717 using xda premium
aevans88 said:
You cannot root an ice rom with a gb kernel. You need to find a rooted ics kernel and flash it with Odin. Keep in mind it needs to be an Odin flashable .tar. if you need help finding one pm me and I will direct you to one.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yerp LOL, he knows now...we been pm...a learning experience for him....
We were all noobs at one time. Hell I still find things that I wonder about. I used to be really scared of bricking my phone because I soft bricked my international sgs2 the first time and thought I was screwed. Now I know that its pretty hard to hard brick a galaxy series phone
Sent from my SAMSUNG-SGH-I717 using xda premium
Hi everyone,
I am a noob but I have scoured the earth and not been able to find any answer to this or any case of this occurring... yet. However the incidence may increase over the next few days as Vietnamese users update.
I have an unrooted S2 GT-i9100G (the ones released for Asian markets).
I bought it new out of an unopened box from a major retailer and have never installed any CFW.
I was running ICS without a hitch until yesterday (and had previously successfully updated from Gingerbread), when an official update announcement arrived (I'm assuming Jellybean... finally).
Phone ran update then rebooted and bricked, and now gets stuck on the splash screen (Black screen with "Samsung Galaxy S2 GT-I9100G in the middle).
If I enter recovery mode (down, home, power) then it shows me a screen with ODIN mode!
I don't get it. I thought ODIN was not included in stock phones? I'm also assuming this is why the stock FW update bricked the phone.
What steps should I take now? Since it appears ODIN may exist on the phone in some capacity should I hook it up to the PC and try to root the phone?
So far all I have done is cleared the phone memory using the standard recovery mode, and left ODIN mode running whilst unconnected to PC to see what happened (which was nothing). For some reason the phone drains completely in ODIN mode even when connected to a charger.
Thanks for your input on this one.
EDIT: Also please don't tell me to take it back to the retailer. The phone is out of warranty now and Vietnamese retailers don't take any responsibility for their products after sale, so I need to sort this out by myself. Thanks
Down/home/power is download mode, not recovery mode. Recovery mode is vol up/home/power.
You need to find an I9100G stock rom for your carrier/country from somewhere (maybe Samfirmware ?), get into download mode & flash it with Odin (how to do this has been covered thousands of times here; search). If Odin won't work or the phone/PC won't recognise each other, search for threads re: this issue. There's a set of 10-12 troubleshooting steps you need to try in that instance.
MistahBungle said:
Down/home/power is download mode, not recovery mode. Recovery mode is vol up/home/power.
You need to find an I9100G stock rom for your carrier/country from somewhere (maybe Samfirmware ?), get into download mode & flash it with Odin (how to do this has been covered thousands of times here; search). If Odin won't work or the phone/PC won't recognise each other, search for threads re: this issue. There's a set of 10-12 troubleshooting steps you need to try in that instance.
Click to expand...
Click to collapse
Roger that. I'm sure I can figure out how to do all these things quite easily. But how about the fact that Odin is present on the phone? I was under the impression that Odin is an extra application that you install to root your phone and install CFW. My phone is unrooted and stock out of a sealed box, so should I expect to have Odin on it? I don't want to have CFW on my phone and I'm concerned that even after I fix this issue and unbrick the phone, I will have difficulty installing the latest Jellybean XXV region OFW through automatic update.
It also seems strange and contrary to me that I should have to even use unofficial methods in order to fix an official update that was delivered automatically.
Odin is not present on the phone. Download mode is also referred to as 'Odin mode' because you use Odin to flash whatever (normally stock roms) in this mode. Odin is a piece of Samsung software initially used by techs @ service centres but now widely used by people who visit XDA/similar places to flash stuff to their phones.
Edit - You can think it's 'strange or contrary' that you need to do X or Y to fix your phone. That's fine (Personally, I'm not really interested). That's how you can fix your phone. Sorry if I sound standoffish or whatever, it isn't personal at all, but you're just another person with a (slightly, at this point) busted phone who visits here. I've told you how to fix it, so you can either do that or not.
And there it is. Thanks for your guidance
MistahBungle said:
Odin is not present on the phone. Download mode is also referred to as 'Odin mode' because you use Odin to flash whatever (normally stock roms) in this mode. Odin is a piece of Samsung software initially used by techs @ service centres but now widely used by people who visit XDA/similar places to flash stuff to their phones.
Edit - You can think it's 'strange or contrary' that you need to do X or Y to fix your phone. That's fine (Personally, I'm not really interested). That's how you can fix your phone. Sorry if I sound standoffish or whatever, it isn't personal at all, but you're just another person with a (slightly, at this point) busted phone who visits here. I've told you how to fix it, so you can either do that or not.
Click to expand...
Click to collapse
Well until your final post I wasn't aware that download mode was also called Odin mode and that is perfectly normal for a stock phone to say this. I think it's perfectly reasonable for someone who has done a fair bit of research into fixing a stock phone to hear about Odin only in the context of rooting and CFW (pages which I avoid because I'm not interested in CFW), and thus to be surprised when they see Odin mentioned on their stock phone. Now that you've made me aware that this is normal, I'm perfectly capable of finding the info required to fix the phone.
I appreciate your help. I just wanted to mention this as it seems you feel I have asked this question unnecessarily. I hope this points out that if one follows this particular train of thought of fixing a stock phone then its very possible and not unreasonable to arrive at this conclusion.
Hi Everyone,
First of all I would like to apologize, if I am repeating any question. I tried many threads but I couldn't understand completely. Hence I am afraid I need to ask individually. Hope thats fine with the community.
So, I own a Samsung Galaxy SII since last 27 months. I bought it with Orange on a contract in France and the company unlocked it many months ago since I do not live in France anymore. I have never flashed the phone with any other ROM, or provided root access or anything else. I have always used Kies to update the software. If I remember correctly the phone currently has Jelly Bean on it (4.1.2 I think). It doesn't have any external SD card, just the internal memory.
Due to some unknown reason, since yesterday the phone is not able to boot up. Its stuck at "Samsung GALAXY S II GT-I9100" screen. I tried to used Volume up+Home+Power keys to go into recovery mode which is not possible. I also tried to go in Download mode using Volume down+Home+Power keys which is possible. Then I tried to connect with Kies to connect it but after 15-20 mins Kies gives error in recognizing the device. When I open ODIN 1.85 (I guess that is the version which should work with my phone), it does shows "Added" status for the device.
Now after reading many posts I have realized that restoring to stock rom would resolve the issue, but it still dint for many. What is appropriate way to deal with this problem. I found some stock rom on the page of mobile network comparison webpage , but I am not sure if I should use it or not. Also I am afraid if I should check the region/model etc for this. I guess I should only install ROM which lies in France-Orange category.
I do not care about any data since I back up my phone from time to time. But I do not wish to play around with the phone much, unless required. However I would appreciate if there is any way to restore the contacts and message stuff.
Thank you very much for your help and support. I highly appreciate the effort.