So I picked up the lg vs980 from Best Buy on Monday. Brand new,$199.00 +tax which is a great price for this phone with no contract. In my impatience to root I did the root method and custom recovery that I used when I had the AT&T G2 . I then attempted to get the Lollipop OTA update. When booting my phone now I get the LG logo in the middle of the screen and in the top left I get
ERROR : boot certification verify
[922380]----------------------------
[922430]
[922480] Secure booting Error!
[922530] Cause: boot certification verify
[922580]
[922630]---------------------------
I can't get into download or any other mode. I can get into the factory reset screen and it says ROOTED in the top left.
When I select yes,push the power button and select start and push the power button instead of getting TWRP recovery or factory reset I get the above screen for 3 seconds and my phone goes black. Am I screwed because of my impatience? Any help and criticism (which is deserved) would be appreciated
ScottsoNJ said:
So I picked up the lg vs980 from Best Buy on Monday. Brand new,$199.00 +tax which is a great price for this phone with no contract. In my impatience to root I did the root method and custom recovery that I used when I had the AT&T G2 . I then attempted to get the Lollipop OTA update. When booting my phone now I get the LG logo in the middle of the screen and in the top left I get
ERROR : boot certification verify
[922380]----------------------------
[922430]
[922480] Secure booting Error!
[922530] Cause: boot certification verify
[922580]
[922630]---------------------------
I can't get into download or any other mode. I can get into the factory reset screen and it says ROOTED in the top left.
When I select yes,push the power button and select start and push the power button instead of getting TWRP recovery or factory reset I get the above screen for 3 seconds and my phone goes black. Am I screwed because of my impatience? Any help and criticism (which is deserved) would be appreciated
Click to expand...
Click to collapse
Try this first: http://forum.xda-developers.com/showthread.php?t=2451696
Try this if the first suggestion does not work: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Instead of screwing around and maybe making things worse I am sending it to LG and let them fix it. Thank You for your help
Related
So today I set about unlocking the bootloader and rooting my Moto X 2014 Pure Edition XT1095.
Unlocking the bootloader went just fine. Then I went to root it. I booted the pure2014sb.img but it didn't work. The phone would just hang on the Motorola logo. Then I read somebody later said that doesn't work on lollipop, so I booted the CF-Auto-Root-victara-victaratmo-xt1095.img instead. That showed me the rooting status page thing before it rebooted, and then rebooted again, but when it fired up after that it was still hanging on the Motorola logo.
Then I attempted this http://forum.xda-developers.com/showthread.php?p=56928477#post56928477
Now the phone will not even hang on the logo, it gets to the animated moto logo part and then turns off half way through. I cannot get back into fastboot state either. It just doesn't respond to power + vol down at all.
EDIT: Actually scratch the not being able to get into fastboot state thing. I just had to hold the buttons down for way longer than normal. I just kept holding them until it showed something. It ended up being like 15 seconds instead of 3-4 like usual.
Help!
slak? said:
So today I set about unlocking the bootloader and rooting my Moto X 2014 Pure Edition XT1095.
Unlocking the bootloader went just fine. Then I went to root it. I booted the pure2014sb.img but it didn't work. The phone would just hang on the Motorola logo. Then I read somebody later said that doesn't work on lollipop, so I booted the CF-Auto-Root-victara-victaratmo-xt1095.img instead. That showed me the rooting status page thing before it rebooted, and then rebooted again, but when it fired up after that it was still hanging on the Motorola logo.
Then I attempted this http://forum.xda-developers.com/showthread.php?p=56928477#post56928477
Now the phone will not even hang on the logo, it gets to the animated moto logo part and then turns off half way through. I cannot get back into fastboot state either. It just doesn't respond to power + vol down at all.
EDIT: Actually scratch the not being able to get into fastboot state thing. I just had to hold the buttons down for way longer than normal. I just kept holding them until it showed something. It ended up being like 15 seconds instead of 3-4 like usual.
Help!
Click to expand...
Click to collapse
Same happened to me early this morning when I was trying to install 5.0.2
You have to flash any firmware you want just avoid to flash the modem and there ate several post here in the general section
Just remember. Don't flash the modem unless is the same firmware you have or else you will lose signal.
Regards
Thanks for the input. I used the instructions in this thread to get my phone back to working condition:
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
I was unable to get it to pick up the 4.4.4 to 5.0 update zip in recovery mode, so I just used the regular OTA update to do it. After that I booted the CF-Auto-Root-victara-victaratmo-xt1095.img and it worked!
slak? said:
Thanks for the input. I used the instructions in this thread to get my phone back to working condition:
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
I was unable to get it to pick up the 4.4.4 to 5.0 update zip in recovery mode, so I just used the regular OTA update to do it. After that I booted the CF-Auto-Root-victara-victaratmo-xt1095.img and it worked!
Click to expand...
Click to collapse
Great! Glad it helps
Enjoy the lollipop Sweet my friend.
My rooted LG G2 got bricked after my little bro accepted an OTA update.
Here's whats happening:
- Tuning on the phone takes me to the LG logo
- On the top left corner I get "Secure Boot Error"
- My screen then goes black, but is still on.
- I can get to the factory reset menu, but attempting a reset just takes me back to a black screen
- I have no custom recovery (TWRP or anything else)
- Phone shows up on my computer as local disk :C - :R.
- In device manager it shows up as QHSUSB_BULK with no drivers at all.
- I can't get into download mode
Someone please help!
I would like to ask some few solutions from expert people here. My phone was stuck in Boot loop for no apparent reason and cause. So, here's the chronology: I was playing Vainglory and it was still drafting heroes in ranked match. During that time, the phone just got freeze and unresponsive for several seconds. Then, it restarts and there we go. It starts boot loop cycle. I don't know what causes it.
How do I solve this? I need help, please. The Phone is Unlocked Bootloader and it is in root condition. As for the version, it was using 4.88B. I would require step by step detail in solving this boot loop before i decided to go to service center and have it fixed which is possible to remove Unlocked bootloader and root which I do not want that to happen.
Thank you so much in advance.
PS: After shutting it off for 30 min, I tried turning it back on. It does bring me to the home screen but then few seconds, it reboots again and causes boot loop. Nevertheless the case, once Powered by android logo came, I won't be able to bypass that.
Try to hold Volume up and Power while launching the phone - it will bring you into the recovery mode of android. From there you should wipe your phone data - sorry there's no viable solution for you, if it's a software bootloop then it should help you bring the phone to factory state and get rid of issues.
KonikoO said:
Try to hold Volume up and Power while launching the phone - it will bring you into the recovery mode of android. From there you should wipe your phone data - sorry there's no viable solution for you, if it's a software bootloop then it should help you bring the phone to factory state and get rid of issues.
Click to expand...
Click to collapse
Sir, It doesn't show the recovery mode. It is like no recovery exist. It just shows Powered by android logo and then keeps restarting.
did you solve your issue? trying to reboot?
How did it happen?
and How did it solved? Did your phone start then?
I think from TWRP you choose to boot different slot.
So I think you have different Kernel-boot to another system-version
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
ibphantom said:
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
Click to expand...
Click to collapse
Make sure you are using the latest adb/fastboot binaries (April, 2020). Flash the stock boot.img from the same guide. You will be unrooted but will be able to boot into System. Now read up on how to patch your own boot.img, it really is very simple. Personally I do not depend on, wait on, or use OTA's. The full image is available the first Monday of every month, and I extract/patch the boot.img from it. The whole operation including rooting takes just a few minutes. It's just one extra step. Once you get the pattern down it can be done very quickly, consistently and you're not depending on someone else's files. If you are bound and determined to use this method, you should seek out more guidance in the tutorial thread itself. Good luck. :good: