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.
I am stuck in an installation loop that started while updating to KitKat.
I was happy with my LG G2 (T-mobile, D801G), but wanted to use root apps. So, I rooted and installed TWRP, but did not flash a custom rom.
Tuesday when I woke up there was a message saying I could download KitKat. After installing my last system update I lost root, so just had to unroot and re-root – took me about 15 minutes. So, I decided to go ahead and install KitKat.
It downloaded and began to install, but got stuck in a loop. The LG logo flashes for 5 seconds, the little droid pops up with his stomach spinning and the message “Installing system updates” but shows for only about ½-second. Then the screen goes black for 2 seconds and it starts again.
I can get it into the factory reset screen, but when I say yes-yes, it puts up the message :
Error: Boot certification verify
341120
341170
341220 Secure booting error!
341270 Cause: boot certification verify
341320
341370
(the nunbers are different each time, but always 6 numbers in increments of 50)
Then it sits in a black, but not quite off screen until I hold down the power button to turn it off. When I turn it back on, it shows the logo, then the droid showing the message ‘Erasing…’ for a full second, then switches to the ½-second ‘installing system updates’ loop.
It will go into download mode. When I connect it to the LG flash tool ‘Up Test’ it says all firmware is up-to-date.
I tried this: http://forum.xda-developers.com/showthread.php?t=2582142 but I couldn’t get Ubuntu 12.04 to install gdisk. Then I noticed that
ls /dev/sd*
returned the same values whether my phone was plugged in in download mode or unplugged completely. The values were
/dev/sda, /dev/sda1, /dev/sda2, /dev/sda3, /dev/sda4.
I tried the next step anyway
gdisk -l /dev/sdb
and got the error saying gdisk was not found, but I could install it with… etc. I tried to install it, but it wouldn’t work.
This is the second phone I’ve rooted – I had my HTC Sensation rooted for years, and flashed many ROMs. I hadn’t played much with the G2 because I liked it just the way it was – but had to have some rooted apps. I also have an HP Touchpad running Cyanogenmod. My experience with Linux is limited. So I’m just one step up from a noob.
Any advice would be appreciated! I bought a go phone so that I can take my time and fix my G2 right. :-/
I have a Note 4 and I was very satisfied with the performance until a few weeks ago, an upgrade to Android 6.0.1 was downloaded and applied.
It seems the update failed and despite I'm now in Android 6.0.1, the phone is working very erratic. Sometimes it freezes for a while (10 seconds, 30, 1 minute, 2 minutes) and then just continues as normal (when it freezes for more than a minute, it goes directly to lock screen ). Sometimes it says some app or system process (touchwiz and the like) has failed and sometimes it simply reboots without any reason. I have restarted it in secure mode but there is no difference.
I have uninstalled all downloaded apps but there is no difference. I have reset it to factory defaults but keeps failing.
I have downloaded latest 6.0.1 Firmware from Sammobile and flashed it with Odin but the fail is still there.
One thing I have noticed is when I start in recovery mode (power+home+vol up), instead of the recovery menu, the android robot appears and the text installing update. It goes for a while, then crashes (robot with red triangle) and then the recovery menu appears. This happens every time I start in recovery mode so it looks like there is some update that was applied (since I have 6.0.1 instead of 5.x) but only partially.
Any help?
is there a way to revert it back to Lollipop?
Hi!
Same thing happened to me. Connect to a computer and use Samsung Smart Switch to do an emergency recovery.
But the phone will be erased.
After that, my Note 4 got even better than before!
Good luck!
Tried Emergency Recovery but phone doesn't show up in the list, so I tried Update Firmware. It told me the firmware I have would be replaced by current version (The SAME version) but I went ahead anyway. Firmware was downloaded from internet, phone booted in Download mode and Smart Switch copied the firmware to the phone, then restarted, installing... Error Message: "No Command", nothing else.
I removed battery, rebooted and error message appeared telling there was a problem with firmware update and I would need to use emergency recovery from Kies (I understand I have to use Smart Switch, no Kies). So I connected it again to Kies and opened Emergency Recovery but once again, it doesn't appear in the list. So trying again with Firmware update. If this doesn't work, I'm afraid I have a very expensive paperweight
Failed again. At 25% update, Download screen showed:
ODIN: flash write failure
A window in Smart Switch tells me something went wrong and offers me Emergency Recovery. It also tells me I have to write a recovery code if using another PC. The recovery code is blank. not a good signal.
Again, Emergency Recovery is showing nothing in the list of devices
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
jedikalimero said:
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
Click to expand...
Click to collapse
please keep posting your observations, i am on the verge of trying flashing 5.1.1 myself.
would be great to know if this resolves our issues.
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
I went to the repair service. The guy there didn't know how to fix it an told me to send it to Madrid for repair. But I haven't sent it yet for two reasons. The phone is still under warranty (as ANY OTHER Note 4 bought in the EU), but first, he told me it would take 25 days to repair (this is Spain, you know. In UK it would take 3 days) and second, my front glass cracked so I had to take it to a repair shop to replace just the glass for 30 euros instead of the 200 euros it would have costed to replace the whole (and totally functional) screen officially. So I'm afraid they would find out the glass was replaced and take this as an excuse to void my warranty. In older models you could replace the glass and nobody would notice it, but in the Note 4 you have to break a copper heat dissipation foil that lies between the back of the screen and the metal frame in order to disassemble the phone.
jedikalimero said:
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
Click to expand...
Click to collapse
so sad!
My wife's S7 is only booting to the verizon logo (with the little colored circles moving below). Long story short:
1) I was trying to back up her pictures to my PC and all of them disappeared from her phone when I drug them to my PC (6 months of pics). Not sure how that happened.
2) In my panic, I downloaded an application called DR. Fone which professed to be able to get the pics back.
3) After installing the app and connecting the phone, I started the recovery process, which rebooted the phone to a "downloading" screen and then booted to the Verizon logo I have been trapped on ever since.
I have tried powering off, rebooting, clearing the cache from recovery to no avail. I have a feeling that this app altered the bootloader or firmware and now I'm stuck.
Booting into recovery ends up with a "No Command" error. I can get into the Android Recovery menu from there ... but I don't want to wipe it just yet.
Any ideas what could be keeping me stuck on that screen?
Pleeeeaaaaasseee help!
Install this rom, connect to your computer with the verizon upgrade assistant running after the rom is installed. The verizon upgrade assistant should see the phone and you can update it from there.
So today i bought my LG G6.
There was a software update (i thing Oreo update) i installed it and when i got to the secure screen on the boot.
I type my PIN ,which was valid and my phone now is stuck on the secure loading screen.
At first i thought it was just going to take some time but after 25 minutes of waiting this started to worry me.
The phone is still on loop and when i use the Power Button and the Vol down the phone restarts but the same thing happens.
I tried everything from restarting it , to hard resetting (which doesn't want to work, the bootloader menu doesn't even show up with all the steps completed correctly) to throwing it on the ground.
(PHONE IS NOT ROOTED)
EDIT:I MANAGED TO SOLVE THE ISSUE BUT NOW IM STUCK AT THE PROVIDERS SCREEN WHICH IS (TIM) AND I CANNOT DO ANYTHING OTHER THAN SOFT RESTART
Regards,
Try put the phone into download mode and use LG bridge to reflash stock [Use the "Update error recovery" to reflash]