I have a weird issue with my Focus.
Everytime when I update my phone (could be through Cab sender or through seveneighter) or even when i am flashing a custom ROM, after installation when the phone restarts, it takes really long time. The Samsung logo appears and stays on this screen for an extended period of time. Due to this the Cabsender/ seveneighter returns a "timeout" error (fortunately the update would have been successful). But I do not know why does my phone take so long to restart.
The restart does not take so long when you normally reboot the phone.
Can anybody help me in resolving this issue.
Related
Hi,
New phone and new to Windows phone 7. Classic story - the phone has stuck in boot screen, it says only "Samsung Omnia 7" and that's all. I have tried all tips I could find from internet - took the battery out and let it sit, tried to hard reset it -nothing. Actually hard reset button combination seemed not to work - when I turn it on, holding camera and volume down buttons, nothing happens, it shows boot screen and that's all. It do switch to the download mode when I turn it on holding camera and volume up buttons. I tried to reflash it (got the rom files that it came originally), and after restart the situation is the same - boot screen stuck and nothing happens.
I used WP7_downloader version 7.41, Samsung USB drivers v5.02. The weird thing was that older versions of WP7_Downloader did not work - told that flash lock was on. 7.41 seemed to work, it erased and downloaded all areas fine. I don't know if this is normal, but the flashing process itself took about 120 seconds only. I tried alternative ROM (classic I8700XXJK1), the flashing time was slightly different, but nothing changed, after flashing the device restarts and stuck to the boot screen. As I have read the flashing process should took about 10 minutes or so? I waited for about 20 minutes and nothing changed.
Can I switch the device to some debug mode or do something else that could lead me to the reason the device is not booting?
Omnia 7 stuck at boot screen after
I upgraded to Mango last week and i now too am stuck at the "Samsung Omnia 7" boot screen.
The phone seemed to do two updates, the first suceeded no problem. I started the update before going to bed. In the morning it had completed the first and was awaiting my pin code to start the device. All good.
It then prompted about the Mango update. I clicked it and left it for an hour or so. Came back and zune stated it was on the step, "restarting the phone".
The phone was showing "Samsung Omnia 7", i left it for another hour and then came back, no progress.
Nothing i've found on the net up until today has worked for me.
I can enter the format and download modes still.
This is what i've found and tried so far.
1:
answers.microsoft.com/en-us/winphone/forum/wp7-wpdevices/samsung-omnia-7-bricked-stuck-in-boot-loop/76831b31-2c5b-4d3b-8f65-06111e1f3798
(Did a device wipe to factory defaults, and its still stuck at boot screen
2:
support.microsoft.com/kb/2547687
(yes this is an older issue but it looked like it was working until it said something about "flash lock").
Next step is a complete ROM reinstall. But i'd really like to find out precisely which ROM i should try and if Mango is the actual culprit. I'd like to reinstall Mango if possible.
My Omnia 7 was bought secondhand.
I am with Telstra NextG carrier.
After mango update mine is behaving strange too. It shuts down itself randomly and it is stucking at omnia 7 screen. After a few try I am able to open it. But I noticed something, it's shutting down much more while it's connecting to web or PC. Can this be related? Because I couldn't find another reason about that.
Ever since receiving an OTA update a few days ago, my phone was never able to successfully reboot again. Instead, it does exactly this when I turn it on: Samsung logo appears when booting, then the At&t logo with the word "installing..." or "updating..." along with a loading bar at the bottom appears. The loading bar reaches 100%, but then it will say "update failed", and it reboots and the same process happens again. I've let the phone run on it's own for several ours to see if it'll ever snap out of the loop, but it just stays in the same never-ending cycle of constant rebooting and updating. My phone wasn't rooted and worked perfectly fine before the update, so I suspect something went wrong while it was updating. I tried pressing the home, volume, and power buttons in attempt to initiate a recovery boot and do a factory-reset, but nothing happens. And I've tried replacing the battery, SIM card, and micro SD card, but there's still no change. I still am, however, able to set it in ODIN mode, but I'm not sure what to do since I'm not techie/literate. Please help, I don't know how to get my phone properly working again.
I have not rooted or anything yet. I was planning on waiting for lollipop...
So I installed the OTA update. S5 starts up and gets to the lock screen, then after a few seconds it restarts. This happens every time. I have about enough time to put my password in and begin to open an app and it restarts.
Any suggestions on what to do? I've tried booting in safe mode, same issue happens.
hi...
I'm really desperate, my phone is suddenly dying and I have no idea why, I'll tell you from yesterday what has happened:
- I'm playing a stupid game and suddenly the screen goes black. No led, phone doesn't answer any button, nothing. I hold power button, nothing. Remove battery and put again, nothing. After some attempts phone turns on, but just after starting it reboots or stays frozen.
- I decide to change the rom (I had simpl rom), so I do a full wipe and put CM 12. It seems it works, but when I'm in the settings, at the beggining, I don't even have time to put the wifi, it starts rebooting again and/or not responding.
- Desperated, I install via odin the stock firmware from Sam Mobile. It seems it's gonna work, but when the dialog of "Android is upgrading -- Optimazitating app x of XX" it always gets stucked in a number, randomly. I never get to the 230 apps.
- As a last chance, I try Kies to install factory firmware. The same as before happens, but now it's only 17 the number of apps it tries to optimize.
These last 2 times, of course, I enter recovery from time to time (now the default one) and wipe cache partition.
My phone is agonizing, what the f is happening? Does anybody know what could happen?
Please help...
I have a stock moto x play whose hardware sku is XT1564. It's on android ver 5.1.1 and system version is 23.21.25.lux_lra.en.US
I have not performed any soft mods or alterations, be it root or bl unlocking.
The only thing that I would think is different than normal is that the phone is encrypted, so it asks for password whenever it boots up.
I got a notification to update to 24.74.5.en.US a few days ago and decided to try doing it today.
It downloads the update fine and when I press on the notification for it to start the update process where it says it needs to perform a reboot to update it goes into a "phone will reboot in 10 seconds" screen and when countdown finished it shows the "shutting down..." popup that appreas when you try to shutdown the phone.
Then the phone stays with that popup until it finally shutsdown like 4 minutes later on what appears to be a hard shutdown because it doesn't reboot. I have to manually power it on and then the phone starts up normally asks me for my password and about a minute after android fully loads the phone tries to shutdown again without any input. And then it just keeps doing that until I boot the phone into fastboot and try to get it to bootloader, where it shows the dead android logo with a red yield sign and promptly shutsdown. Then when I start the phone normally it shows an "update unsuccessful" screen.
Anyone have any idea what might be the problem?
I've been thinking it might be the encryption but IDK. Also I've checked the thread with the firmware versions and couldn't find mine there. Is there a way I could dump mine for backup in case I **** something up trying to get OTA to work.(without unlocking bootloader and rooting, of course)
Now the update has stopped appearing and I can't get it to recognize there being an update for this device.
Fudge!