Hey guys, i have installed CM 12.1 on my LG G3 D855.
Everything seems to work fine and correct.
Only one problem is left, i made a factory reset (in settings), the phone rebooted. It rebooted in Recovery (TWRP) but there it stuck in a boot loop. I removed the batterie and and restarted the device. Now it boots correct, but i think my TWRP is still broken. Is there a way to fix it?
Can i simply use e.g. Flashify app to install TWRP correct again?
Don't ever perform a factory reset or take an OTA update w/ a third party recovery like TWRP installed. You're lucky you were able to get the phone to boot normally. There's probably nothing wrong w/ TWRP, but yes... you can use Flashify again to re-flash recovery.
Okay, i thought it will only reset the CM - specific settings and not the LG ones.
Can i use "OTA"-CM Updates? As i am using the Nighties and there is an Update everyday - or should i just update once a week?
Could there be a problem with my "broken CR?
As you have said I can use Flashify for flash TWRP again, can i use the normal files which are made for stock, or do i have any special CM ones?
Thanks.
Related
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?
I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.
It happened with me twice on Lg F220 & LG G2Ls980, stock lollipop firmware and TWRP Recovery was installed on both devices, i just rebooted the device to recovery mode to see which version is installed and explorer the different setting(i didn't activated anything) and reboot back to the system, now every time the device starts, the brightness level go to 100% and screen off time to 2mins. this happened on both of the devices, can some tell me what caused that problem.
Now i have bought an LS980 for myself, i have successfully rooted it and now its time to install a recovery, personally i love 4ext recovery but unfortunately it is not available for this device, i have only option to install TWRP, but now am afraid that if i installed it same problem will occur to me :crying:
""My device has Stock LS980ZVA installed""
Insert sim card or use custom rom. Its not a recovery deal
Librastar said:
It happened with me twice on Lg F220 & LG G2Ls980, stock lollipop firmware and TWRP Recovery was installed on both devices, i just rebooted the device to recovery mode to see which version is installed and explorer the different setting(i didn't activated anything) and reboot back to the system, now every time the device starts, the brightness level go to 100% and screen off time to 2mins. this happened on both of the devices, can some tell me what caused that problem.
Now i have bought an LS980 for myself, i have successfully rooted it and now its time to install a recovery, personally i love 4ext recovery but unfortunately it is not available for this device, i have only option to install TWRP, but now am afraid that if i installed it same problem will occur to me :crying:
""My device has Stock LS980ZVA installed""
Click to expand...
Click to collapse
Never experienced that, after installing a version of TWRP, upgrade to Blastagators TWRP 3.0.2.1 bumped & signed. I don't have the link handy, but searching should find it for you. But i agree, i have never had this happen on any version of TWRP recovery -i thinks it's un-related.
Agimax said:
Never experienced that, after installing a version of TWRP, upgrade to Blastagators TWRP 3.0.2.1 bumped & signed. I don't have the link handy, but searching should find it for you. But i agree, i have never had this happen on any version of TWRP recovery -i thinks it's un-related.
Click to expand...
Click to collapse
Is there any difference between normal TWRP & Blastagators TWRP ??
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Peshyy said:
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Click to expand...
Click to collapse
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
steadfasterX said:
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
Click to expand...
Click to collapse
twrp-3.0.2-1-h815.img, H815 as the title says and from the official website as I've always done. As for the thread - I don't have TWRP and I can't even flash it as I've written in my post. That's what I'm struggling with.
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hi there,
I'm having a strange behaviour with my recovery. im using TWRP 3.1.0-0 for OP3 from official website.
I encountered this problem some days ago, while flashing a new rom (i'm atm on PureNexus) but I didn't realized how it was happening.
Everytime i get into TWRP, even without doing anything at all, phone gets a full reset (data+internal storage).
I noticed this because I was about to flash magisk and i downloaded it from magisk app (it gets downloaded in /sdcard/MagiskManager/) then after booting into recovery I was unable to find any file from the "install" menu. I then rebooted to system and i got android's first start wizard.
dedo.93 said:
Hi there,
I'm having a strange behaviour with my recovery. im using TWRP 3.1.0-0 for OP3 from official website.
I encountered this problem some days ago, while flashing a new rom (i'm atm on PureNexus) but I didn't realized how it was happening.
Everytime i get into TWRP, even without doing anything at all, phone gets a full reset (data+internal storage).
I noticed this because I was about to flash magisk and i downloaded it from magisk app (it gets downloaded in /sdcard/MagiskManager/) then after booting into recovery I was unable to find any file from the "install" menu. I then rebooted to system and i got android's first start wizard.
Click to expand...
Click to collapse
use blusparks twrp
Like earlier, just use the latest blue_spark twrp and you will be fine.
Thanks guys, I've flashed and done a couple of reboots in recovery. Seems fine so far now
Glad it fixed
Hello guys.
I'm having trouble here with a friend's device.
the device simply reboots the twrp.
I already realized the flash of several rons, I also tried with the stock.
installs everything correctly, but at the time of doing the reenicialization in the system returns to twrp again.
I have already tested several versions of twrp and also did not succeed.
Has anyone ever had this problem? I'm finding it very strange, because I've been with rom for a long time and I've never had any problems like this.
What do you think it could be? and how can I resolve and re-restart correctly again?
Thank you in advance.
You flashed the stock ROM and you still have TWRP? Then something is wrong. Usually when that happens you did something wrong. So this is a good thing you are stuck in TWRP. Usually a factory reset will make it boot again. You can pull data off from TWRP before doing this (like pictures and such).
What exactly have you tried to flash (order too), and what version of TWRP are you using. The factory ROM may not have worked as well if you tried to flash the latest, without having the treble partition setup, or did not have a version of TWRP that keeps the vendor partition mounted.
We really need a few more details on what you tried to help.
If you just want to get it booting, I would try wiping everything in BluSpark's TWRP, and flash 5.1.5 OOS.