Hi all
I'm here to ask you guys about this strange bootloop. This is my brother's phone, fully stock. It was on Lollipop, was never rooted, flashed, and even hard reseted. He was using normally last night, and this morning he woke up to see what time was it and the phone was bootlooping itself.
My first idea was enter in recovery mode and wipe the cache (but then I discovered that LG's stock recovery is very simple...), but I simply can't go into recovery mode, I tried a lot of combinations and nothing happens.
It's strange because is a stock phone, and he has it for like 3 years now. I'm guessing this is a hardware problem.
I made a small video showing the problem:
https://youtu.be/TZ9R5yqlfI8
Any help will be appreciated.
"solved."
The phone's motherboard is dead. My brother now bought an Moto G4 Play.
Related
Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?
Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.
Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/
Hardware problem.
That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??
Guys I was copying movie to my phone using usb cable.
I was copying it to my phone memory as i have not yet put a memory card.
While copying it got stuck at 90%. Then I canceled the copying after which my phone restarted.
When it booted it was very sluggish and i wasn't able go to the menu. So I turn off the phone and switched it on again. This time also it was sluggish so I again turned it off and when I turned on it got stuck at the Motorola logo powered by Android screen.
It is not going any further I have tried many times. I even went to fast boot and tried the recovery and factory option. But nothing happened. It will come back to the boot screen again.
BTW guys my phone bootloader isn't unlocked and it is not rooted.
So the phone is in very much stock. My phone is not yet 1 month old. I have never faced this kind of situation in past.
I have like 500mb of pics in the phone memory which I will like to get back.
Is there any way to fix to phone without voiding the warranty and get the pics and video back.
Any help will be very much appreciated..
aviseknandi said:
Guys I was copying movie to my phone using usb cable.
I was copying it to my phone memory as i have not yet put a memory card.
While copying it got stuck at 90%. Then I canceled the copying after which my phone restarted.
When it booted it was very sluggish and i wasn't able go to the menu. So I turn off the phone and switched it on again. This time also it was sluggish so I again turned it off and when I turned on it got stuck at the Motorola logo powered by Android screen.
It is not going any further I have tried many times. I even went to fast boot and tried the recovery and factory option. But nothing happened. It will come back to the boot screen again.
BTW guys my phone bootloader isn't unlocked and it is not rooted.
So the phone is in very much stock. My phone is not yet 1 month old. I have never faced this kind of situation in past.
I have like 500mb of pics in the phone memory which I will like to get back.
Is there any way to fix to phone without voiding the warranty and get the pics and video back.
Any help will be very much appreciated..
Click to expand...
Click to collapse
I think you could only try to "fastboot boot recovery.img" with a custom recovery out there ( like twrp from adrianom ), but probably it won't work with a locked bootloader
eskamhl said:
I think you could only try to "fastboot boot recovery.img" with a custom recovery out there ( like twrp from adrianom ), but probably it won't work with a locked bootloader
Click to expand...
Click to collapse
And unlocking the bootloader will void the warranty.
So it is of no use
Guys I gave my phone to service center. The at the service center said the reason behind this boot loot might be over night charging, Phone falling from hand. I was confused like how can hardware problem lead to software problem. How is charging related to OS corrupting.
He said that it can also happen but installing corrupt software..
It didn't make any sense.
Can you guys can put some light in the matter...
HI. HAVE NOT FOUND THIS FULLY ADDRESSED. HAVE THIS USED S4 ACTIVE . ONLY BEEN ABLE TO USE IT FOR 4 DAYS.-STOCK 4.4.2 UNROOTED .YESTERDAY IT DRAINED THE BATTERY TOTALLY WHILE CHARGING. GOT A NEW BATTERY AND IT STARTS OVERHEATING SO MUCH IT BECOMES HARD TO HOLD. THEN I WIPED CACHE AND DID A FACTORY RESET AND IT GETS STUCK AT BOOT WHEN I AM ABLE TO TURN IT ON , WHICH IS RARELY, IT NEVER GETS PAST THE BLUE ATT BALL.ALL IT SHOWS IT THE GREY BATTERY. mY PC WILL NOT RECOGNIZE IT, ODIN WILL NOT EITHEIR OBVIOUSLY. ANY KIND SUGGESTIONS??? WOULD LIKE TO THANKS FOR THE HELP
1. writing everything in capslock will not help you to get a reply faster my friend.
2. seems you bought a device with a dirty flash. someone flashed a custom rom like cyanogen, faced these issues, tought he can go back with a easy reflash, but didnt cleared the device by factory reset.
What i would do:
trying to get into recovery mode by holding volume up + power. if there is a recovery system on this device, wipe factory reset the device and flash a new fresh OS onto it.
otherwise you can use it as a paperweight.
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
You didn't mention how you tried to install the stock ROM . Did you use Odin?
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Nabeel mhd said:
my galaxy note 4 (sm-n910t) caught in bootloop . i dont know what caused it. the phone simply restarts upto first bootscreen, ie upto 'samsung galaxy note 4' and then vibrates and then restarts.this process continues upto battery is down or i pull out battery.the phone is not entering to recovery mode but enters to download mode.
i have tried installing stock rom from sammobiles but it won't help.i have also installed custom recovery twrp but that also won't help to enter to recovery mode,
i am trapped pls help..
Click to expand...
Click to collapse
hi OP,
did you find any solution to your problem?
Hello all. I'm also pasting this in the T-mobile thread in case it can be of benefit to someone. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
chrismcnally123 said:
I just fixed mine with the same issue. I was able to boot into recovery and download mode but mostly download mode without bootloop when I had the usb cable plugged in. I used ADB when I could to boot into download mode, but the buttons worked too. Trying to restart the phone only lopped after the Google screen.
I followed several guides here to flash stock with Odin and wipe cache etc but none solved my boot loop issue. almost gave up but there is a video on You Tube that said the battery warping in the cause of the boot loop. The battery, after/during quick charge, may heat up and change shape causing the issue. Today I installed my new battery purchased on amazon and no more issues.
Now I am on stock and have to find a good rom.
If you do decide to flash back to stock there are a lot of good guides. You may find yourself stuck on the T-mobile screen for 15 minutes when booting for the first time but that is ok. If you still boot loop after installing stock and wiping cache I would try the battery.
Click to expand...
Click to collapse
Thanks sir! I have the same issue! it's working now after replace the battery
Hello everyone!
I have a Pixel 4XL, bought it when the phone was released. Phone is fully stock, not rooted or flashed with any custom ROM, the bootloader is also not unlocked.
I pulled my phone out of my pocket yesterday and it was on the google logo loading screen that you usually see when you boot up the phone. I assumed that it restarted itself because it was too hot (it felt sort of hot to the touch). But the phone never rebooted itself, it was stuck in the booting screen forever.
I then tried various ways to restart the phone, through recovery mode etc. However, I couldn't get my phone to boot back up. I have yet to try factory resetting the phone as I do have some files in the phone I really would like to keep. Is there any other way to resolve this without a full device data wipe/reset?
Thank a lot in advance!!
andchiang said:
Hello everyone!
I have a Pixel 4XL, bought it when the phone was released. Phone is fully stock, not rooted or flashed with any custom ROM, the bootloader is also not unlocked.
I pulled my phone out of my pocket yesterday and it was on the google logo loading screen that you usually see when you boot up the phone. I assumed that it restarted itself because it was too hot (it felt sort of hot to the touch). But the phone never rebooted itself, it was stuck in the booting screen forever.
I then tried various ways to restart the phone, through recovery mode etc. However, I couldn't get my phone to boot back up. I have yet to try factory resetting the phone as I do have some files in the phone I really would like to keep. Is there any other way to resolve this without a full device data wipe/reset?
Thank a lot in advance!!
Click to expand...
Click to collapse
You can try rescue mode and using the tool Google has online. https://pixelrepair.withgoogle.com/
Depending on the issue and what the tool has to do it may factory reset it.
Thank you! I will give it a shot!
I was hoping that sideloading the May update OTA would revive my phone but it didn't happen so I had to cut my losses and factory reset the phone. I really hope this never happens again...
As my phone was stock and the software never altered, what would cause a bootloop like mine?
andchiang said:
I was hoping that sideloading the May update OTA would revive my phone but it didn't happen so I had to cut my losses and factory reset the phone. I really hope this never happens again...
As my phone was stock and the software never altered, what would cause a bootloop like mine?
Click to expand...
Click to collapse
A friend had the same issue. It appeared that his power button actually got stuck internally so he tried to press it from lets say different angles. It worked, he saved all his data and was fine.