Hi there,
To brief the story:
Tried to upgrade my Rogers Captivate non-root Froyo to Gingerbread trough Kies the first attempt failed as after 30 min there was no progress on the installation bar, I disconnected the phone and restarted it, it booted up well and again I tried to upgrade. This time the bar filled up to 10% and then the screen on my phone went all Pink!! and the progress got stuck, then the phone was in semi-bricked state. I tried to flash back to 2.2 stock ROM on Odin 3 v1.82 the progress failed half way with a all purple screen (the green bar on Odin was almost at the beginning of the procedure). I thought to get it into DL mode once more to see if I could succeed but no DL mode anymore, all I get is random dots all over the screen!! and even when it gets connected on COM, ODIN cannot reach it anymore and it fails at Setup Connection. My belief is that my phone is bricked totally, but wanted to see if anybody on XDA has any thoughts for this.
Thanks for the help and time in advance.
Chrs.
metpink said:
Hi there,
To brief the story:
Tried to upgrade my Rogers Captivate non-root Froyo to Gingerbread trough Kies the first attempt failed as after 30 min there was no progress on the installation bar, I disconnected the phone and restarted it, it booted up well and again I tried to upgrade. This time the bar filled up to 10% and then the screen on my phone went all Pink!! and the progress got stuck, then the phone was in semi-bricked state. I tried to flash back to 2.2 stock ROM on Odin 3 v1.82 the progress failed half way with a all purple screen (the green bar on Odin was almost at the beginning of the procedure). I thought to get it into DL mode once more to see if I could succeed but no DL mode anymore, all I get is random dots all over the screen!! and even when it gets connected on COM, ODIN cannot reach it anymore and it fails at Setup Connection. My belief is that my phone is bricked totally, but wanted to see if anybody on XDA has any thoughts for this.
Thanks for the help and time in advance.
Chrs.
Click to expand...
Click to collapse
From my experience with the Galaxy Ace , Kies is a major killer for the phones .
I think that it's fully bricked and cannot be fixed unless you bring it to Samsung .
Forever living in my Galaxy Ace using XDA App
Yes it seems there is no way out of this. I cannot believe how a simple routine upgrade can bring all the hassle!!
I will give these guys a call to see what they say.
I guess I found the cure for it. I plugged the phone into the power and after a while (5 min or so) the screen turned all white (the same as all pink and all purple thing which if one notices can see the very blurry shade of the notification bar on top!). I turned it off and try the volume up and down DL mode method, it turned on in the same all white screen, I started the Odin and voila, it passed the setup connection step (cannot relate the connecting to the power with the resolution I got in any way!!!). I got the stock version back now wanna try to root and clean up the mess.
Chrs,
Related
Hey all i am really new to this and run into a major problem. I rooted my phone with superoneclick and installed a ROM from SGS tools for my samsung captivate. When it would enter into the recovery screen it would not show the usual options but instead a screen of what looked like a pixelated mess. Once the phone started i went to restore to factory settings and now when the phone starts up I see the AT&T logo then it goes to a black screen where it stays there forever. Did i manage to screw up my phone? any help is greatly appreciated.
ok, I finally turned the phone off and left it overnight. The phone does start and work like it should. The only thing is that once you try to go to the recovery mode and the phone does its thing, I am brought to a screen that is half snowy (like the television when you dont get a certain channel) and the other half with lines of red, green, and blue. From here I cannot tell what is going on when I use the volume key to go up or down. Then with a double click of the power button the phone just restarts normally.
I have a Samsung Captivate and I've been having some issues that have gave me some trouble, Yeah I know it says to look up previous cases of the device but I have yet to find Anyone with the same problem and I've been at this for a week now trying to fix this phone.
When I press the power button the AT&T Logo comes on but only stays there for about 8 seconds then turns off it'll stay on if I hold the power button.
First I tried the Odin3 program, I followed all instructions for it. My phone can go into DL mode and my computer can recognize it as a device, I booted up the program and so far I've had no problems during the process the Odin detected my phone and finished the process but when it finishes my phone will boot to the AT&T logo for a couple of seconds then it'll go to the battery stand by screen and ... that's it.
I tried looking on google for anyone who is experiencing the same problem and so far close but not the same and I ran out of ideas...
Can someone please help me out because I really want this phone to work and Yes I am a noob -.-
Ok. So 14 days ago my wife and I both got S6's for Verizon from a local big box store. (yes, 14. Today is the last day I have to take it back.)
We took the OTA to OE2 and I was able to root both phones with PingPong. Everything was fine until yesterday. Her phone wasn't responding when a call was coming in, so she restarted it by holding in the power button. Now, when it boots up it goes to a black screen after showing the initial "Samsung Galaxy S6" screen. Nothing changes. There is a teal/blue pulsing LED that doesn't go away.
I can enter the recovery and wipe cache, factory reset, safemode, etc. I've tried all of those many times. I can enter download mode and use Odin 3.10.6 to reflash OE2 and it says "Pass". After rebooting, it goes to the "Android is upgrading" dialog and goes through and updates about 248 apps, and then changes to read "Starting apps." It won't go past that screen. I left it on that from 10pm last night until 6am this morning with no change. The battery eventually went dead (from 100%). I've tried Odin many times, and it passes every time.
What are my options? When booting, the padlock is unlocked and says "Custom". I'd really like to get rid of that so I can return it to today without problems. When in Download mode, the system status says "custom".
Please help!!
I've also tried using SmartSwitch on the PC, and it doesn't detect the phone.
Update: I'm trying an Emergency Recovery with Smart Switch. It's at 52% right now. I got a serial number from another S6 so it would allow the download/recovery process to start. It's kind of ridiculous you can't get the serial number for your device from anywhere but the settings page on the phone. (Note: not the IMEI, the actual SN). It's not on the box or back of the phone.
Ok, another update. Emergency Recovery didn't work. It finished, and said that it was successful, but didn't fix the issue.
I took the phone back to the place of purchase and they tried about everything that I had already tried. They ended up just replacing the phone. They said that they never saw this issue before.
I have almost an identical issue except I have not roOted or installed any custom ROMs everything is stock . The fingerprint scanner quit working today and said it required a restart, when I restarted the phone I'm experiencing exactly what you are a black screen and a blue pulsing light. In the stock recovery screen I've tried booting to safe mode USB debugging everything except the factory restore yet I think that is my last resort.
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
rexsis13 said:
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please post your question here:
http://forum.xda-developers.com/showthread.php?t=2257421
The experts in that thread will be able to help.
Good luck!
Thread closed.
I just downloaded the update for Cyanogen Mod 13 and I clicked install then my phone powers on (no matter what buttons I press; power, power and volume up and home) it has the Samsung S5 logo and the text "Recovery booting..." (as well as the other warranty text stuff). It then quickly flashes the screen with the Android and cog logo with the text "Installing system update" for the shortest time (making it almost impossible to read the text) it then flashes this screen on and off every 5-10s for the rest of the time. I thought that the screen maybe just a little glitchy but the "update has been running for almost an hour now. How can I fix this problem if my phone doesn't allow me to put it into recovery mode .
So I spent about 3 hours trying to fix this problem trying every combination of buttons to press on boot as well as trying to make my phone detectable or something like that. Let my Mum try fiddling with it (she has no idea what she doing with new tech) some how she managed to press the buttons just right. It went into download mode and I was able to flash it with an update of TWRP using ODIN and it rebooted and started up. If you haven't already try putting it into download mode, I've heard getting the timing right can be tricky when your phone is doing unusual things. Now I'm unsure whether to try updating again but I might try wiping and going back to a stable 12.1.
Mod Edit:
Thread closed as ODIN fixed it