Hi guys, my phone is right borked and I hope someone can help me out. I've been searching forums all day and I find bits and pieces of advice that apply to parts of my situation, but haven’t found a fix yet.
I installed CyanogenMod on my Rogers Samsung G3 a couple months back. Everything has been going smoothly until last night when I installed an update.
The phone rebooted and got stuck on the Samsung splash screen with the blue cyanogen dude. I left it for 30 min and when I got back, it was still the same.
I took the battery out, turned it back on and ended up in the same spot. I took the battery out again, turned it on and left it over night. Same thing this morning.
On advice from this forum I put the phone in recovery mode. I thought I had TWRP, but Clockwork Recovery comes up.
I did a factory reset, and cleared the cache. Rebooted and still the same thing.
I tried to flash the ROM, but it doesn't work. The android dude just lies there, dead. Poor guy.
I plugged it into my computer but even though the computer makes the connection ‘cah-ching’ its not recognized. Through the recovery screen I tried unmounting and mounting everything, and mounting as usb and the computer still won’t pick it up. I uninstalled Kies, and the drivers for the phone and re installed everything. The driver pop up says MTP has failed.
Any suggestions?
Related
Ok so I'm not a noob around here. I'm pretty good with the android stuff, but this one has got me stumped. I have a perfectly working sidekick 4g with B2b 2.5 on here. All of a sudden it forces itself into a repeated reboot. It shows me the white sidekick/samsung screen, and about 3 seconds later reboot into the same thing. And it does this over, and over, and over again. At some point it stops and functions normally, but only for a few minutes, then repeats the process. I've already changed roms, back to glorious overdose. It will even reboot in CWM. The only time it stays stable is when it's in download mode. Another problem there. ODIN doesn't recognize when the sidekick is plugged in through USB. So even if I wanted to ODIN, I can't. I tried booting without my sd card, and my sim card. No avail. and i disabled lagfix, still reboots. I take the battery out, and when I put it back in, it turns itself on just so it can continue restarting. There's nothing stopping this phone. Please help if you can. Thanks for taking the time to read this!
first, enable voodoo. i tried disabling voodoo once and it just kept rebooting. i pulled the battery, put it back in, enabled voodoo, and it booted normally. however, in your case, i would run fix permissions before trying to reboot. to run fix permissions, while in recovery mode go to advanced. select fix permissions, wait for it to say done, hit the back button, and reboot. see if that helps. if not, you may want to ask someone more experienced.
Thanks for your reply. I found out that my windows(8) didn't correctly install my sidekick drivers. tried it on my xp machine and bam, ODIN worked like a charm. Unfortunantly, the problem persisted. So i know it's not a software problem. I contacted samsung yesterday and sent in my phone today. I ODINed back to stock then updated to kj1 through kies. I read up on it a little more and people said it was maybe a loose connection on the phone. I'm still in warranty, so I'll let samsung deal with that.
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
Last night I was using my phone and it rebooted randomly, and when it came back up it got stuck at the AT&T logo. I pulled the battery and restarted several times with no luck. Even left it out overnight and tried again.
I can get the phone into 3e recovery just fine. Will clearing the cache possibly help? What information is on the cache that will be cleared?
I don't have an original charger cable right now, so I can't try download mode. I'm trying to avoid using Odin again, because I would rather not lose the huge amount of new contacts and notes I have in my phone, it would be a major setback.
My phone has also had some issues with a device I/O error, and I haven't been able to back up my phone, so I'm not even sure if download mode would work for me.
Please help!
Edit: As I was about to write that I have had this problem before.... my phone was at the AT&T screen and it magically works again.
InfuseIssues said:
Last night I was using my phone and it rebooted randomly, and when it came back up it got stuck at the AT&T logo. I pulled the battery and restarted several times with no luck. Even left it out overnight and tried again.
I can get the phone into 3e recovery just fine. Will clearing the cache possibly help? What information is on the cache that will be cleared?
I don't have an original charger cable right now, so I can't try download mode. I'm trying to avoid using Odin again, because I would rather not lose the huge amount of new contacts and notes I have in my phone, it would be a major setback.
My phone has also had some issues with a device I/O error, and I haven't been able to back up my phone, so I'm not even sure if download mode would work for me.
Please help!
Edit: As I was about to write that I have had this problem before.... my phone was at the AT&T screen and it magically works again.
Click to expand...
Click to collapse
I'm sorry if your not able to save all your contacts but the only way to stop your phone from flashing samsung over and over again is to use odin. Or the case could be is that your power button is either stuck or messed up.
After months of Samsung not fixing the known issue, I got mine working again today. Here is what I did, hope any with same problem have similar results. I am not an expert or anything, just finally found a way to get my tablet working again.
I downloaded the Kies program from Samsung website to my pc. I went ahead and used the "Lite" version. Once it recognized my tablet, I had it check for updates. I went ahead and installed the update and the progress screen stalled again and then the tablet rebooted again and still had the same problem not powering off.
So here is what I did different this time after the failed update attempt and it worked!!!!!
I went ahead and force closed the Kies program which was still trying to run with ctrl alt del. I then unplugged the tablet from the computer usb and then plugged it back in.
I restarted Kies Lite and it told me the last attempt failed and if I wanted to use recovery method, so I clicked yes.
It then gave some steps to do to get the process started but they were WRONG! Instead , I disconnected the usb cord, then pressed both the power button and the volume up key for about 15 seconds until the tablet rebooted itself into recovery mode. This booted into a recovery screen which gave a warning about loading custom ROM or something but I went ahead and proceeded anyhow by following the on screen instruction.
I then reconnected the usb cord and then the button to get started was highlighted and able to be clicked, so I clicked start.
And to my surprise it actually finally started updating instead of just sitting there hung up.
I let it continue installing and when the tablet rebooted, I disconnected the usb cord and the tablet was on its way to finish updating and installing the 4.2.2 working update with a power button that finally worked again.
This was my experience I wanted to share with others that are as frustrated as I was, just dont blame me if it doesnt work haha.
Update: I was able to successfully fix my inlaws tablet as well this evening with absolutely no issue. He has read about it and also tried various methods posted everywhere but mine was the only way that worked.
Only download you need is the Samsung Kies program, no need looking for outdated links, unzipping, Odin recovery options, etc. This is to get it back to stock Samsung ROM which currently is the 4.2.2.
Please post up your results if you try it and have a minute, Im curious how many others this works for after spending so much time reading, searching and testing diferent methods.
My zte awe got messed up so I energy went into recovery mode and cleared cache. My phone was able to boot up after and worked fine until I restarted the phone a few days later. I tried to boot up the police but it wouldn't go so I did the recovery and cleared cache. During the process the phone froze longer than it should have and was unresponsive. I took the battery out and put it back in. The phone never turned on since. Completely unresponsive. My pc still recognizes it but I don't know what to do. Is this a dead phone or can it be fixed.
P.s. I don't think it's a hardware issues as there was no damage to the phone only software.
Any help would be great. Thanks