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.
Related
Hi All,
So, I tried to flash Cyanogen mod last night using the instructions here: http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide. I was coming from a BIONIX ROM that flashed fine.
Anyways, the phone went into a reboot loop in the recovery screen and I foolishly just held the power button until it stopped. When I turned it back on it was broken. That is, now all it does is display the white Vibrant logo in the middle of the screen with the smaller Samsung logo below it. If I hold the power button for about 8 seconds the screen goes black for about 2 seconds and then comes right back up to where it was. I can't seem to even turn the phone off any more. It just stays on that screen permanently unless I hold the power button, in which case the screen is off for 2 out of every 10 seconds. Yanking the battery of course turns it off, but putting it back in immediately returns it to the state I've described.
I've scoured these forums and tried every button press + battery state + cable state + SD card/SIM state combo suggested, but the phone won't go to download or recovery mode. I found one thread describing the exact same problem. The OP said he'd try a jig and then disappeared without any further updates. I'm going to try to get my friend to make a jig using one of these sets of instructions
http://forum.xda-developers.com/showthread.php?t=819551
http://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/
but until then my questions is: does anyone have any experience with this problem (can't even turn the phone off)? If so, do you have any recommendations? Did a Jig work?
keep trying to get to download mode, pull battery, plug usb in to computer and to the phone, while holding both volume up and volume down pop in the battery. People have tried hundreds of times with it not working and then all of a sudden *bam* download mode.
So... my friend made me a jig and it works in that I can see the shoveling droid indicating download mode. However Heimdall/Odin won't recognize my phone. Heimdall's zadig utility won't locate the phone either, even with the cable plugged in. I'm, once again, stumped.
Just an update; I've tried Odin on three different computers, two Windows 7 (64 bit) and a Mac (with Heimdall). None of them seem to recognize the phone. Device manager on the Windows 7 machine does not update when I plug the phone in (in Download mode via the jig or not) and I can't find anything about Samsung in it anywhere. However I have installed the Samsung drivers; a few different sets I've found around the forums. I've also tried a couple utilities like the Vibrant toolbox and one click unbrick. Nothing seems to have any effect. I was so hopeful when the jig worked and got me to download mode, but now it's seeming I'm actually bricked. Has anyone seen a phone that could get to download mode but still be bricked? Oh, and I checked the cable using a friend's phone; her Mac recognized her phone using the cable. Haven't tried her phone on my Window's machines though.
Once again, any help is more than appreciated.
Have you tried to see if adb is working? If it does then try adb reboot recovery? If it works there is a file I can post for you later (is in my pc) that can restore your sbl.bin and fix your download mode problems.
Thanks for your help everyone, the problem was apparently resolved by a new cable; which is strange because the old one works for data transfers... just not for flashing apaprently. :S
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
I have a rooted i777 with SHOstock rom, I haven't updated the rom for a few months so I'm not sure which version it is.
The phone was working yesterday and it suddenly got stuck so I tried to reboot it (had to take out the battery because the power button didn't respond) but now each time I try to turn it on it is stuck on a black screen with the logo "Samsung Galaxy SII" and won't progress.
I tried to boot to recovery but it shows a screen saying "CWM-based Recovery v6.0.2.7" but it doesn't go pass the screen to show the recovery menu (it just reboots after being stuck on this screen for about a minute).
I tried to boot to download mode and succeeded, but every time I connect the device to my pc, the pc doesn't recognize it
(I tried re-installing kies, but it didn't help and probably the problem is not with the pc drivers because if I connect my wife's unrooted i777 to the pc it does recognize it).
so now I don't have clue what else to try.
any advice will be appreciated.
Make sure you have Odin v1.85 on your Windows PC. Look in the Windows Add/Remove programs dialog (or Uninstall a Program dialog) to see if you have SAMSUNG USB driver for mobile phones.
Open Odin on the desktop. Next put the phone into download mode by holding down vol + and vol - while plugging in the USB cable.
If Odin recognizes your phone, flash back to stock. I would recommend UCMD8 stock firmware, which you can get from the Download Repository.
don't know what happened to it but now it doesn't even turn on.
it's stopped turning on before I had a chance to try what you suggested.
now even if I connect it to the charger it doesn't show the charging status.
is there any other "force something" I can try?
kokoman said:
is there any other "force something" I can try?
Click to expand...
Click to collapse
Remove the battery and leave it out. Connect the USB cable to your PC. While holding down the vol- button (also try it with both vol- and vol+) but not the power button, plug the USB cable into the phone. The computer will provide the power. If this works, your phone will go into download mode. If not... you have very likely had some kind of hardware failure.
unfortunately it didn't work.
can't get it to download mode.
I'll try to leave the battery out for a longer time and try again.
should I try ordering a JTAG usb and see if it puts it in download mode or
probably my only option is to send it to mobiletechvideos?
I had the same problem, Your battery got too low. Pull your battery and leave it out for a while 15 mins or so. Put the battery back in and connect charger. Let the battery charge for a while without trying to turn on phone. The phone will not turn on with a dead battery even if it is connected to charger.
I just solved a problem that I didn't find any help with, so I thought I would post it here in case somebody else needs help out of this situation, and this is a recent and related thread.
After I pulled the battery of my i777 to test in another phone, without remembering to power my phone off first, it would only hang at the Samsung boot logo (stock UCMD8 ROM, rooted, stock recovery). Normally the Samsung boot screen shows for only about five seconds. Pulling the battery wouldn't get it to boot right. Holding Power to force a reboot didn't solve it. After clearing the cache it would move to the AT&T Rethink Possible screen once, then reboot and then again get hung on the Samsung logo screen. Also my battery was heating up a lot as it was hung.
I could get into both download mode and recovery. I tried reflashing my ROM from the stock file in ODIN since that would save all of my data IF it worked. This still didn't get it to boot past the first logo. Finally doing a factory reset on stock recovery is what solved my problem. I had to re-add my account and reload apps from scratch, etc.
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]
Alright, head over here (http://forum.xda-developers.com/showthread.php?p=18630030) and read this thread by creepyncrawly.
It works. Virtually everyone who's ever had this phone and flashed custom stuff has had to use his guide at some point, so I promise you it works.... IF you follow the directions!
Good luck.
SteveMurphy said:
Alright, head over here (http://forum.xda-developers.com/showthread.php?p=18630030) and read this thread by creepyncrawly.
It works. Virtually everyone who's ever had this phone and flashed custom stuff has had to use his guide at some point, so I promise you it works.... IF you follow the directions!
Good luck.
Click to expand...
Click to collapse
I will definitely try your suggestions and for that I need to buy a USB Jig (as I am unable to boot into download mode). I will get back to you once I get the Jig. Hope I could boot into download mode using USB Jig. Since my phone is hard bricked, will a jig put it into download mode ? As I have read in various other forums that usb jig works only if the phone is soft bricked.
digesh9870 said:
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]
Click to expand...
Click to collapse
digesh9870 said:
I will definitely try your suggestions and for that I need to buy a USB Jig (as I am unable to boot into download mode). I will get back to you once I get the Jig. Hope I could boot into download mode using USB Jig. Since my phone is hard bricked, will a jig put it into download mode ? As I have read in various other forums that usb jig works only if the phone is soft bricked.
Click to expand...
Click to collapse
I have no idea what CyanDelta could have done. A firmware hard brick would usually be due to a damaged bootloader. Hard brick means no sign of life what-so-ever. If there is any sign of life, then there is hope. You need to get into download mode to proceed with recovering the phone. If you are unable to get into download mode by any means, then you probably need a jtag repair.
I can't tell from what you've written what you have tried so far to get into download mode. So, here are four ways to possibly get the phone to boot into download mode. Try each one of them before you give up. Also, remember that you must have a good working USB connection as well, especially with the battery out.
1) With the battery in, and the USB cable plugged into your pc, hold down vol+ and vol- but not power, and then plug the USB cable into the phone.
2) With the battery in, and phone connected to the pc via USB cable (plugged in at both ends,) hold down the vol- button.
3) With the battery out, and the USB cable plugged into your pc, hold down vol-, and then plug the USB cable into the phone. The USB cable will supply the power.
4) With the battery in, insert the USB jig.
Any USB jig you can buy should work. They are not phone specific. The only critical factor is that the resistance value must fall within a certain range. I don't remember the exact numbers off the top of my head, but I havn't seen anyone complain about bad jigs since Captivate days.
creepyncrawly said:
I have no idea what CyanDelta could have done. A firmware hard brick would usually be due to a damaged bootloader. Hard brick means no sign of life what-so-ever. If there is any sign of life, then there is hope. You need to get into download mode to proceed with recovering the phone. If you are unable to get into download mode by any means, then you probably need a jtag repair.
I can't tell from what you've written what you have tried so far to get into download mode. So, here are four ways to possibly get the phone to boot into download mode. Try each one of them before you give up. Also, remember that you must have a good working USB connection as well, especially with the battery out.
1) With the battery in, and the USB cable plugged into your pc, hold down vol+ and vol- but not power, and then plug the USB cable into the phone.
2) With the battery in, and phone connected to the pc via USB cable (plugged in at both ends,) hold down the vol- button.
3) With the battery out, and the USB cable plugged into your pc, hold down vol-, and then plug the USB cable into the phone. The USB cable will supply the power.
4) With the battery in, insert the USB jig.
Any USB jig you can buy should work. They are not phone specific. The only critical factor is that the resistance value must fall within a certain range. I don't remember the exact numbers off the top of my head, but I havn't seen anyone complain about bad jigs since Captivate days.
Click to expand...
Click to collapse
Thanks for your instant replies. I tried all the above methods except for the last one i.e. usb jig method. None of them worked. I think my phone has no sign of life. I will have to try with USB Jig and then lastly jtag repair.
Even the usb jig could not get me into download mode. The phone is hard bricked.
Sent from my SM-N900 using XDA Premium 4 mobile app
I have a samsung galaxy s3 i9300! While i was sleeping, i was charging my phone and when i woke up the phone was stuck at the initial logo screen of samsung! Then, i tried to press the home bottom power and volume up bottom to reset while it was doing that it went back again to the logo screen before being able to choose wipe cache and stuff! I tried it several times! Then as i was searching through net i saw that odin thing custom Rom and i thought that maybe i should give it a try! So i tried to installed it by connecting my phone to the laptop but my pc did not identify my phone! Then I tried again by connecting and disconnecting the pc with my phone and while doing so i pushed the button of Repartition at Odin. My phone was not identified so i have no idea if that happened! Now my phone does not even open, or charging! Please tell me if there is a way to make it work again!
It might be of some help to mention that my charger is a new one that i bought from bol.com and its not the original one! I have no idea if that affected somehow the mobile functioning.
No, you are unlikely to fix that. You can try a usb jig, see if download mode will start, but it sounds like partial SDS followed by user panic until it was hard bricked.
If it didnt show in odin you have a driver issue and the repartition wouldn't have happened.
Remove battery, sd and sim. Make sure the battery is charged.
Insert battery and hold home+vol down while pressing power once.
If the screen lights up do not let go of home+vol down until it has entered download mode. If the phone wont light up at this point you have a bigger problem.
Once in download mode install the samsung mobile device drivers on your pc, you might need to try different versions, and plug the phone into the pc's usb on the motherboard. Try to avoid using front mounted or shared ports as they are unreliable. If your phone doesnt interact with your pc try other drivers.
Sent from a stolen phone!