Hi All, i was hoping to use my old galaxy alpha as a second phone, but , since entering an unlock code from the provider, my phone is constantly restarting after 20-30 seconds. It doesnt restart when i'm in the boot menu, so i'm assuming this is a software issue.
Can i reinstall android (or even an updated version) to fix this?
Related
I was given this Nexus to attempt to fix because it constantly reboots almost as soon as the lockscreen appears. I have tried a factory reset through the recovery and flashing a stock image using the Android Toolkit but the phone still just auto reboots shortly after starting. I am assuming it is having hardware failure somehow? I had no way to check the build number since I cannot access it fast enough and the device did not have USB debugging enabled so I just flashed each stock image I saw for the Verizon Toro with bootloader PRIMELC03 and so far I have not had any luck. The gallery force closes as soon as the system boots but then it will restart right after.
e: At the moment I am going to accept this as some type of hardware failure due to if I do not attempt to interact with the phone it will stay on the phone setup screen but as soon as I touch the screen it'll re-notify me of the Camera and/or Gallery crashing then restart.
ee: The phone has not rebooted for going on 30 minutes since removing the camera and software I'm going to assume that was the cause of the rebooting.
Hi,
yesterday, my phone started randomly freezing for about 10sec, and would then reboot. This happened every few minutes. I let it off, plugged in, all night, and today this was still happening.
I was running the latest PureNexus. I decided to try to clean flash, but couldn't access twrp ( After selecting recovery from the bootloader, the phone would just freeze and reboot ). I then flashed the latest android M factory image via fastboot. The flash went smoothly, but the phone still wouldn't boot ( same issue ). I can't reliably access the recovery ( the stock one ), as the phone reboots when it gets to the android icon with the warning sign ( even though sometimes I can get to the recovery, but can't select anything in the list, as it freezes and reboots ).
I'm running out of ideas, and would like to know if there's anything I can try before contacting LG?
Thanks !
Hey, i think you need to ask lg to replace your phone
Same issues in this thread
Hello!
the issue:
My device s4 mini (serranoltexx) does not boot further than the initial Samsung logo (showing the "normal" warranty kernel in the left top end of the screen), and then turns black. I can't do anything beyond this stage. When I take out the battery and insert it again, the device boots /starts automatically until the samsung sign and turns black again.
the background:
Last year in July, I flashed mys4 mini (serranoltexx) using odin, twrp and one of the latest official lineageOS Roms 14.1 (July 2018), with nano gapps. But since this morning (10. of January 2019), I can't start my device anymore. The latest update, which I did for the ROM was in July. Due to work reasons and since the official maintenance expired, I did not follow any other Lineage updates for my device, e.g. on this website. But I could use my device daily without any problems until this morning, when I started an app (music player) and after a few tones, the music stopped and the device turned black. Since then I could not enter or boot my device properly. I use a 32gb sd card as an integrated storage.
steps already done:
I tried to enter the recovery mode. When switching it on (taking the battery out and back in), I can enter the initial screen of the recovery mode, but after may be 3 to 5 seconds it turns black again. Saying nothing. I intended to flashed fresh using odin and twrp, and then the latest lineageOS ROM versions from your website. But the same sequence happened again: After using the key sequence for entering the download mode, I can enter it and push the volume up button, but then the device turns black again, saying and reacting to nothing. I changed the batteries (I have several), but it did not change anything. And this puzzles me ....
I know that my device updated trwp yesterday - when my device was still working - but I turned it off and I could turn it one this morning functioning well until I used an app.
the question /the request:
Is there any possibility to fix this problem? Could anyone help me on this issue, please. I really like my s4 mini, I do not want throw it away. I would really appreciate any advice which would possibly fix my problems.
Many thanks in advance for your replies and help
Hello, so after I got OTA update this morning (201) my phone has a weird issue.
For few seconds it freezes then locks itself, and asks me to enter my PIN, not even my fingerprint works. It also displays the message that phone needs to be unlocked with PINlike it does after reboot. But it's not a reboot, it's just locking itself after freezing for few seconds.
Anyone got this too?
C432 variant.
And yes, I did a complete hard reset and the issue persists.
Whatever problem fixed with 235 HStool update.
Mods can delete thread.
So, this is more for interest than anything else, but here's the scenario.
A friends 5T did a sudden shutdown. He picked up the phone, unlocked the screen and opened WhatsApp. An error message flashed on the screen - too fast to read - and the phone shut down immediately. He tried to restart, but it was stuck at the boot logo (circle with rotating dots).
We had a go at trying to get it back up again and did the following. I should note that both recovery and fastboot were available, however the bootloader was locked.
1) Booted into recover and sideloaded the latest OnePlus ROM - Stuck at boot logo
2) Got hold of unbrick tool and flashed with latest version (seems to be Android 8.1) - Stuck at boot logo
We were about to give up assuming a hardware issue when on a whim I tried the old unbrick for Android 7. Amazingly the phone booted. I quickly enabled bootloader unlock and unlocked the bootloader. We then flashed TWRP and tried to flash a custom ROM (Bliss in this case) - followed all the instructions to the T and got stuck at the (Bliss) boot logo (very cool boot logo by the way).
We then flashed a rollback version of Android 7 designed for folks coming back from one of the early beta 8 versions. This booted again, although it replaced TWRP as expected. We then sideloaded the latest version of 7 we could find (seems to be 7.11).
So here's the question. The only thing not working on the phone is the Wi-Fi. It does not switch on and shows a MAC address of 02:00:00:00:00:00 which indicates an issue. So I'm assuming something to do with the Wi-Fi has died on the mainboard. However, Bluetooth still works, SIM cards still work. I can use the phone normally with a mobile data.
So, what would stop anything above version 7.11 from booting if just the Wi-Fi is broken? Is there some link to this that was added in Android 8. It would great to update to 8 or 9 and still be able to use the phone, as everything else seems to work.
P.S. I have noticed that the camera takes about 10 seconds for the image to appear after the app opens, then works fine after that. Related maybe?
Anyway, was just wondering if anyone knows the inner workings and can shed some light on this one.