Related
so i bricked my vibrant yesterday. i was running macnut r12 and i tried to flash one of my backup roms. since then my phone gets stuck at the galaxy s gt-i9000 screen. i've searched all day for a solution and nothing has worked.
none of the button combinations i read to boot in recovery or download mode has worked. odin sometimes does detect the phone as com3, but that's as far as i can get it.
is the phone pretty much dead? any help would be great. thanks!
I had the same problem when I tried to downgrade from a 2.2 ROM, to a 2.1 ROM. give this thread a read, and you should be able to fix it in under five min.
http://forum.xda-developers.com/showthread.php?t=732458
I did the same yesterday.
My fix was to remove the battery, re-insert, immediately go into download mode, do not try to boot. Then use odin to put on a stock ROM.
Worked for me.
FYI, this anso allowed me to get into clockwork, but I could not successfully recover anything using it.
Sent from my SGH-T959 using XDA App
You're phone's fine...last week mine got to the point where I couldn't get it to do anything at all (caused by my first attempt to use odin...ironic, huh? haha). It was my first brick, so I was sweating bullets.
You need to get into download mode...once there you'll be good. Here's the thread that saved me: http://forum.xda-developers.com/showthread.php?p=9370249#post9370249. I had to pull everything (sim, sd, battery), plug in the usb, hold both volume rockers, then reinsert battery. Presto...dl mode.
And it might matter what version of odin you're using. Version 1.0 is what bricked my phone b/c it froze part way through a restore. I downloaded v1.3 and it worked flawlessly.
thanks for the reply everyone. i've tried getting the phone to boot in dl mode, but nothing seems to work. i've tried pulling out the battery, sim, and sd, holding both vol. buttons and plugging in the usb and all i get is the charge screen.
another question i had is when i plug my phone into my computer should the computer still detect the phone even at the state its in?
Mine didn't. But I also was able to do what the previous post said.
Remember you have to have both volume buttons pressed while you put the battery in. not after.
Sent from my SGH-T959 using XDA App
I'm not sure where to go for help or what to do next, so I'm posting on here (I've read a lot of great stuff on here in the past and now!). So, here's the story:
Tmobile came out with their 2.2 update and I decided to get on the band wagon and update my phone. What I didn't know after I started was that the stupid Samsung program doesn't want to work with Win7 x64 for whatever reason. So after my phone is sitting at 2% for two hours, I decide enough is enough and I disconnect it and reset it.
Now it's got the phone...!...PC picture on it (or black screen o' death).
I've tried just about every combination of the 3-button push to get it into the "download" screen I've been able to find on this forum and others, but all I ever get is the black screen of death. I've got Odin installed and it sees it when I connect the phone via the USB cable, but I still never get onto the download screen. I thought "what the hell" and tried to flash it anyways with Odin. The phone went to a completely purple screen. Reset and back to the Black screen of death.
So, there you have it. Is there anything else I can try? Or is my phone dead dead? I've read about some kind of micro-usb-resister thing I can try, but I'm not positive of being able to reproduce that item. I've also read a lot of terms and procedures that I'm very unfamiliar with. I'm a compelte noob when it comes to flashing and rooting my phone in fears of this exact problem. Now I'm facing it and need some help.
Thanks in advance for your help!
All I can tell you is keep trying to get into dl mode. It can be a real pain in the ass getting the three button to work sometimes. Good luck.
Sent from my SGH-T959 using XDA App
Pull everything out, battery, sim, microsd
Have ODIN open
Plug the usb into the PC
Plug usb into the Phone
Hold down ONLY the volume buttons
Put the battery in
Take your battery, sim, and everything out of your phone. Open odin. Connect usb cable to your computer only. Put your battery back in. Hold volume up + volume down. Connect usb to your phone. BOOM. You should be in download mode and recognized in odin.
Flash back to stock. If it's that messed up, you may have to use eugenes froyo that doesn't brick first. Search the stickies for that.
Hope this helps.
Sent from my nuclear powered submarine!
jmcghee1973 said:
Pull everything out, battery, sim, microsd
Have ODIN open
Plug the usb into the PC
Plug usb into the Phone
Hold down ONLY the volume buttons
Put the battery in
Click to expand...
Click to collapse
Lol! You posted as I was typing it out.
Sent from my nuclear powered submarine!
offdutyninja808 said:
Take your battery, sim, and everything out of your phone. Open odin. Connect usb cable to your computer only. Put your battery back in. Hold volume up + volume down. Connect usb to your phone. BOOM. You should be in download mode and recognized in odin.
Flash back to stock. If it's that messed up, you may have to use eugenes froyo that doesn't brick first. Search the stickies for that.
Hope this helps.
Sent from my nuclear powered submarine!
Click to expand...
Click to collapse
Thanks for posting! So, I tried both methods that you two mentioned, but I'm still only getting the phone..!..PC image. SD card, SIM, and Battery removed; connected USB, held down volumen buttons, and put in battery. Odin does appear to see the device attached (shows up "0:[COM5]" highlighted in yellow), however. Any other thoughts or perhaps there is something I'm missing?
Thanks again for your help!
Addition: I'm using Windows 7 Pro x64 if it matter..
Try odin on different pc. Or try different version of odin. Did you make sure you had proper Samsung drivers installed? 64 bit drivers. After opening odin make sure you have micro usb plugged to pc. Hold only the volume up and volume down buttons at the same time. Now plug usb to cell and that should do it.
Sent from my SGH-T959 using XDA App
Try it with the phone just powered off.
Pull the battery and unplug the USB from the phone.
Leave it plugged into the PC.
When you put the battery back in it should stay powered off.
Now with the battery back in, ODIN open, and your holding both of the volume buttons down, plug the phone in to the usb.
***Opps looks like rayvil already posted this method
It's working!!
So, when the xda forums went down last night and I didn't have much other guidance I decided "what's the worse that could happen if I keep on screwing with it?". Well, I could never get to the actual download screen no matter what buttons or combination of buttons I pressed. However, my computer would always recognize the device and so would Odin.
I downloaded a .PIT file, loaded it into Odin with the new 2.2 .TAR file. Then I hit "Start". To my amazement, the thing started to update the phone! Even while the phone was still on the "phone..!..PC" image. There was even the download/process bar showing up on the phone itself. 10-15 minutes later and the phone is up and running. The best part, though, was that all my settings and apps were still loaded and working! Odin must have taken over what samsung's piece-of-crap Kies program couldn't do and finished the upgrade process.
Thanks to everyone's input and this forum! It's a lifesaver!
Lappitude said:
It's working!!
So, when the xda forums went down last night and I didn't have much other guidance I decided "what's the worse that could happen if I keep on screwing with it?". Well, I could never get to the actual download screen no matter what buttons or combination of buttons I pressed. However, my computer would always recognize the device and so would Odin.
I downloaded a .PIT file, loaded it into Odin with the new 2.2 .TAR file. Then I hit "Start". To my amazement, the thing started to update the phone! Even while the phone was still on the "phone..!..PC" image. There was even the download/process bar showing up on the phone itself. 10-15 minutes later and the phone is up and running. The best part, though, was that all my settings and apps were still loaded and working! Odin must have taken over what samsung's piece-of-crap Kies program couldn't do and finished the upgrade process.
Thanks to everyone's input and this forum! It's a lifesaver!
Click to expand...
Click to collapse
Great ! Congratulation !
BTW ODIN is made by Samsung also if you didn't know that !
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I was flashing from MIUI 1.9 to MIUI ICS in CWM and all seemed well until upon boot it hung on the MIUI bootup screen. After waiting about 15 minutes I figured I would simply ODIN back to stock and try again as I normally do when I have a problem flashing. In ODIN however I was unable to make it past the boot.inf stage of the flashing. Stupidly I unplugged the usb cable mid flash and tried again, and again same result, it would hang at boot.inf. After trying a couple different stock ODIN files the phone will not turn on at all. Even if I pull the battery and connect the phone to the pc I cannot boot into download mode. When I connect to the wall charger the battery screen does not come on either.
Strangely if I press the power button on the phone with the phone connected to the pc, windows will make the sound of a usb device being connected, however, if I release the power button it makes the sound of a usb device being disconnected. ODIN does not seem to be recognizing my phone anymore since I haven't been able to boot into download mode.
I've bought a usb jib hoping this would solve the problem but it hasn't seemed to work. Maybe I'm doing something wrong.
Please someone help me get my phone up and running again. I've flashed numerous roms before and had trouble but nothing as serious as this.
Try reading up on Droidstyles Guide . Its in General section .
Sent from my SCH-I500 using xda app-developers app
Thanks for that. I went through his guide but unfortunately I think my problem is a little more serious. My phone will not turn on at all. I cannot boot into CWM, download mode or boot normally. The screen just remains black. It doesn't show up as a recognized device in windows but when I connect the usb cable it makes a sound of it being connected.
If any has any ideas on things I could try I would be really grateful. I bought my phone out of contract and can't really afford to buy a new one right now.
iztel said:
Thanks for that. I went through his guide but unfortunately I think my problem is a little more serious. My phone will not turn on at all. I cannot boot into CWM, download mode or boot normally. The screen just remains black. It doesn't show up as a recognized device in windows but when I connect the usb cable it makes a sound of it being connected.
If any has any ideas on things I could try I would be really grateful. I bought my phone out of contract and can't really afford to buy a new one right now.
Click to expand...
Click to collapse
Can you "3 finger" into recovery ?
Sent from my SCH-I500 using xda app-developers app
No, when I try to use the 3 buttons to boot into recovery the screen stays black.
Another strange thing it's doing is when I connect the phone to my Mac with the SD card in the phone the Mac will continuously popup a window that asks whether I want to connect the usb device to the Mac or my virtual machine. It flashes so fast I'm unable to click either option. If I connect the phone without the SD card in this menu never comes up but I'm still unable to boot into download mode.
Hmm....I've never heard this before...have you tried plugging phone charger in ( wall outlet ) and let it charge 8 full hours
Sent from my SCH-I500 using xda app-developers app
You say you bought " out of contract", from a private seller ? No warranty?
Sent from my SCH-I500 using xda app-developers app
I charged it from the wall charger overnight still no luck. Yeah, I bought it a year and a half ago used from ebay. I think it's really strange too. I've had plenty of hiccups flashing roms before but it's never been something ODIN couldn't fix and I'd at least be able to get into download mode.
I think you are going to have to use UnbrickableMod.
Thanks MM. I bit the bullet and bought a used Galaxy S II. I may still try that unbrickable mod so I can give my Fassy to my mom who's overdue for a smartphone. I've never used a soldering iron though and not too certain how successful I'll be.
iztel said:
Thanks MM. I bit the bullet and bought a used Galaxy S II. I may still try that unbrickable mod so I can give my Fassy to my mom who's overdue for a smartphone. I've never used a soldering iron though and not too certain how successful I'll be.
Click to expand...
Click to collapse
Have you tried the wall plug trick?
I had been running a Fascinate rom on a Showcase for almost a year & the same thing happened to me. Initially, the battery had run completely down and after full charge, I had nothing but bootloops. At first I could connect via odin, but could not complete flash.
After messing with it & yanking out the cable as you did, I had same issue, blank screen, pc would beep but that was it, pc/odin would not recognize or show the comm port. I would get unknown device.
Ultimately, I successfully repartitioned & odined a stock Fascinate Froyo EB01 rom by doing several things -- not sure which worked, but perhaps might work for you rather than soldering
First, I fully charged an oem battery using a spare battery charger (not in the fassy)
After charge, I put the batt in the fasc & plugged the fasc in to the wall charger while holding down the volume button & got the download mode to show up.
I left batt in when I unplugged from wall & the download mode stuck.
Odin still didnt recognize on my laptop, so I tried 3 other machines till I Odin finally saw the fascinate, at which point I odined Froyo with .pit & repartitioning as my starting point, then clockworked & rooted etc. I think I left battery in during the flash, then reflashed later in download mode with battery out.
I was also successful using heimdall a few times, when another pc wasn't available & odin wasn't playing nice. Was very odd, as 2 of those laptops ALWAYS worked fine with odin & the fascinated showcase before. Now they still won't recognize, but I can easily odin if I try diff computers --- some windows 7 some xp & some vista.
Magickly said:
Have you tried the wall plug trick?
I had been running a Fascinate rom on a Showcase for almost a year & the same thing happened to me. Initially, the battery had run completely down and after full charge, I had nothing but bootloops. At first I could connect via odin, but could not complete flash.
After messing with it & yanking out the cable as you did, I had same issue, blank screen, pc would beep but that was it, pc/odin would not recognize or show the comm port. I would get unknown device.
Ultimately, I successfully repartitioned & odined a stock Fascinate Froyo EB01 rom by doing several things -- not sure which worked, but perhaps might work for you rather than soldering
First, I fully charged an oem battery using a spare battery charger (not in the fassy)
After charge, I put the batt in the fasc & plugged the fasc in to the wall charger while holding down the volume button & got the download mode to show up.
I left batt in when I unplugged from wall & the download mode stuck.
Odin still didnt recognize on my laptop, so I tried 3 other machines till I Odin finally saw the fascinate, at which point I odined Froyo with .pit & repartitioning as my starting point, then clockworked & rooted etc. I think I left battery in during the flash, then reflashed later in download mode with battery out.
I was also successful using heimdall a few times, when another pc wasn't available & odin wasn't playing nice. Was very odd, as 2 of those laptops ALWAYS worked fine with odin & the fascinated showcase before. Now they still won't recognize, but I can easily odin if I try diff computers --- some windows 7 some xp & some vista.
Click to expand...
Click to collapse
I had the same issue. I think it had to do with the battery being too low. I think that ODIN could have a check in place to allow only to flash if the battery is not clos to low in case things go wrong. I had a second fully charged battery and when i read the above post, i changed the battery across and it set it to download and ODIN eventually detected it. Thanks for the help guys.
I have a similar problem, I was on PA JB rom 2.18, and I decided to flash latest devil kernel [1.5.2? or something like that]
so then it would just boot into devil recovery. and that's all. Tried to flash pa rom over it [to get stock recovery back] but it failed. also it had lots of errors about mounting.
So I did advanced restore, and chose to restore boot from other JB backup. This just made it worse, bootlooping into an android recovery with a "!" triangle, then immediately rebooting, over and over again..
So I put into download mode, and heimdall a boot.img extracted from the JB rom [paranoid android], and it still didn't work right.
So then I heimdall'ed the atlas.2.2.pit, thinking the partition was screwed. Then I was booted into cwm 6.x! So I thought I was out of the woods, and wiped, then flashed PA 2.18 jb rom, and then rebooted.. and then I had no samsung logo bootloop. I could tell cuz it was dark, and I could see the backlight coming on and off. on, off... on... off... endlessly.
I tried download mode, and it didn't work. That's when I got scared.. I tried it again, nothing. just the black [very dim black, because of super amoled technology] screen, coming on and off..
So I finally tried taking the battery out, and then it went into download mode!
But I still cannot figure out why it will not let me flash any rom. I'm gonna have to boot into windows and odin back to EH03.
Good thing I have a 3-4 day old backup.
So, do not use devil kernel unless you want a softbrick.
mvmacd said:
I have a similar problem, I was on PA JB rom 2.18, and I decided to flash latest devil kernel [1.5.2? or something like that]
so then it would just boot into devil recovery. and that's all. Tried to flash pa rom over it [to get stock recovery back] but it failed. also it had lots of errors about mounting.
So I did advanced restore, and chose to restore boot from other JB backup. This just made it worse, bootlooping into an android recovery with a "!" triangle, then immediately rebooting, over and over again..
So I put into download mode, and heimdall a boot.img extracted from the JB rom [paranoid android], and it still didn't work right.
So then I heimdall'ed the atlas.2.2.pit, thinking the partition was screwed. Then I was booted into cwm 6.x! So I thought I was out of the woods, and wiped, then flashed PA 2.18 jb rom, and then rebooted.. and then I had no samsung logo bootloop. I could tell cuz it was dark, and I could see the backlight coming on and off. on, off... on... off... endlessly.
I tried download mode, and it didn't work. That's when I got scared.. I tried it again, nothing. just the black [very dim black, because of super amoled technology] screen, coming on and off..
So I finally tried taking the battery out, and then it went into download mode!
But I still cannot figure out why it will not let me flash any rom. I'm gonna have to boot into windows and odin back to EH03.
Good thing I have a 3-4 day old backup.
So, do not use devil kernel unless you want a softbrick.
Click to expand...
Click to collapse
I think the problem is you used the wrong Devil... the latest is 1.6.1 and the older ones will not work with the new partition layout. Get it from http://rootaxbox.no-ip.org/derteufel/
Here is some FYI for you guys. If you are using a pc with a USB 2.0 or higher then it provides the power to go into download mode for Odin. That's why people say to remove the battery and then plug in the USB cable and hold the volume and power to go into download mode for odin. IF you are using a desktop then it's best to use one of the hardwired usb ports on the back of your pc, if it's a laptop then they are all hardwired to the motherboard. USB 2.0 and up all provide power through the usb port, therefore if you leave the battery in while Odin'ing it may not be a good outcome, this is just a suggestion.
netlagger said:
Here is some FYI for you guys. If you are using a pc with a USB 2.0 or higher then it provides the power to go into download mode for Odin. That's why people say to remove the battery and then plug in the USB cable and hold the volume and power to go into download mode for odin. IF you are using a desktop then it's best to use one of the hardwired usb ports on the back of your pc, if it's a laptop then they are all hardwired to the motherboard. USB 2.0 and up all provide power through the usb port, therefore if you leave the battery in while Odin'ing it may not be a good outcome, this is just a suggestion.
Click to expand...
Click to collapse
You are suggesting we leave the battery out while Odining? what good would that do?
mvmacd said:
You are suggesting we leave the battery out while Odining? what good would that do?
Click to expand...
Click to collapse
I always Odin without battery. Try it. Remove battery, connect to PC with Odin opened, hold volume down button for dl mode, and fash.
Sent from my SCH-I500 using xda premium
mezster said:
I always Odin without battery. Try it. Remove battery, connect to PC with Odin opened, hold volume down button for dl mode, and fash.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Yet again, I ask, what good would taking the battery out?
I'd have to set it and the cover down and put them back after Odin..
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
Yet again, I ask, what good would taking the battery out?
I'd have to set it and the cover down and put them back after Odin..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's probably just a precaution so you don't accidentally reboot the phone while flashing or something like that. Every guide I have read says to pull battery before using Odin so I do... and I haven't had any problems. I think it'll probably work fine with the battery in, but why bother taking the risk?
Crawshayi said:
It's probably just a precaution so you don't accidentally reboot the phone while flashing or something like that. Every guide I have read says to pull battery before using Odin so I do... and I haven't had any problems. I think it'll probably work fine with the battery in, but why bother taking the risk?
Click to expand...
Click to collapse
how would the battery cause the phone to reboot?
I have never Odin'd without the battery. And I never had any problems
So yesterday morning I went to turn on my phone, but nothing happened. It was on the charger all night so it should have been a full battery.
Here are my symptoms:
1) AC plugged in without battery - Phone's screen turns on for a second, turns off, and then repeats.
2) AC plugged in with battery - Phone will start to charge (has the loading symbol in the battery), but then turns off immediately. It cannot boot into recovery. It CAN boot into download mode, but my computer will not recognize it to restore the phone with odin.
Any ideas?
I don't have an official upgrade until October, but I'm going to call customer service to try and get them to bump the date up so I can get a new phone.
First possibility to suspect is a failed battery. If you know someone else with an s2, ask to borrow their battery temporarily to see if your phone will boot. Or perhaps go to an AT&T store to see if you can borrow a battery.
If it's not the battery, then the next step to try is to boot into download mode with the battery out of the phone to see if Odin will recognize the phone with the battery out. With the battery out of the phone and the USB cable plugged into the computer, hold down the vol down button while plugging the USB cable into the phone. The computer will supply the power. This assumes that you have the proper "Samsung USB driver for mobile phones" installed on your PC.
That's a start.
I am having the same issue with my s2. i had shostock installed on it a few weeks back and it was working fine. then it just stopped working. i tried rebooting but it keeps on going on bootloops. I tried using odin to flash back to stock but no go, just bootloops. kies just dont work for me. i know it isnt the battery cuz i have the charging cradle to charge the battery and the phone goes to odin mode without the battery. Any help is appreciated.
sfb14 said:
I am having the same issue with my s2. i had shostock installed on it a few weeks back and it was working fine. then it just stopped working. i tried rebooting but it keeps on going on bootloops. I tried using odin to flash back to stock but no go, just bootloops. kies just dont work for me. i know it isnt the battery cuz i have the charging cradle to charge the battery and the phone goes to odin mode without the battery. Any help is appreciated.
Click to expand...
Click to collapse
It sounds like you got a successful flash of stock. Boot into recovery and perform a wipe data/factory reset.
creepyncrawly said:
It sounds like you got a successful flash of stock. Boot into recovery and perform a wipe data/factory reset.
Click to expand...
Click to collapse
I just did. Still no boot.
sfb14 said:
I just did. Still no boot.
Click to expand...
Click to collapse
OK. Did the flash to stock succeed? In other words, you got a pass in odin?
Which version of SHOstock was installed, the latest? And which version of stock did you flash?
i flashed SHOstock v3 before all of this happened. i flashed ucle5 stock rooted. battery icon flashes capacitive keys blink over and over again. if i unplug it nothing happens. i may have to try UCKH7 once im done downloading it.
** after flashing KH7, i go to recovery to wipe/factory reset... there is a message saying
Installing Multi-CSC...
"can't access to '/system/csc/ATT/system/'
Successfully applied multi-CSC
sfb14 said:
i flashed SHOstock v3 before all of this happened. i flashed ucle5 stock rooted. battery icon flashes capacitive keys blink over and over again. if i unplug it nothing happens. i may have to try UCKH7 once im done downloading it.
** after flashing KH7, i go to recovery to wipe/factory reset... there is a message saying
Installing Multi-CSC...
"can't access to '/system/csc/ATT/system/'
Successfully applied multi-CSC
Click to expand...
Click to collapse
This is sounding a bit like nand read/write corruption, which is fixable. Try this:
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful and boots normally you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Will try that later. Thanks for your help!
Sent from my SAMSUNG-SGH-I337 using xda premium
still no luck.. i did everything odin says "PASS" but it just wont boot. i'm going to try and get a different battery and see if that works.
thanks for your help sir. :good:
sfb14 said:
still no luck.. i did everything odin says "PASS" but it just wont boot. i'm going to try and get a different battery and see if that works.
thanks for your help sir. :good:
Click to expand...
Click to collapse
Going through the exact same issue with my kids phone with the same results. Tried creepy's 6 steps, but still no luck.
I think it was caused by my kid killing the battery.
update: got it to boot into custom recovery, then reflashed ROM. It stills acts weird though. Very laggy.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t-usb-port-repair/
Sent from my SGH-I777 using xda app-developers app
Having a very similar issue here.. Battery icon flashes then black screen. Boot to download mode.. Push up arrow, black screen. Computer does not register device connected.
Sent from my SGH-I997 using xda app-developers app
jvick920 said:
Having a very similar issue here.. Battery icon flashes then black screen. Boot to download mode.. Push up arrow, black screen. Computer does not register device connected.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It's hard to give any suggestions with this little information. More information would be useful. A lot more information would be more helpful.
creepyncrawly said:
It's hard to give any suggestions with this little information. More information would be useful. A lot more information would be more helpful.
Click to expand...
Click to collapse
When I plug then phone in (automatically turns on when plugged in, power button is broken), the battery logo and hardware buttons flash erratically for up to a minute then nothing at all. I've tried different batteries and different cords. The only thing that seems to bring it back to life is letting the phone and battery sit unplugged for 2 weeks up to a month and trying again, but it's very hit or miss. This only seems to happen when the battery completely drains.
jvick920 said:
When I plug then phone in (automatically turns on when plugged in, power button is broken), the battery logo and hardware buttons flash erratically for up to a minute then nothing at all. I've tried different batteries and different cords. The only thing that seems to bring it back to life is letting the phone and battery sit unplugged for 2 weeks up to a month and trying again, but it's very hit or miss. This only seems to happen when the battery completely drains.
Click to expand...
Click to collapse
What phone do you have... the AT&T SGH-I777 does not have hardware buttons, but maybe you mean the capacitive buttons which are part of the display? Your previous post was sent from an Infuse? If it's not an I777 then you need a different forum.
If the phone that has the problem is an SGH-I777, then... what firmware is/was it running? Is it rooted? Is USB debugging turned on? Have you been able to boot into download mode since your first post? How long was the power button broken before this problem first manifested?
I think you need to get into download mode and flash stock firmware.
You also may need to see if you can do something about the broken power button, since that may be involved in the problem. That would mean either taking the phone apart and trying to mechanically clean the button or move/press/activate it a lot to get the dirt out so that the problem clears itself, or it may mean getting it replaced.
creepyncrawly said:
What phone do you have... the AT&T SGH-I777 does not have hardware buttons, but maybe you mean the capacitive buttons which are part of the display? Your previous post was sent from an Infuse? If it's not an I777 then you need a different forum.
If the phone that has the problem is an SGH-I777, then... what firmware is/was it running? Is it rooted? Is USB debugging turned on? Have you been able to boot into download mode since your first post? How long was the power button broken before this problem first manifested?
I think you need to get into download mode and flash stock firmware.
You also may need to see if you can do something about the broken power button, since that may be involved in the problem. That would mean either taking the phone apart and trying to mechanically clean the button or move/press/activate it a lot to get the dirt out so that the problem clears itself, or it may mean getting it replaced.
Click to expand...
Click to collapse
It is the I777, capacitive buttons is what I meant.. I apologize, I'm still fairly new with terminology.. Yes, I have an Infuse also, it's my backup phone because I can't get the s2 to charge. It is rooted and flashed, running 4.2.2 (Avatar ROM)
The problem is, it isn't holding enough of a charge to do anything. Aside from the previously stated issue, it will go into download mode, but the screen will only stay on for maybe 5 seconds max. The power button has been broken about 6 months before this issue arose. This only started happening about a month ago when I let the battery discharge completely. To test my theory that it's a battery/charging issue, I got a backup battery (which allowed the phone to work again) and I allowed that one to discharge completely. Now I'm having the same issue with both batteries. I was able to get the phone to power on once after letting the phone and battery sit disconnected for about 2 weeks.
jvick920 said:
It is the I777, capacitive buttons is what I meant.. I apologize, I'm still fairly new with terminology.. Yes, I have an Infuse also, it's my backup phone because I can't get the s2 to charge. It is rooted and flashed, running 4.2.2 (Avatar ROM)
The problem is, it isn't holding enough of a charge to do anything. Aside from the previously stated issue, it will go into download mode, but the screen will only stay on for maybe 5 seconds max. The power button has been broken about 6 months before this issue arose. This only started happening about a month ago when I let the battery discharge completely. To test my theory that it's a battery/charging issue, I got a backup battery (which allowed the phone to work again) and I allowed that one to discharge completely. Now I'm having the same issue with both batteries. I was able to get the phone to power on once after letting the phone and battery sit disconnected for about 2 weeks.
Click to expand...
Click to collapse
What firmware is/was it running?
Is it rooted?
Is USB debugging turned on?
Did it charge the second battery fully more than once?
How long did it operate with the second battery?
creepyncrawly said:
What firmware is/was it running?
Is it rooted?
Is USB debugging turned on?
Did it charge the second battery fully more than once?
How long did it operate with the second battery?
Click to expand...
Click to collapse
Firmware is CM 10.1, it is rooted, running AvatarROM. USB debugging and mock locations were turned on. It had no issue charging while it was working, it was after I allowed the batteries to die that I started having issues. Even on the second battery, it would continue operating as long as I kept it charged.
jvick920 said:
Firmware is CM 10.1, it is rooted, running AvatarROM. USB debugging and mock locations were turned on. It had no issue charging while it was working, it was after I allowed the batteries to die that I started having issues. Even on the second battery, it would continue operating as long as I kept it charged.
Click to expand...
Click to collapse
I have never used Cyanogen Mod or any of the other AOSP firmware, and I don't know how the firmware would affect this issue, if at all. But I suspect there may be some link.
I think what you need to do is to flash back to stock firmware, or perhaps use one of the stock plus root packages, and then a custom kernel, and then reload CM 10.1. So try this:
Pull the battery and leave it out. Open Odin3 on the desktop and then while holding down the volume buttons, plug in the usb cable. See if the phone will boot into download mode this way, and if Odin will recognize it. If so, then go ahead and flash the stock of your choosing. I think if it were me, I would flash 4.0.4 UCLL6 plus root.
So I have had the phone for a while and have been running Task's AOKP ROM with minimal hiccups.
I had the phone charging and when I unplugged it it would not turn on.
After pulling the battery and rebooting, I noticed that the stock AOKP boot image appeared (as opposed to my custom one) and the phone got stuck in a boot loop. Booting in to CWM I could see that something had gone wrong as it kept popping up about a recovery log file not being found.
When I tried to reboot the phone it did not do so, even after charging. No sign of life at all. Buying a new battery didn't help - it still shows no signs of life at all.
Anyone any ideas? Anything I can try? I'm willing to flash back to stock if that's what it takes but I can't even get it to power on in to CWM to do so.
Would the USB JIG help?
The jig might help. If you have one on hand try that first. Otherwise, try to boot into download mode with the battery out. Do the following:
Pull the battery and leave it out.
Open Odin3 (v1.85 recommended) on the desktop.
Have USB cable plugged in to appropriate port on computer but not connected to the phone.
Hold the vol down button (or holding both volume buttons is okay) but not the power button and plug the usb cable in to the usb port on the phone. The computer will supply the power.
If you get download mode, and Odin recognizes the phone, flash the full stock package from the Download Repository. UCMD8 is the latest stock.
creepyncrawly said:
The jig might help. If you have one on hand try that first. Otherwise, try to boot into download mode with the battery out. Do the following:
Pull the battery and leave it out.
Open Odin3 (v1.85 recommended) on the desktop.
Have USB cable plugged in to appropriate port on computer but not connected to the phone.
Hold the vol down button (or holding both volume buttons is okay) but not the power button and plug the USB cable in to the USB port on the phone. The computer will supply the power.
If you get download mode, and Odin recognizes the phone, flash the full stock package from the Download Repository. UCMD8 is the latest stock.
Click to expand...
Click to collapse
So I tried your suggestion but plugging the phone in with the battery out does nothing. No sign of life. Do I need to have specific drivers installed?
I have the most recent SAMSUNG drivers for the S2 found here on XDA and have ODIN 1.85 installed but the phone just remains blank and nothing happens. Any other options/thoughts? I it perhaps the USB charging port? Or is it fully bricked? Any way to check?
EDIT: With the phone plugged in and the battery either out or in, the top of the phone does become warmer so it seems like the USB port IS working perhaps? This is very frustrating...
I'm far from experienced with this sort of failure. I can only make suggestions based on my collected knowledge from reading the forum every day, and my understanding of trouble shooting principles. So don't take anything I say as definitive.
Generally, if the phone shows no sign of life, that is the definition of a brick. If it shows no sign of life except getting warm when plugged in, that is a different symptom than "no sign of life."
Do you have a jig, and have you tried inserting the jig with a charged battery in the phone? That would be the third troubleshooting step to see if the phone can enter download mode. 1) standard method to enter download mode with a charged battery. 2) attempt download mode with the battery out 3) attempt download mode using a usb jig with a charged battery.
As far as the usb port, were you aware of any problem with it before this issue came up? As far as I can remember from what people have said in the forum, they know that they have a usb port issue because of wonky behavior, before complete port failure. Also, most people report that their phone still boots when they have usb port failure.
I always hate to suggest spending money, but if you are unable to get into download mode through any method, then I can't think of anything else to do but send it off for repair.
I just resurrected my S2 two days ago when I bought my laptop. Used a jig I made from a YouTube video and all went well other than some slight USB issues like the phone thinks its plugged in sometimes.
Sent from my ATT S4 MF3 using Tapatalk
Bricked phone
I was using CyanDelta for over months without any problem. Today (1 December 2013), I downloaded an update of about 21 MB of Cyanogenmod Nightly 10.2 for Samsung Galaxy S2 SGH I777. While trying to install it, the phone booted into recovery and installed it. However, during the process of Upgrading, i.e. when the screen says “Android is Upgrading”, “Optimizing App”, the phone got stuck at “Optimizing app 271 of 313”. I waited for about 30 minutes before I manually switched off the phone using the power button. Then I restarted the phone and saw a new boot logo of cyanogenmod; but it got into boot loop. Then I booted into recovery and manually installed the new zip (of 1 December 2013) found in CyanDelta folder. Still the phone could not boot. Now I saw “Samsung” logo only once and then the phone completely turned off. Now I could not turn my phone on, nor could I boot into recovery or download mode. Also I fully charged the battery before flashing the new Zip.
I tried all other steps to boot my phone like removing the battery and pressing power button for a minute, plugging the usb cable into PC and pressing the volume down button and also all sorts of other key combinations. Nothing could boot the phone. Please help. Is my phone completely bricked or is there any issue with my battery ?
Phone : Samsung Galaxy S2 SGH I777 (AT&T)
ROM : Cyanogenmod Nightly 10.2
Battery Condition : Poor (But it was fully charged and also charger was plugged in while flashing the Zip)
Email : [email protected]
... and this is the 3rd time you've posted this. Please wait for your answer in the thread you created, or try the steps creepy has laid out. I guarantee you've not tried everything.
SteveMurphy said:
... and this is the 3rd time you've posted this. Please wait for your answer in the thread you created, or try the steps creepy has laid out. I guarantee you've not tried everything.
Click to expand...
Click to collapse
Sorry for the same post being posted thrice. And I have already tried all the methods except for the USB Jig method. I may think of buying usb jig, but is there any specific usb jig available for S2 sgh i777 ? And my phone usually gets warmed up when I put in my battery, but could not do anything with the phone.