Need help installing cm13 on my lg ls980 - Sprint LG G2

Hello guys
First I own a lg ls980(sprint version) it was on jelly bean when I got it but last year I rooted it and installed twrp(using freegee since autorec caused sofbrick to my phone) then I flashed cm12.1(android 5.1.1) and everything worked fine
Yesterday I decide to flashed cm13 or any other marshamellow based ROM so I found a post on xda (https://forum.xda-developers.com/sprint-g2/help/sprint-lg-g2-ls980-how-to-install-cm13-t3273187) that said that the bootstack are different and I have to install bumped twrp(blastegator) and a hybrid bootstack(https://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219) so I installed bumped twrp first and everything was OK but after I installed the bootstack my phone bricked ( I got secure booting error ) I was unable to boot neither in recovery or system so I had to unbrick my phone (forcing qbulk mode and using skr tool) and reflashed a stock ROM and installed twrp and cm12.1 again
Everything work fine but I really want to to upgrade to cm13 so what should I do about the bootstack (I am sure that the problem is because of the bootstack because I tried twice and in both case my phone brick after I install the hybrid bootstack and before I install cm13)
Thanks in advance for your help

Follow this guide:
https://forum.xda-developers.com/sprint-g2/general/ls980-lollipop-update-root-sim-unlock-t3357837
Then root and install bumped TWRP from blastegator.
That's should be enough to install custom roms. Since you flashed stock ROM, your EFS partition is likely cleared and destroyed and can no longer be activated.

Related

[Q] Not a V500 (it's a palman) G.Pad 8.3 v500d

Yoh Guys,
so i just bought the G-Pad 8.3 about 6 Months ago or so. Yesterday i decided to flash a custom rom
and with hours of searching i managed to install the latest TWRP 2.8.0.1. So everytime i enter recovery
it says:
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
Then i'll hv to wait for about 2-3 seconds untill it gets me to the TWRP recovery. Is it normal?
So i moved the custom roms (mahdi, cm infected, A.I.C.P and latest gapps to my SD-Card). Since then
I was trying to install the custom roms but it says that my device is a "palman" and no "v500".
Any1 knows whats the problem or why I can't flash custom roms?
I googled it already but it seems that only 1 person had the same problem.
Regards and thx in advance.
p.s. I'm running the latest Android Version (4.4.2) for this device.
Maybe you installed the v510 GPE (palman) TWRP on your v500? If you did that, then flash the correct TWRP.
http://forum.xda-developers.com/sho...
[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]
Thx a lot for the link m8! All the research I did on finding the latest TWRP was always for the palman even they said its for the V500 which caused me the problem with the recovery. I flashed the recovery in the link u gave me and flashed philiz right away. Now everything's smooth and works like a charm (running A.I.C.P btw). Do u know any other active projects besides A.I.C.P. and CM Infected which is worth testing/using?
I'm running stock 4.4.2 and havent tried anything else. I'm just going to wait and hope someone ports Lollipop 5.0 from the v510 to the v500.

Cannot install CM11 no matter what

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.

Problem with dirty flash older version of a custom rom

Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?
Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.

Bootloop on installing AOSP based ROMs

Hi.
I had an issue with my phone and I flashed a stock LG KDZ to go back to stock before sending my phone to LG.
Now, after having re-rooted my phone, via the 1-Click Root tool for LL, I can only install stock based ROMs such as Fulmics 5.1, but if I try to install an AOSP ROM such as Exodus/Candy6/RR/etc, I get a soft boot loop after rebooting from TWRP..
Using latest 3.0.2-0 TWRP recovery.
Anyone got any ideas?
Note, I was running AOSP based ROMs for the last year without issue..
I am having this same issue. For CM13 and Dirty Unicorns. Can someone help?

Unable to Install TWRP Recovery

Hello everyone, I have LG G3 D851 T-Mobile.
I was on 5.0.1 and wanted to install custom ROM and for this I needed to install custom recovery first so I used Flashify to install TWRP (twrp-3.1.0-0-d851.img) , installation works fine it says installation complete, but when I restart the phone it starts bootloop.
So I restored my phone back to stock (4.4.2), rooted and again repeat flashify process this time again the same issue of bootloop.
Can Anyone here help me in this matter.
Thanks
Ha ha ha. If you had searched/looked here on xda you would know twrp 3.1 does not work only bootloops. Also twrp 3.0.2 is no good either. You should use the unofficial builds. Also a restore is not needed just pull battery for a minute and then it will boot back to the installed rom.

Categories

Resources