I have the AT&T variant (D800), and got a popup that a software update from AT&T was available, so I tried to install it. The phone was rooted, and I think I had the stock recovery. I tried to flash CWM using ROM Manager from the Play Store, but everytime I tried to boot into recovery I got the "Error: boot certification error" on the LG logo screen.
So I tried to get the software update, which turned the phone off. It didn't boot up for like half an hour, so I tried to turn it on. I got the "Boot certification error," and then the phone went to the black screen. If I shut down by holding the power button and then turn it on again, same thing happens. Before, doing this would have booted the phone into the OS. Now it just repeats the error. What can I do? I'm getting it warrantied tomorrow, but if it's possible I'd like to avoid it.
Related
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
The_mamba said:
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
Click to expand...
Click to collapse
Pretty common prob plug it in to the wall charge see if it boots sometimes it still wont but most of the time it will the battery quality on the g3 is crap they last at most a year with a few exceptions i would first order a battery.
I was in snapchat when all of a sudden my nexus 5x totally froze and rebooted (which is normal considering how much snapchat sucks.)
I saw the warning about my bootloader being unlocked which was normal and it went to the Google screen, where it sat for about 5 minutes. Normally in every previous bootloop I've had in the past, the boot animation just loops forever and ever. I force shut it off and tried booting it up again and this time on the Google screen the phone totally shut off and restarted showing me the warning about my bootloader. I tried the recovery, but got the same results. So, I went home and plugged it in thinking maybe that would help but it still was shutting off and rebooting. It never got to the boot animation. I had all the adb and fastboot drivers so I just decided to flash the factory image. It flashed fine, and sadly the problem was still there. I'm so stuck, I can't get into the recovery to do anything and there's only so much that you can do over fastboot. I've found that if I press the power button every couple seconds while the Google screen is still showing and it doesn't reboot but the Google logo won't leave for the boot animation.
Seriously guys, please just give me any of your ideas.
My Karbonn Sparkle V appears to have bricked itself, I don't know why, I don't know how to fix it, and I don't have the money or time to replace it. I turned it off when I was going to a job interview, prior to which it was working fine. Afterwards I tried to turn it back on, and for the last 12 hours I've been fighting to get it working again with no success.
I can get into recovery mode, but nothing more. If allowed to try a normal boot, then it will either stay on the "Karbonn Smart" logo screen forever and ever amen, or it will APPEAR to boot, but once it reaches the lock screen it dies on its arse. The best-case is that the lock screen will stay up for about 3 seconds, then the screen will go black for another 3 seconds, and then we go back to the lock screen and the process repeats. OR, the lock screen comes up, 3 seconds, and then we go back to the bouncing dots loading screen forever and ever amen.
I tried a hard wipe from recovery mode - it's made absolutely no difference.
This is a stock phone which has only ever received the OTA updates; I've never rooted it, I don't have a custom recovery installed, and I've never used ADB before today.
I've downloaded a number of "stock ROMs" for this phone, but none of them actually work for me; it doesn't seem to matter whether I try to install them through Recovery mode\Apply update from ADB, or put them on the SD card and try "Apply update from SD card". For most of them, I get the error "failed to verify whole-file signature" and it won't install; I tried to install the stock file from https://forum.xda-developers.com/crossdevice-dev/android-one-general/ota-links-t3287707 but that doesn't get me much further; The error becomes
"Package expects build thumbprint of 6.0.1/MMB290/2459718:user/release-keys or 6.0.1/MMB29K/2419427:user/release-keys; the device has 6.0.1/MOB31E/3142026:user/release-keys"
Click to expand...
Click to collapse
I have pretty much no idea what I'm doing here; Please help.
My father-in-law's S6 was rebooting right after the menu screen came up. After trying numerous things which wouldn't work (still had varying boot loops) like getting into the recovery mode and doing a factory wipe, I decided to use Odin and flash the base stock Android nougat on this (it had the one verizon security patch after that, so should be no issue doing this).
That went okay and it rebooted and got all the way to "Android is starting" which you see after a firmware upgrade. But I didn't realize the battery had run down through all this so it died at this stage. So it was taking a charge now, so let it charge overnight and give it another run.
Got up today, tried to start it...back to the boot loop. So I figured I'd flash stock again with Odin (can always get back to that mode).
It completes successfully and then after the reboot at about 32% jumps to "erasing" and then the boot loop again.
Got into recovery mode once and wiped cache (pointless at this point, but whatever) and did factory reset there, then boot to bootloader. Got all the way to the verizon screen...and then boot loop again.
Is this phone just done? The only thing I can consistently get to is Odin mode. I tried the stock reflash a couple more times and keep ending up in a boot loop and it doesn't even get past the "custom" screen now. And I can't even actually get it to shutdown for that matter. I can get to the battery pull mode but if I try to power off from there, I just get the black screen with the blue light.
And, to make matters even worse, now on restart, it brings up the blue system update screen for a second, then jumps over to the no command screen, sits there for a second, then reboots again. I think I've somehow managed to even blow the recovery menu but this has all been stock and never had any custom firmware or root.
Any help/suggestions would be greatly appreciated!
I unrooted my phone through Magisk Manager to get the Android 10 update, and I guess I missed a step. Because when my phone rebooted, it comes up with the "No Command" screen after showing the unlocked bootloader warning.
I am able to enter the recovery mode and all of those settings, but my phone wont boot normally. It doesn't even show the Motorola "M". If I leave it on for a bit, it will switch between the unlocked bootloader warning and the no command screen. I've already tried a factory reset but that does nothing.
Am I stuck with a broken phone, or is there another hope? I'll do my best to provide more info if needed. Please help!
Randomsamm said:
I unrooted my phone through Magisk Manager to get the Android 10 update, and I guess I missed a step. Because when my phone rebooted, it comes up with the "No Command" screen after showing the unlocked bootloader warning.
I am able to enter the recovery mode and all of those settings, but my phone wont boot normally. It doesn't even show the Motorola "M". If I leave it on for a bit, it will switch between the unlocked bootloader warning and the no command screen. I've already tried a factory reset but that does nothing.
Am I stuck with a broken phone, or is there another hope? I'll do my best to provide more info if needed. Please help!
Click to expand...
Click to collapse
What recovery u using I would look for orange fox and fastboot into that there is more things u can do if you don't want to save any thing I would reflash using orange fox recovery the rom u want I would use bliss or havoc I'm on now supper stable everything works and it's Android 10