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]
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.
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!
Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
Hi Guys
I used Odin to reflash my Galaxy S10+ dual sim (duos) as it was experiencing some slowness. I used the Singapore firmware as it uses the same "G975FXXU1ASBA" model name.
The process completed successfully but when the phone boots, it gets past the Samsung logo screen and then gets stuck on a blank black screen with "Starting Android..." showing in the middle. I can swipe down from the top to show the toolbar, but it is limited in what I can select from it and the phone doesn't get to the point where the home screen boots.
I'm guessing this could be an app optimization process but after 4 hours, it was still on this screen.
I've tried re-flashing (redownloading the firmware files), clearing the cache and rebooting the phone.
Does anyone have any ideas?
In case you do want to start clean anyway, have you tried doing a reset in the recovery menu (where you are wiping the cache)? This will wipe all data.
I may have to try the full wipe, which is something I wanted to avoid but seems I have no choice.
Hopefully that at least solves the problem.
I have the same problem but I cannot get it to boot into recovery or download mode. I was flashing Magisk at the time. Odin said it worked but now it wont pass the initial stating android... Odin detects the phone but can talk to it. ADB does not even detect the phone. Phone power and reset come on. if i hold both volume the assistant comes on and if i hold bixby the safemode tag appears in the bottom corner but it still wont boot past Starting Android or boot into download mode
I tried to root my device trough odin. Odin said it was succesful, but when i turned on my device it said someehing like 'vertification failed, you have to reset your device'. So i tapped the button 'reset'. Then my phone restarted and its now stuck on a boot loop with the 'erasing' screen. It just goes to a blue screen with the android logo and beneath it it says 'erasing'. Then after a few seconds, it restarts and turns back to the screen again.
I cannot get into recovery mode, because you'd have to do it with the power button, volume and bixby button, but the second i try to do that, it just restarts and starts the loop again. Even when my phone stopped with the bootloop and just shut down, when I hold my power button it just restarts the boot loop... I already let the battery drain but then still, it just happens again.
I can only get into download mode, but thats all. I dont know my build number. I already looked at the box my phone came in when i ordered it, but all I could find was:
- an IMEI code
- an S/N code.
- a long code existing of numnbers only.
None of these codes I think were build numbers, only the S/N code contained letters.
So I dont think i have my build number. I cant get into recovery mode since it just starts the bootloop.
Please help
My phone is a samsung galaxy sm-g950f
I hope my phone isnt bricked and this can be fixed.
hi did you find a fix? I have the same issue