I'm not sure at all what caused this problem. I downloaded Autorec to try and update my recovery, it seems to have worked fine and I can access my recovery fine. After backing everything up with TiBu, and TWRP (EFS because I was told to always have a backup), I rebooted my phone and when I get to the LG logo, it says "Security Error" and reboots infinitely until I power it off. I can still get into recovery and restore but I can't boot into system.
What does this mean? Do I have to restore to stock or is there a way I can repair the partition(s)?
SOLVED: Flashed 39A KDZ
Related
right so i have twrp 2.2.1.4 and made a backup, flashed cm10 (no gapps), tried to boot, nothing but a black screen. so i held the power button and vol down to get into bootloader but idk what to do from there because clicking "recovery mode" sounds like something other than a boot into twrp and fastboot commands aren't working. can someone tell me how to get this working again?
also when i tried restoring a backup via twrp before i wasn't able to boot cm it would just reboot twrp and not restore...
Edit: nvm i fixed it. i thought recovery mode would put it in something similar to dfu mode on ipods but clicked it anyway and got to twrp still can't restore my backup tho...
Edit2: ok now found out that 2.2.1.4 was a bad release. went back to 2.2.1 and all is good
Went to the Play Store, installed ONline Nandroid Backup by Thomas Otero, and ran a CWM online backup. It worked fine.
Went back to the Play Store, installed TWRP manager by Jmz Software, and ran a TWRP standard backup. Rebooted to recovery for the backup, and now the phone is stuck in a boot loop
It boots to:
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
vibrates twice, and starts over.
the only way to stop it is to pull the battery.
Is there a combination of buttons that I can push to get it to at least boot to a recovery screen? I have tried power+home+volume up... no luck.
Nevermind... I did tried booting to download, and just saying cancel, and it booted up fine. I'll be getting rid of that TWRP dowload manager.
I have a d802 . I had cloudy1.3 and twrp 2.7 installed with autorec. I tried to update it using
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(from twrp page, with the latest img file).
But I coudn't access recovery, some error about security. Then I shutdown my phone and then it booted fine into system. I retried to access recovery but nothing.
So I decided to return to autorec, I installed it, I clicked "Flash Recovery" and now my phone doesn't boot in any way.
It show "lg security error" and then shutdown.
I can access download mode. Is there a way to fix my phone without deleting everything?
I'm sure the problem is the recovery, I was messing with it, can I bring my phone back and don't delete my configuration, photos, apps?
Thanks
I'm so happy!
I did it!!!
I managed to boot into recovery with the usual combination of keys (with the method that ask you if you want to format, but then you press power and it boot into recovery).
From there I saved everything using adb pull (Just in case). Then I dirty flashed Cloudy 1.3 and my phone is back !
I hope my experience can help someone
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
So, I did brick my D802 in some way.
After a long history from cloudy g2-g3, rr, cm12, cm13, lineage 14.1, I clicked by mistake on the OTA of the lineage.
I thought I could stop the update once in the recovery, but I got stucked in the recovery bootloop. I got rid of it via recovery terminal, but system didn't boot. I tried reflashing lineage, nothing happened, I tried restoring a cm13 full backup, nothing happened, so I got back in download mode to restock with lollipop kdz (the one I used every time I restocked to change rom). It did not work, and I had to download a different KDZ to get to stock again.
Now, all the methods always used to root + recovery didn't work, so I manually rooted, installed the proper AUTOREC, but it didn't work (as I understand after hours of searching because supersu had updated himself in the meantime).
So I tried to install the TWRP image using flashify, it didn't work and corrupted something in my recovery. So i tried to unroot everything and reinstall the original root + supersu without letting him autoupdate. Not working.
Well, now I can boot and I can get in original lollipop rom, but I have no recovery and download mode appears but doesn't work anymore (once I had 3 COM ports when connected in download mode, now I can see only one; kdz flash does not sense the phone connected). When I try to open recovery I got the error "boot certification verify, secureboot error" in the top left corner of the screen, then a white page opens with the message "critical error" "demigod crash handler", volume up to download mode (that opens but does not work), volume down to reboot.
Now, I am stucked, I cannot find any suggestion of what to do to get the recovery working or to get the download mode working again.
Any help will be highly appreciated.
Thank you very much guys.
Not sure will it help but you may give it a try:
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076