Hello, I used Autorec to install TWRP on my Lg g3 .
I booted successfully into TWRP two nights ago. I am thinking about installing a custom rom onto the device, however I cannot boot into twrp anymore. I still have root, I believe.
I am running latest stock, 23c, lollipop.
eddytheyeti2 said:
Hello, I used Autorec to install TWRP on my Lg g3 .
I booted successfully into TWRP two nights ago. I am thinking about installing a custom rom onto the device, however I cannot boot into twrp anymore. I still have root, I believe.
I am running latest stock, 23c, lollipop.
Click to expand...
Click to collapse
just flash the recovery back on with n app or DD code, there must be something else going on, because the answer to your question is obvious.
use this
And learn the key combination to get into recovery
Related
So i decided to flash the old ZV4 update to the g3 and received the OTA update which updated the g3 to lollipop. I have successfully rooted it but want to install TWRP recovery so that i may flash CM12. How can i get to installing TWRP? Please guide me because i am stuck and need assistance. Thank you!
WoodenDiamond71 said:
So i decided to flash the old ZV4 update to the g3 and received the OTA update which updated the g3 to lollipop. I have successfully rooted it but want to install TWRP recovery so that i may flash CM12. How can i get to installing TWRP? Please guide me because i am stuck and need assistance. Thank you!
Click to expand...
Click to collapse
This is your only option. http://forum.xda-developers.com/showthread.php?p=55225699 It has all the info and links you'll need.
engine95 said:
This is your only option. http://forum.xda-developers.com/showthread.php?p=55225699 It has all the info and links you'll need.
Click to expand...
Click to collapse
I followed all the steps, but the phone screen flashes recovery loading then shows lg boot logo with secure boot failure at the top left corner. What should i do now?
WoodenDiamond71 said:
I followed all the steps, but the phone screen flashes recovery loading then shows lg boot logo with secure boot failure at the top left corner. What should i do now?
Click to expand...
Click to collapse
While you might be able to root ZV8, you can't install recovery from the OTA.
Flashtool back to zv4, root it, then install recovery. All of this is on zv4. Then you can flash Roms.
engine95 said:
While you might be able to root ZV8, you can't install recovery from the OTA.
Flashtool back to zv4, root it, then install recovery. All of this is on zv4. Then you can flash Roms.
Click to expand...
Click to collapse
Darn, i kinda like how the ZV8 update is, plus i love the way CM is as well since the GS3 always had it installed. Does GPS work now with CM12 for the g3? Theres times where i need it and it never works. Ends up not locking my location.
All:
I have attempted to flash TWRP via various methods to no avail. I have somehow messed something up so I cannot get the stock recovery to work. I can get into the stock recovery screen, but if I select anything, it says Secure boot error. I am currently on OTA 5.0.1 VS98523C. Any advice on how to proceed? I have looked at KDZ options, but am wondering if I can just get the stock recovery back and let it ride until TWRP is available.
Thanks in advance,
Steven
I'm having trouble with getting TWRP to flash successfully. Using their app and flashify
MrSpohn1 said:
All:
I have attempted to flash TWRP via various methods to no avail. I have somehow messed something up so I cannot get the stock recovery to work. I can get into the stock recovery screen, but if I select anything, it says Secure boot error. I am currently on OTA 5.0.1 VS98523C. Any advice on how to proceed? I have looked at KDZ options, but am wondering if I can just get the stock recovery back and let it ride until TWRP is available.
Thanks in advance,
Steven
Click to expand...
Click to collapse
In theory, you can use the dd comment to put the aboot back, but I would not recommend it as I got my phone hard bricked that way. (so dead that even KDZ does not work)The safest way is KDZ back to 10b, and then stump root. Then:
1. Install TWRP manager from Google Play.
2. From TWRP manager you can choose your phone model and download and install TWRP recovery.
3. Follow the instruction from this link to use TWRP to install the 23c
http://forum.xda-developers.com/verizon-lg-g3/development/rom-rom-base-lp-upgrade-bump-t3051884
Never do OTA if you have rooted your phone. It needs to be completely stock for OTA to work.
/\ What he said.
Twrp doesn't work after lollipop because of the signing requirements in the bootloader.
It needs to be rolled back to 10-12b and then rooted and then you can load twrp. Once you have twrp you can load jasmine or skydragon which are both 5.01.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Thanks! So if I want to use xposed, I should roll back to the other versions of lollipop?
thanks all. I KDZ'd 12b stock rom, rooted, then flashed TWRP through flashify. I then went into recovery and installed the 23c rom. I used skydragon 4.0.0 because I tried to flash Jasmine 7.0 like 8 times. I did not have any of the bottom keys and I could not access my pulldown menu. I could not figure out why this was happening. Skydragon worked for me perfectly. Thanks All.
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
you should write this in other section but i want to help you.
maybe try to flash stock kdz again if you still can then check if bootloader method you use is correct but if was not you will brick your phone.
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
actually i gave a answer for you http://forum.xda-developers.com/showpost.php?p=64674426&postcount=2
u even can flash kdz ? if yes, try it and check if your bootloader unclocking method, file, is correct.
You could brick your phone.
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.