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
Okay, So I am as NOOB as NOOB can be,
I got a used SGS2 (Bell/Virgin), I am on Telus so I figured, how hard can it be to unlock it instead of paying some dude to do it for me? (First mistake, and have been humbled every step of the way since!...)
Anyway I will try to keep this relatively short (it will be difficult)... ...I read a few things online and saw that I needed ODIN and a Rooting software, I originally used SuperOneClick, and to download the right insecure kernel to match my original one etc... ...problem is I obviously didn't read nearly enough when I started because I was almost done and then there was a hiccup when SuperOneClick said that I needed to enable SU in Kies. So I decided to go into Kies to try and do so but the instructions before I started Rooting said to put the phone in USB debugging mode. Apparently Kies doesn't see the phone if it is in that mode. Well by this time I can't get past the logo screen and this is where my downward spiral begins.
I then tried to unroot the phone to go back to stock but didn't really know what I was doing and then I read something about the cache needing to be wiped and then after that I read that maybe my OS was wiped. So at this point I did lots of reading (what I should have done in the first place) and most of anything useful I found was on XDA so that is why I am here. It seemed like yes, in fact my OS was wiped because of one of my not so S-M-R-T actions. So I fumbled through and found the right OS for my S2 and I had ODIN going strong and I had the OS loading, the green bar getting bigger in ODIN and the blue bar working it's way across the screen of my S2...I thought "finally!!, I rock!!"... ...then for some reason everything stopped! I had seen in a post that I had to uninstall Kies before doing anything, which I did...but I didn't see until after the fact that my anti-virus likely interfered (I didn't disable it for the process before I started).
At that point of course I was left with a phone that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So then I was afraid to try anything else because many say to steer clear of Kies and also I had read that I may need a USB jig to be able to get it back into download mode because all I was getting was the "firmware upgrade issue" screen. I did make a USB jig with a resistance of 300K Ohms and I *can* get the phone into download mode. (Though another concern is that when I plug the USB jig in and it brings the phone into download mode, the counter is not reset and I read that that was supposed to be reset by the jig.)
So last night I got brave and decided to try and run ODIN and to have another attempt at installation of OS. Now I can get ODIN to detect the phone, but I put the I9100MUGLD3_I9100MBMCLD3_I9100MXXLD3_HOME.tar.md5 file into the PDA section of ODIN and it starts and gets to the part where it says loading firmware or something and then bootload.bin and it stayed like that for like, an hour and then I gave up, fearing that I am just going to screw it up even more.
So now I decided that I am not even close to knowing what to do next but every time I found anything to move forward it was on this site so I figured I may as well join the site since I have been here so often. Now I am hoping for some kind of miracle...so, in advance, please please please and thank you thank you thank you all for your input. (Sorry for the length of this I just wanted to get all the info I could into this)
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
UnwiredDroid said:
Its quite a long story and didnt bother reading it.
If you can still access your phone via odin at downloadmode. Flash a stock firmware for your device and it should fix if it is just a soft brick.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sorry for the length of the story, I thought there may be alot of useful info mixed in with the useless info... ...when you say use stock firmware do you mean the kernel or the actual OS? I tried loading ICS onto it (which I thought was stock but I may be wrong). Is it supposed to be gingerbread or something else? Also where would I find a good file for it.
Thank you again for any input, very much appreciated!
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
schtiven said:
Hey ,
I also have a Virgin Samsung S2 i9100 and the first time I tried rooting it, it got stuck on the screen with the yellow triangle and wouldnt move at all. I believe it was bricked?
anyways, I m not sure I totally understand your situation, but I solved my problem using this thread
http://forum.xda-developers.com/showthread.php?p=21493413
look it under the i9100M section. hope this helps
Click to expand...
Click to collapse
Thank you all so much for your help, I could not get it to work after several tries, I even tried three or 4 different USB cables and ports on my PC and still no. I read on another thread that one person tried another PC and it worked so I tried my friend's laptop and it worked!...my SGS2 boots up and all that now! Very very happy thank you all.
Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy
Hello, today I got a Samsung Galaxy S2 from a friend. I'm not sure how to identify exactly which model, but it's american and doesn't have the oval home(?) button at the bottom.
I've done rooting and flashed roms before onto Samsung phones, and I haven't had this problem.
The phone started off completely stock, no modification whatsoever. Then I downloaded a kernel with clockworkmod on it, and it wouldn't boot again. It would get stuck in the bootloop with the little yellow caution symbol. After trying several other things I was able to flash another kernel onto it, however, something happened in ODIN and it disconnected. Ever since the only thing it does is the blue LED comes on. I cannot access download mode, or the recovery I was going for. When it's turned on it doesn't even have a bootloader.
Thank you very much for the help.
Your problem starts at 'I'm not exactly sure what model it is'. If it has no home button and does have a blue Led, it's most certainly not an i9100. I'm willing to bet you've been flashing the wrong firmwares all along.
Now that your phone disconnected during an Odin flash, it's done for. When you plug it in to the charger, does it get hot? If so, motherboard replacement.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
Remove the battery and check the model.
Then go to the device's forum or ask the mods to move it 98% chance this is the wrong place for you.
Sent from...this is not even my S2
I apologize up front if this is has been previously asked. I found lots of helpful info on here searching through old threads but being a bit of a luddite I was a bit confused exactly which situation applied to me. I live in China and recently bought a s3 I9300I and attempted to root it using the chainfire method from the video on this site. Odin declared success but when the phone rebooted it just went back to download mode with a message at top saying, "Could not do normal boot, ODIN MODE." Turning it off and on, removing battery and retrying Odin flash produce no results. The most important thing of course is just to get the phone back to functioning but I'd also like it rooted if at all possible. I read that using Odin to install a custom kernel would root it and I would not be at all opposed to a good custom kernel. I read something about a binary counter that may need to be reset but that seemed to require doing something with the actual phone functions which don't seem to work. Odin still recognizes it when I plug it in and attempts to let me redo the rooting but it just shows a progress bar then reboots right back into download mode. Sorry if this is basic stuff but I'm kind of terrified of bricking this thing and am just not sure what the best course of action is here. Thanks for any help you can offer.
Chinese stock firmware is different to the international, there is a special thread in general forum on rooting etc.
Do you have a link to that thread? I have looked and cannot find anything that seems specific to this problem.
Please. Searching for "China" or "Chinese" gets me absolutely no relevant results. If this has already been covered can someone please direct me to the thread. I really need to get this phone working and am at a loss. Thanks.