This question may or may not have come up before but I couldn't find anything specific to my problem. Basically I was running Cognition on my Captivate before trying to restore a backup using Clockworkmod. Everything seems to go fine, my phone restarts and I see the AT&T logo but after that it just hangs on the Designgears screen. I tried wipe data/factory reset but it still gets stuck on that screen. What are my options now?
Related
So the past 2 days I've had an interesting problem, with even more interesting results.
Both mornings I've tried to use my GPS and it just hangs on trying to connect to it. The GPS says it's on, and I can toggle it off and back on again but it never finds any sats.
Yesterday I reboot the phone and it takes a while to boot the phone back up (most like the first time you boot after a fresh install), and when the phone came back online the GPS worked but all my bluetooth pairings were gone.
Today I have the same GPS problem so I reboot again, and again it takes a while to boot and so far I still have my bluetooth pairings, but I've been unable to connect to the devices, all my sound settings are back to the defaults, when I hold down the power button now the only option I have is Power Off, nothing else, when my screen times out and I hit power to bring it back on it goes right back to wherever I was, I don't see the lock screen anymore. And to top it all off my home button and my search button do not work.
What a mess, this phone is getting worse by the day, I'm actually starting to regret the purchase. I guess it's time to call it in and see what they say.
Edit: Forgot to add all my SMS messages were deleted as well.
Rooted? Have you done anything to it? That's definitely not normal but I guess you know that
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
gohawks1 said:
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
Click to expand...
Click to collapse
I would guess it's not the phone but the CWM made the mess. You probably want to try factory reset.
My Bluetooth settings and profiles randomly appear and disappear and I'm bone stock.
Well, factory reset got all my buttons working again, and my screen locks again. Since I'm back to stock now and have to re-setup everything now I think I'll go try out the Eaglesblood ROM and see how that goes.
So out of nowhere my Incredible started rebooting on a loop. I have the MIUI installed on it and has always worked fine, but now it won't boot.
I plugged the phone into my comp and it won't show up in "my computer" either.
What do you advise I do?
I went to bootloader and tried factory reset on the phone and that won't work either...just keeps looping the boot screen.
anyone know?
So you can still get to the factory reset? After doing this, does it remain in the recovery screen long enough to reflash? Try using your old NANDroid backup and reflashing. Hopefully this will work.
My friend has a Captivate. He lost all his google apps, android market, gmail, etc. He flashed gapps.zip from his recovery and now his phone is not working right. When he flashed a new rom to his phone, and it brought up the welcome screen it shows it for about 2 seconds and then reboots. He is also almost unable to access the recovery becuase of this, but even when he finally was able to access it and wipe everything, dalvik, cache, data/system, it still has issues. Nothing is fixing the issues from the gapps.zip. He was wondering if there is a way to wipe his entire phone from a update.zip file. Any help would be appreciated. Thank you in advance.
Please note that even when he wipes everything in recovery and flashes a new ROM, it still reboot on the welcome screen and he is unable to resolve this issue.
Ok, so he has now wiped all cache and system files, now instead of showing teh galaxy S logo with the cyanogen logo underneath, it shows just the AT&T screen, but it will not go any furhter, it just sits there. He says that because he is now unable toget into android he cannot access the recovery and the volume up/down is not responding. Is his phone Bricked?
Have you used Odin 1-click to revert back to stock?
had my friend use the Odin 1 click and he said it still did not work. He cannot get the volume up/down trick to work, when before all this it worked just fine. I am going to guess that the only thing he could try is the jig method. He swaers that Odin3 is not doing anything
I'm trying to remove apps that's on this phone (GT-S7500) because some of the apps always force close and not working. Firstly, I tried uninstall the apps one by one, all went good until I rebooted the device, all of the apps are back again. Second, went to privacy>erase everything including SD card content, device rebooted and went straight to recovery. It was weird because normally it will reboot itself straight to home screen. So I select the option factory reset/wipe data, after that wipe cache partition and reboot. Device does not reboot but turned off completely (weird again) Turned it back on, and only saw that none of the apps were removed. Even the wallpaper are still the same. Next thing I do is manually boot into recovery menu and factory reset again, still the same thing, (device turned off without rebooting itself, turned it back on and everything was still the same) after few tries again, I finally decided to flash a stock rom with ODIN. Flashing was successful ODIN shows PASS, waiting device reboot but it shut off completely again. turned it back on, but nothing changes. wallpaper are still the same and every single downloaded apps were still there. Went to settings> about device only to found that it wasn't the same rom that I've flashed earlier using ODIN.(flashed 2-3 times again, results still the same) Very confused right now, suspected that the internal SD card was corrupted/damaged. Does anyone experiencing such thing on your galaxy ace plus? searched on xda forums and found that this issue was also happening on few other devices. This is not my phone, just helping a customer. Thank You.
After flashing stock rom
Go to recovery (stock of course)
Wipe data/factory reset
Wipe cache
Reboot
Sent from my Gt-S7500
Earlier today, I got an error upon starting up my Samsung Galaxy S5 (T-Mobile) that says "Unfortunately, System UI has stopped." My background has been turned to black and none of the buttons work properly. The phone IS rooted (and has been for about a week), but runs on stock OS (5.0 Lollipop) and stock recovery. I have never flashed a rom on this phone. I already tried restoring from a Titanium Backup I made yesterday before this error ever showed up, but it did nothing. Perhaps it's relevant that this error first happened after I booted the phone in recovery mode (to see what stock recovery looked like), then selected "reboot phone." I also already tried wiping the cache partition, wiping the System UI cache, and rebooting is Safe Mode. None of these worked. I thought unrooting the phone might help, but I accidentally uninstalled SuperSU without removing the root. With the System UI down, I can't install any apps at all, such as SuperSU again or a file explorer that would allow me to remove the "su" folder in /system/bin/. Now I have no way of unrooting, short of wiping the phone. I DO NOT want to do that. How do I get my phone back to normal?
--EDIT-- I finally gave in and did the factory reset. I rooted it again using the same method as before (in order to use Titanium Backup), and just to see what would happen I went to recovery mode. Sure enough, I was greeted with the same error as before. I had already rebooted the phone normally multiple times before trying to use recovery mode, so I have no doubt that the stock recovery mode is the cause of these issues.
Signal2Noise said:
Personally, I don't like Titanium Backup. I seem to be in the minority with that opinion, but it's given me issues in the past. Try flashing a non-stock recovery like TWRP for your S5 and either wiping your phone or wiping and flashing another ROM.
Samsung phones seem to dislike rooted users for some reason
Click to expand...
Click to collapse
Too late, I already wiped the phone. I re-rooted using Chainfire's auto-root, then flashed CWM so that stock recovery doesn't screw me over again. Before restoring from the backup, I booted into CWM recovery and restarted the phone. No error. I hope it stays that way, this whole thing is a huge hassle. There really needs to be a disclaimer with Chainfire's auto-root telling people to get rid of stock recovery!
Hi there
You'd be best served asking for help from the experts who own your device, here:
T-Mobile Galaxy S 5 Q&A, Help & Troubleshooting
Good luck