Here are the two posts I made when initially dealing with this issue.
http://forum.xda-developers.com/showpost.php?p=61190258&postcount=5972
http://forum.xda-developers.com/showpost.php?p=61198589&postcount=5984
My G2 remains at the second boot screen indefinitely when running 39A bootloader and a 39A rom. I've tried xdabbeb 3.1.2 and his stock (rooted) G2 lollipop roms multiple times, with no luck.
Quick rundown:
Was on 24A, then to 26A, then to 39A with xdabbeb 3.x rom. Worked perfectly. Did a bonehead move and tried to restore back to 24a backup without modifying bootloader. Resulted in boot certification verify error, couldn't get into recovery etc.. I flashed back to 24a stock kdz using lg flash tool, rooted, etc and got back to working 26a rom. Now I cannot get a 39A rom to get passed the second boot screen (Verizon logo on stock). I follow the process meticulously. Flash 39a, reboot, wipe, flash rom, reboot, aaaand its stuck. I can then boot into recovery, wipe, flash 26a bootloader, 12b bootstack, and flash my 26a rom backup to get a working phone.
Any idea why I can't boot into a 39a rom subsequently after getting the boot certification verify error and having to restore to 100% bone stock? Considering I can successfully boot into a 24a or 26a rom, I'm not sure what to try.
Thanks. I really want to get on lollipop again.
tried a different 39a bumped bootstack and I was able to successfully flash and boot into a lollipop 5.1.1 based rom. consider this solved
Related
Hey guys,
I just flashed from 4.2 Malladus to 4.4 Malladus smoothly. Everything loaded and is buttery smooth now. I attempted to enter Recovery to make a back up but it only left me with a black screen after the LG logo. I can't seem to figure out what happened, I tried to enter TWRP through ROM Manager's boot in recovery option and also the Power off and Restart into Recovery that comes with the ROM installed.
Anyone have any ideas on how I can access my recovery again?
ifizik said:
Hey guys,
I just flashed from 4.2 Malladus to 4.4 Malladus smoothly. Everything loaded and is buttery smooth now. I attempted to enter Recovery to make a back up but it only left me with a black screen after the LG logo. I can't seem to figure out what happened, I tried to enter TWRP through ROM Manager's boot in recovery option and also the Power off and Restart into Recovery that comes with the ROM installed.
Anyone have any ideas on how I can access my recovery again?
Click to expand...
Click to collapse
Did you update your firmware also? Can't directly flash a recovery on 24A. There's some extra steps involved, AutoRec listed in the LG G2 section is the easiest way around that.
I believe I did, TBH I do not know that answer for sure. I merely followed the steps listed in the installation guide for Malladus within this page:
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/edit - that step being 3b, telling me to flash vs980_1xx_to_24a.zip to prep for 4.4. I'm assuming that's the file for the firmware but I could be wrong.
I followed the steps completely and everything booted up beautifully, minus the issue with me having no recovery when attempting trying to make a back-up.
I'll check out the AutoRec suggestion you've given me, thanks.
ifizik said:
I believe I did, TBH I do not know that answer for sure. I merely followed the steps listed in the installation guide for Malladus within this page:
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/edit - that step being 3b, telling me to flash vs980_1xx_to_24a.zip to prep for 4.4. I'm assuming that's the file for the firmware but I could be wrong.
I followed the steps completely and everything booted up beautifully, minus the issue with me having no recovery when attempting trying to make a back-up.
I'll check out the AutoRec suggestion you've given me, thanks.
Click to expand...
Click to collapse
If you were on 11A you needed the vs980_1xx_to_24a_twrp.zip. Meaning you had to have taken the OTA to 12B, not just have flashed the radio. If you were on 11A and didn't flash the right prep zip it would erase recovery. Either way, just download Flashify from the market and let it flash whichever recovery you want. That should work just fine. With either of those prep zips it flashed the JB aboot, and laf. So Flashify will get your recovery back.
So the AutoRec method worked beautifully. I have a recovery once again and was able to make a back-up so i can flash kernels
Thanks for the help.
JRJ442 said:
If you were on 11A you needed the vs980_1xx_to_24a_twrp.zip. Meaning you had to have taken the OTA to 12B, not just have flashed the radio. If you were on 11A and didn't flash the right prep zip it would erase recovery. Either way, just download Flashify from the market and let it flash whichever recovery you want. That should work just fine. With either of those prep zips it flashed the JB aboot, and laf. So Flashify will get your recovery back.
Click to expand...
Click to collapse
If you scroll down on page 2 of the document in the FAQ section it tells you how to install a recovery.
Hello,
I rooted my stock phone (Verizon, 4.4.2, VS98027A, Kernal: 3.4.0-perf) using Stumproot, than installed SuperSU and used Autorec to install TWRP. I succesfully created a Nandroid backup and transferred this to my PC for safekeeping. I also took the opportunity to transfer all pics and backup all my apps, texts, etc. But I'm having an issue where the phone will freeze when I try to knock on (or wake it in general) and boot to the verizon logo and restart.
I planned on flashing a new rom to the phone (I need something super stable like CM) - Would that possible fix the issue? I read somewhere else that this problem is caused by Autorec, but I can I fix it properly?
Thanks for the help, complete noob here.
furry007 said:
Hello,
I rooted my stock phone (Verizon, 4.4.2, VS98027A, Kernal: 3.4.0-perf) using Stumproot, than installed SuperSU and used Autorec to install TWRP. I succesfully created a Nandroid backup and transferred this to my PC for safekeeping. I also took the opportunity to transfer all pics and backup all my apps, texts, etc. But I'm having an issue where the phone will freeze when I try to knock on (or wake it in general) and boot to the verizon logo and restart.
I planned on flashing a new rom to the phone (I need something super stable like CM) - Would that possible fix the issue? I read somewhere else that this problem is caused by Autorec, but I can I fix it properly?
Thanks for the help, complete noob here.
Click to expand...
Click to collapse
Your problem was using AutoRec. I've said it throughout a few threads, and others have stated that AutoRec causes issues on 27A.
You should be using a bumped recovery, not the old 2.7.0.0 recovery found in AutoRec. Try flashing blastagator's latest bumped recovery (Reboot to recovery to make sure thew new recovery loads up first), then the 27A bootstack, and then flash the boot image I posted in one of MicorMods' threads.
I'll make it easy for you:
Recovery (If you can't get the recovery to flash, you will have to adb it manually, or use MicorMod's tool): http://blastagator.ddns.net/twrp/2-8-5-1.php
27A bootstack: http://www.mediafire.com/download/jbswp6k7vwiijvx/bouchigo_VS980-27A_bootstack.zip
MD5: a25e8745be420e7286ed84127496d5d1
Boot image: http://www.mediafire.com/download/xa24h6fln972mz7/Fix_Rooted_Status_LG_G2-VS980-27A_v2.zip
MD5: 29c3c830e3147687db9ba3534fa8b481
Thank you!
So if I understood correctly, transfer the blastagator vs980 recovery and MD5 to my phone. Reboot into recovery, then flash this bumped recovery file.
Then transfer the 27A bootstack and boot image you posted onto my phone. Boot into TWRP that I currently have installed, select these 2 files, and flash the phone correct?
furry007 said:
Thank you!
So if I understood correctly, transfer the blastagator vs980 recovery and MD5 to my phone. Reboot into recovery, then flash this bumped recovery file.
Then transfer the 27A bootstack and boot image you posted onto my phone. Boot into TWRP that I currently have installed, select these 2 files, and flash the phone correct?
Click to expand...
Click to collapse
Just transfer all the files at once to a folder on your phone. Boot into recovery, flash blastagator's recovery, reboot recovery (there's an option in twrp that reboots into recovery without having to leave recovery) to make sure the new recovery loads up. Now proceed to flash the bootstack and boot image files.
Thanks! Will give this a shot and report back
I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?
Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.
Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
numanair said:
I have a moto x 2013 with an unlocked bootloader. I was on 4.4.2 and I decided to take the OTA. After flashing stock 4.4.2 and updating I flashed TWRP and my custom boot animation. It would no longer turn wifi on which I had solved in the past by reflashing stock. I stupidly tried to do this, and realize now that I have the 4.4.4 bootloader with 4.4.2 images. Is there anything I can do? Is there any way to flash 4.4.4?
Edit: I flashed TWRP and copied the ota to the sd card from a otg drive. I then flashed back the stock 4.4.2 recovery and used it to install the ota zip. I do not recommend others try this as I have no idea how safe it is. Avoid getting in this situation to begin with.
Now I need to know if I can try flashing TWRP again and what I did wrong with that last time? Or was it the boot logo/animation?
Click to expand...
Click to collapse
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
coles427 said:
You're fine to flash TWRP. The issues was you re-flashed it before taking the update last time. To update to 4.4.4 you have to do a stock restore to 4.4.2 first then install the update.
Click to expand...
Click to collapse
I am almost certain that I flashed it after taking the update. The update won't flash with anything other than the stock recovery. It was probably user error of some sort when flashing.
I flashed the new 39A Rom. Works great but battery life sucks. As such, I want to restore a 24A ROM that I backed up before flashing the 39A. So I when restoring the 24A backed up ROM, I flash Xdebs 24A bootloader, then restore the 24A ROM. However, I get an insecure boot error when the 24A ROM boots up. I can restore the 39A backup but really want the 24A to restore.
Any suggestions? Is it because I'm on a bumped recovery, TWRP 2.8.5.1 vs a previous version loki'ed recovery? I tried flashing a 2.8.0.1 recovery from my 2.8.5.1 recovery but the flash failed.
Open to suggestions. Thanks.
Is there a chance your 24A rom was not bumped? If that's the case, you will need to flash the individual 12b bootloader (see faq #3 in the Resource thread) after your flash the 24a bootstack. Can't hurt to try either way since 12b works with both loki and bump.
Go back to 12b
h_10 said:
I flashed the new 39A Rom. Works great but battery life sucks. As such, I want to restore a 24A ROM that I backed up before flashing the 39A. So I when restoring the 24A backed up ROM, I flash Xdebs 24A bootloader, then restore the 24A ROM. However, I get an insecure boot error when the 24A ROM boots up. I can restore the 39A backup but really want the 24A to restore.
Any suggestions? Is it because I'm on a bumped recovery, TWRP 2.8.5.1 vs a previous version loki'ed recovery? I tried flashing a 2.8.0.1 recovery from my 2.8.5.1 recovery but the flash failed.
Open to suggestions. Thanks.
Click to expand...
Click to collapse
Go back to 12b.
XDAbbeb has some updated information for the VS980 that I think everyone with the device should know.
http://forum.xda-developers.com/verizon-g2/development/vs980-resources-bootstacks-unofficial-t3050777
I tried loading a cm12 nightly for a vs980. Kept failing so I tried loading a 39A bootstack from xdabbeb. Now I get the boot certification verify secure booting error when it tries to boot. I try to restore a nandroid from before all of this and still get the boot error. I tried flashing a xdabbeb 27a (what I was on before...and matches the nandroid), but still get the boot error.
Any ideas?
Did you tried doing a kdz o tot restore?
I have not. I guess I was hanging on to my old nandriod with too much hope.
Hehehe, try to kdz and then restore with the nandroid, worst that could happen is it wont work.
When you flash a 39a LP rom you have to flash the 12b bootloader from xdabbeb's thread, reboot into recovery, I then flash the bootstack of whatever rom I'm going to flash and I haven't ran into the secure boot error since.