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
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
hey everyone, im having a little trouble with my galaxy2.
its the canadian bell hd lte version, unrooted, running gingerbread 2.3.3. obviously i want to upgrade.
im comfortable with the rooting process using odin...etc.
heres my issue, ive done some looking but couldnt find anybody with the same issue or a solution.
upon attempting to enter download mode, with the phone off, using the vol down + home + pwr key, it does just that, totally skipping the "warning!" screen.
ive also found that odin will not recognize my phone, though the computer does, i am unsure if this is because of the bypass of the warning screen? maybe its time for a jig?
tldr phone will go into download mode, but odin will not recognize, no warning about custom os displayed.
thanks for looking.
Only reason I can think of for it not showing the warning screen before going directly into download mode is because you are holding down all the buttons for so long that it uses that as the "up" which it needs to go from the warning screen straight into download mode. *Like if you need to hold for 5 seconds to get into DL mode, try holding for 4.5 seconds so that you know it's booting into DL mode, but that you're certain you're not stilling holding down the UP button prematurely, so that it's going by the warning screen too quickly for you to notice -- if you really care enough at all*
What's most likely going on with ODIN not recognizing your device is that your Phone's Drivers has for some reason not installed correctly on your PC. That's not too rare of an occasion (happened to my brothers phone the other week when I tried to root it - wouldn't install drivers on my pc [thus not showing up in odin], so we had to use his computer (where they were already installed). What you can do (assuming this is the problem) is 1) Try using a different computer, and if you plug the phone in and the drivers do not start installing within the first minute and a half of connection then you can either look at the device option of windows (device and printer or w.e - see if there's an option for drivers, or uninstalling drivers [so that you can re-install] or something like that), or try downloading Kies (now used for official samsung updates), as I believe there is an option there to install your phone's drivers. Hope that helps, lemme know the results. I'm like 80% sure the problem you're having is the Drivers not being installed proplery on the comp.
dub_lyfe said:
hey everyone, im having a little trouble with my galaxy2.
its the canadian bell hd lte version, unrooted, running gingerbread 2.3.3. obviously i want to upgrade.
im comfortable with the rooting process using odin...etc.
heres my issue, ive done some looking but couldnt find anybody with the same issue or a solution.
upon attempting to enter download mode, with the phone off, using the vol down + home + pwr key, it does just that, totally skipping the "warning!" screen.
ive also found that odin will not recognize my phone, though the computer does, i am unsure if this is because of the bypass of the warning screen? maybe its time for a jig?
tldr phone will go into download mode, but odin will not recognize, no warning about custom os displayed.
thanks for looking.
Click to expand...
Click to collapse
Seems a little odd that it's skipping the warning but don't think it's a big issue.
As for the drivers I would suggest downloading the latest Kies software and installing any updates that should install all necessary drivers
I would then reboot computer and not launch Kies or anything else before opening Odin, Whenever I flash my phone I always run Odin from a fresh reboot just so I know that Kies isn't running or anything else to interfere with flashing process.
*Make sure Kies isn't running in the background when flashing things in Odin or strange things happen and flashing can get interrupted leading to possible bricked device.*
Also make sure USB debugging is enabled on your phone when you use Odin.
thanks for the reaponses!
it is wierd that its skipping the warning.
if a person puts the phone in dl mode, and at the warning screen chooses no, what happens? does the phone still go into dl mode or just reboot?
as for odin i cant check at the moment but ill try that, i have a feeling that the warning may have something to do with it, if someone wants to try to confirm my suspicions above?
will get back on the odin issue when i get a chance.
"ive done some looking but couldnt find anybody with the same issue or a solution." ... then look harder.
yea download the kies drivers or install a temporary cwm on your phone and go through that.
still have yet to get to a computer but messed with the device a bit.
it boots in recovery fine, still no warning for download mode.
also, if i dont continue to hold the dl mode button sequence till it goes straight into.dl.mode, the phone boots as normal.
so the theory of holding the buttons too long seems unlikely.
dub_lyfe said:
still have yet to get to a computer but messed with the device a bit.
it boots in recovery fine, still no warning for download mode.
also, if i dont continue to hold the dl mode button sequence till it goes straight into.dl.mode, the phone boots as normal.
so the theory of holding the buttons too long seems unlikely.
Click to expand...
Click to collapse
Alright I mean if you can get into recovery mode at this point (and download mode seems to work anyway, just doesn't give warning) shouldn't be a problem. If you do try getting the drivers from kies and use download mode then you can figure out if it's bonkers. If not, just use recovery to flash something and all should be well. That's quicker and easier anyway
Also, you should probably note that since you said you have the "canadian bell hd lte version", that you PROBABLY do not have a GT-I9100. So don't go flashing random stuff from the forum (which is for the I9100) - else I can almost guarantee you will run into problems.
(refer to this article, and this post)
If you are right about having the HD LTE version of the Galaxy S II, I'm betting you actually have the SGH-I757M. (you can verify this by looking on the label under the battery)
That phone (the SGH-I757M) doesn't have a dedicated forum, unfortunately. Your best bet is to search XDA for that model number, like this.
I was feeling generous, so I did a bit of legwork for you. The current latest Samsung official version is still 2.3.6. You can get it from sammobile.com. That will offer only minor updates from your current version of 2.3.3.
There IS the CyanogenMod9 custom ROM for your device, if you want to go that route. It'll be listed on the xda site search for your model number that I linked above.
In any case, I must warn you again against flashing anything that is meant for the i9100 Galaxy S II.
EDIT to add: the fact that the model is different from an I9100 could also explain the lack of a warning screen before download mode. There was no warning screen on my girlfriend's old Captivate prior to download mode, so maybe there isn't one on the SGH-I757M, either.
Hi everyone,
I'm sorry if ever I'm posting this on the wrong section cause I'm not sure if this is a problem from android or samsung.
I'm not good at all when it comes to phone troubleshooting so I will try my luck and ask questions about what have happened to my phone just awhile ago. I got this phone from Japan(Samsung Galaxy SII Wimax isw11sc) months ago and I only use it for multimedia purposes as it is region locked and I am at another country atm. everything is running fine until my phone asked for a software update(not really sure what upgrade that was) and I decided to give it a shot and let it download the updates. I left it to do some chores and when I came back to check on it, it reboot looped itself on the AU(mobile phone company from japan) logo.
I did some research and found some things like hard reset and download mode. I tried to do the hard reset(power/home/volume up) method but I can't seem to access the settings instead, the phone keeps on showing me this "Preparing for S/W update. Please wait." after a few seconds, the phone will reset itself back to the reboot loop.
I tried to do the download mode using odin mode but then, I realized that my phone and computer won' connect via USB port because well, my phone won't boot. Also downloaded the manual driver but my pc won't recognize it.(win7 if that helps.)
Please tell me what have happened and what I can do to fix this problem, I don't really care if i lose everything that I have stored on my phone, I just want it to work again. Help will be much appreciated, Thank you.
Hi all,
Im new to the forum and did some searching but cant find the info i need. I tried rooting my verizon note 2 to casuals one click and didnt realize i had updated to android 4.3 prior. So it tried to root 4.1.2. Now my phone has the yellow triangle and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried kies and kies 3 and neither one recognizes my phone.The only way to shut the phone off is to pull the battery.When i reinstall the battery i have a brief window to volume down+home+power and it takes me to odin. I saw this problem in the forums for roms but couldnt find anything on rooting.Please tell me i can fix this and go back to stock, and i didnt lock my phone up for good.I know im an idiot and i didnt back up anything. Ive learned my lesson and will do more research before attempting this again.I also realized there is no root for 4.3 yet. My phone was stock before i tried all this. Its the verizon sch-1605.Any help is much appreciated. Thank you!
gilitin99 said:
Hi all,
Im new to the forum and did some searching but cant find the info i need. I tried rooting my verizon note 2 to casuals one click and didnt realize i had updated to android 4.3 prior. So it tried to root 4.1.2. Now my phone has the yellow triangle and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I tried kies and kies 3 and neither one recognizes my phone.The only way to shut the phone off is to pull the battery.When i reinstall the battery i have a brief window to volume down+home+power and it takes me to odin. I saw this problem in the forums for roms but couldnt find anything on rooting.Please tell me i can fix this and go back to stock, and i didnt lock my phone up for good.I know im an idiot and i didnt back up anything. Ive learned my lesson and will do more research before attempting this again.I also realized there is no root for 4.3 yet. My phone was stock before i tried all this. Its the verizon sch-1605.Any help is much appreciated. Thank you!
Click to expand...
Click to collapse
Couple of things:
- if you've received the 4.3 update, your bootloader is locked and (currently) un-touchable. Don't try to flash, well, anything.
- if you've received the 4.3 update, you've also received Samsung's odius KNOX technology. If you do try to flash anything most things (especially recoveries), you'll trip the KNOX counter and invalidate your warranty (I believe it also means you can't use your phone in enterprise setups that use KNOX)
The good news is that you can restore your phone to working order! You'll need to install the Verizon Software Upgrade Assistant. XDA member scoobysnack posted a link to download the software, though you can also get it from any functioning Verizon Samsung smartphone that's plugged into a computer.
After you've installed the software, turn your phone on and plug it into the computer. Run the software and select the tab on the left column titled 'Repair'. Click on the repair button near the right side and sit back & wait. The software will download the 4.3 OTA and install it. Like ODIN, it is imperative that you not unplug your phone during this process.
If you have trouble getting the software to recognize your phone, it may help to put it into download mode. I had to go through this myself (I foolishly forgot about the bootloader issue and tried to flash a recovery. Sigh).
You can achieve root for 4.3, but there are some serious concerns about Kingo, the software the provides root. XDA doesn't allow links to them due to unanswered questions about privacy concerns due to unusual traffic capture going between the software and (apparently) servers in China
thanks so much. ill try it in the morning when i get off work.
Also when i was in odin and plugged my phone in, the software on the pc didnt recognize my phone either. Is that something i should worry about. I guess the box was supposed to turn green but never did.Many thanks
ok so i got home today and tried downloading verizon software update from the link you gave and it wont open the program. Ive tried on 2 different computers. so i called verizon tech to see if they have it cause i can only find it on the website described eariler, and they said they dont have it. Its only in your phone. Well i cant access my phone to get it and im stumped. They said to go into a verizon store and they should be able to fix it. What are my options? I dont have any data on the phone i need to save so can i just go back to a previous version or wipe it out? Or do i have to do a custom rom? Thanks in advance.
gilitin99 said:
ok so i got home today and tried downloading verizon software update from the link you gave and it wont open the program. Ive tried on 2 different computers. so i called verizon tech to see if they have it cause i can only find it on the website described eariler, and they said they dont have it. Its only in your phone. Well i cant access my phone to get it and im stumped. They said to go into a verizon store and they should be able to fix it. What are my options? I dont have any data on the phone i need to save so can i just go back to a previous version or wipe it out? Or do i have to do a custom rom? Thanks in advance.
Click to expand...
Click to collapse
When you go into ODIN mode (turn off your phone, power on using POWER+HOME+VOL-DOWN), do you a line that reads 'KNOX WARRANTY VOID'? It would be in the upper left corner under 'SYSTEM STATUS'.
I ask because if you don't have that line, you didn't upgrade to 4.3 and your bootloader is NOT locked. You should be able to flash to 4.1.2 from ODIN and go from there (CASUAL to unlock & root, et cetera).
If you do have that line, then your only option is the VZW Software assistant. I'm uploading it now and I'll send you a link via PM. Please keep in mind that if you use the VZW Software assistant, whether your bootloader is currently locked or not, it most definitely will be locked after using it. If you're already locked, no harm done, but I'd make sure first.
It's my beloved I9100P. Last night it strangely failed. I realised in the morning when the alarm didn't go off. The phone was switched off.
When I tried to switch on, it got stuck in boot loop. The carrier animation and samsung logo will keep repeating. So I thought I will go into recover mode and do a factory reset. Phone went into factory mode the first time. I thought let me do a restart from there, just to see what happens. At this point, I noticed a lot of red errors on recovery mode screen, most of which saying something like "unable to mount /cache". I restarted it, but unfortunately the phone again went into boot loop.
Now when I tried, it refused to go even to recovery mode. I tried several times, but every time it got stuck on Samsung Galaxy logo.
It went into download mode fine, so I thought I will flash Orange UK carrier ROM. I downloaded the ROM and tried flashing with ODIN. ODIN recognised the device, but the flashing failed with error "Complete (Write) operation failed".
I don't know what to do now, have exhausted all option that I knew.
Any help in reviving my phone please?
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
wulsic said:
@kaushal101 Keep yourphone phone connected to your pc and keep it in download mode. Dont disconnect it it could turn into a hardbrick which you can't fix without jtag repair service.
What you could do is see or you have installled all drivers, kies is disabled, right odin version. Google the problem and you would probably find an answer fast. I hope this message isnt too late..
Click to expand...
Click to collapse
Interesting. After trying several things, I did unplugged it from the machine. It shows the upgrade failed warning message whenever I try to switch it on now, which was expected.
I can still go to download mode and restart the ODIN flashing original Orange firmware process, but it fails with the same error. The only difference is, the first time it failed on CACHE step. Now it is failing one step earlier, at NAND writing stage.
Is there any hope? I had kies disabled etc., but will give it another shot. My phone was accessible with kies and I could also upload my development APKs from Android studio. So I think drivers shouldn't be a problem.
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
wulsic said:
@kaushal101 I dont really have much knowledge about the s2 anymore, so the only good thing I can suggest is to google the problem and get more people to your thread here to help you and or find other threads about the same thing.
It is good that your phone can still go into downloadmode, I think there is still hope to fix your phone
Click to expand...
Click to collapse
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
kaushal101 said:
Thanks for keeping the hope alive!
Have followed XDA's S2-ODIN troubleshoot guide, with no luck so far. Tried different versions of ODIN, reinstalled USB drivers, made sure KIES is removed from processes etc. None has helped so far. I'll keep looking!
Click to expand...
Click to collapse
Did you tryed another stock rom version?
Try other usb cable.
Sounds weird but try to leave the battery out of your phone for like a couple minutes
Try other usb port.
Try other computer:silly:
These are the things I can think of atm.
Have tried other USB port. Have tried a different firmware.
Am going to try a different PC today, will also give different cable a shot. But the cable I'm using is Samsung official one which came with the phone. And I've been uploading APKs using this cable fine, so am quite sure the cable is fine. But still, will give it a shot. Thanks for replying