Not sure what all information you will need but ask and I shall gladly supply
Got a LG-ls980
Running stock lollipop 5.0.1 on ZVG update or w/e
Rooted using LG One Click Root (program never said it finished but checked phone and root is verified)
Used autorec to get TWRP v2.8.6.1 (seemingly worked fine)
currently trying to flash the latest nightly of Cyanogenmod
Receiving errors like
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error executing updater binary in zip '/pathtopackage/packagename.zip
can no longer boot normally "security error"
I've done some looking around and tried a few different things but nothing has made any changes, any assistance would be greatly appreciated, thanks
I was told something about loki needing to be unlocked but haven't made any progress as this is my first LG style phone
I'm sure the solution has probably been posted somewhere and probably isn't that difficult but either I couldn't find it or I didn't recognize what I was reading
Tokerot said:
Not sure what all information you will need but ask and I shall gladly supply
Got a LG-ls980
Running stock lollipop 5.0.1 on ZVG update or w/e
Rooted using LG One Click Root (program never said it finished but checked phone and root is verified)
Used autorec to get TWRP v2.8.6.1 (seemingly worked fine)
currently trying to flash the latest nightly of Cyanogenmod
Receiving errors like
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error executing updater binary in zip '/pathtopackage/packagename.zip
can no longer boot normally "security error"
I've done some looking around and tried a few different things but nothing has made any changes, any assistance would be greatly appreciated, thanks
I was told something about loki needing to be unlocked but haven't made any progress as this is my first LG style phone
I'm sure the solution has probably been posted somewhere and probably isn't that difficult but either I couldn't find it or I didn't recognize what I was reading
Click to expand...
Click to collapse
Doesn't the 5.x autorec install the 4.4 bootloader? You need a 4.2 bootloader to flash cyanogenmod 12 at the moment, because it still uses the loki exploit, instead of the bump provided with the 4.4 bootloader.
Choristav said:
Doesn't the 5.x autorec install the 4.4 bootloader? You need a 4.2 bootloader to flash cyanogenmod 12 at the moment, because it still uses the loki exploit, instead of the bump provided with the 4.4 bootloader.
Click to expand...
Click to collapse
I realized there were bootloader issues, how do I go about getting a 4.2 bootloader
Tokerot said:
I realized there were bootloader issues, how do I go about getting a 4.2 bootloader
Click to expand...
Click to collapse
Are you planning on running lollipop? I'd suggest keeping the 4.4 bootloader and flashing a CAF-based rom, not only they are much less hacky, they're pretty much stable now.
I'd only flash the old bootloader if I were to install kitkat. Current CM12 sources are VERY outdated.
I was trying to find you the jellybean bootloader but since I don't own a ls980 and I don't visit the section too often this was the closest I could find http://forum.xda-developers.com/showthread.php?t=2627765
I was trying to find you the jellybean bootloader but since I don't own a ls980 and I don't visit the section too often this was the closest I could find http://forum.xda-developers.com/showthread.php?t=2627765[/QUOTE]
My goal is to have CM12 Lollipop but with a working radio (so a KK bootloader but LP rom?) Reading around I've seen people who have successfully done it but I've got no luck. I'm willing to start over and reflash everything needed, I just need the files and order to flash.
If i could find out how to fix this Loki issue i could finish this easy.
Tokerot said:
I was trying to find you the jellybean bootloader but since I don't own a ls980 and I don't visit the section too often this was the closest I could find http://forum.xda-developers.com/showthread.php?t=2627765
Click to expand...
Click to collapse
My goal is to have CM12 Lollipop but with a working radio (so a KK bootloader but LP rom?) Reading around I've seen people who have successfully done it but I've got no luck. I'm willing to start over and reflash everything needed, I just need the files and order to flash.
If i could find out how to fix this Loki issue i could finish this easy.[/QUOTE]
Can you link me to the rom thread?
If everything else fails, there's always the Kitkat KDZ -> Kitkat autorec (which installs the JELLYBEAN bootloader, the one you're looking for).
Otherwise, have you considered maybe using a 5.1.1 lollipop rom?
Choristav said:
Can you link me to the rom thread?
If everything else fails, there's always the Kitkat KDZ -> Kitkat autorec (which installs the JELLYBEAN bootloader, the one you're looking for).
Otherwise, have you considered maybe using a 5.1.1 lollipop rom?
Click to expand...
Click to collapse
Anything you would suggest? I use aviate launcher so really whatever is the best for battery. As long as it's for ls980 and is easy to do.
Thank you for helping me this far I appreciate it.
Tokerot said:
Anything you would suggest? I use aviate launcher so really whatever is the best for battery. As long as it's for ls980 and is easy to do.
Thank you for helping me this far I appreciate it.
Click to expand...
Click to collapse
My pleasure, thank you for using the Q&A section instead of spamming the development threads like users usually do.
While I can't recommend any rom personally (this leads to uneasiness between developers, publicly saying a rom is better than another is frowned upon and for good reason, as they all bust their asses to deliver something for -free-), I can say that anything that has [CAF] in the title is a green light for you.
You can check here or here. I personally use Euphoria-OS as it's basically what you probably think of cyanogenmod with extra customization, but RR, blisspop crdroid and others are really good, too. You just have to look a tiny bit into it. Many if not all of these threads support multiple variants, just search for ls980 and you're good to go.
There are also developers like @zg85 who have done an amazing job both contributing to the CAF-rebase and building several roms for the d802, although practically none are posted as a thread on XDA. While they're not for your variant, there probably is at least a single developer who doesn't post his builds to XDA for the sprint version.
Lastly, as soon as the CAF rebase is complete (as in completely stable, as at the moment there's a bluetooth bug and some connectivity issues), rashed97 himself will post a CM12.1 build and many other roms will pop up (as the device source will be stable, porting will be really easy).
Related
I've been reading these forums for two days now and I'm just add confused as when I started. If I get a new device that comes with the current 12b update, I see root is available, but very Unclear about recovery - all the threads op's are vague and misleading. Any clarification would be appreciated. 2nd: of the plethora of roms available, is it true that the rom itself must be updated for the 12b firmware? That's the jist I'm getting, and how on earth do you know if they have been? It's all very confusing and Unclear. I'm coming from the beautiful unlocked bootloader if the vzw galaxy s3 and our important threads are grouped into guides and updated regularly. Understanding the basics is easy with the s3, but I'm truly questioning if I want the g2 now (I'm a flashaholic) - so confused!
Any detailed help would be awesome..
Sent from my LG-V500 using Tapatalk
you might have some problems with 12b and installing recovery root your phone install an app called freegee and select twrp or cwm i like twrp but i think both work i had one problem when i backed up stock rom stock freaked out and asked for a decrptyion code reboot fixed that so some have reported problems one thing if your going to root install a custom rom because if lg pushes the ota to your device if its rooted it will brick it cm11 is a little unstable but if you can look past some bugs its a great experience
I DO NOT TAKE RESPONSIBILITY if you brick your device ROOTING or modding your device has risk
oh and have fun with cyanogenmod
Personal Experience
Just got a replacement 12B G2, this is what I've noticed:
-Installing root/recovery is still fairly simple on 12B.
-No problems with flashing roms either (tested both TWRP and Philz Touch).
-But KERNELS will throw you a curve ball. 12B requires a separate loki patch from the older builds. PAEK refused to flash in both recoveries (assert failed: run_program("/tmp/loki.sh ==0) until I found a user-patched workaround kernel. After that it flashed fine, but it required some digging.
Right now AOSP is nowhere near 100 percent stable on the VZW G2 and probably won't be until LG gets their act together. Just something to consider. Best of luck!
I hope lg gets there act together cm11 is unstable but I can use it as mY daily driver no problem maybe with a kitkat update it will be more stable
Sent from my LG-VS980 using Tapatalk
Have updated my Tmobile LG G2 to Kitkat and want to debloat it (as I actually like the LG UI). However everything I google about Rooting just links to Kitkat being available but not how (or if) you can root it.
I assume that IORoot22 will only work with 4.2.2, and vroot/kingofroot don't work either, so does anyone know a way to do this?
Thanks in advance
This should be in the Q&A section
Sent from my LG-D801 using Tapatalk
Learnerspermit said:
Have updated my Tmobile LG G2 to Kitkat and want to debloat it (as I actually like the LG UI). However everything I google about Rooting just links to Kitkat being available but not how (or if) you can root it.
I assume that IORoot22 will only work with 4.2.2, and vroot/kingofroot don't work either, so does anyone know a way to do this?
Thanks in advance
Click to expand...
Click to collapse
there is currently no way of rooting T-Mobile's Official KK update.
your best option at the moment is to flash back to 4.2.2 via KDZ > Root + Custom Recovery > Flash SmiLey's Stock KK ROM ( http://forum.xda-developers.com/showthread.php?t=2664652 ) > Flash SuperSU zip before rebooting (Recovery will be lost after reboot).
or wait until an exploit is found, there are at least 3 threads discussing this exact thing in the G2 General Section
edit: This thread seems to be the most promising so keep an eye on it (http://forum.xda-developers.com/showthread.php?t=2667227)
TheCoutures said:
This should be in the Q&A section
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
This is the Q&A section
if you want to keep recovery there is a guide here http://forum.xda-developers.com/showthread.php?t=2673736
Learnerspermit said:
This is the Q&A section
Click to expand...
Click to collapse
Must have been moved it was originally in the Dev Section.
Okay, I somehow rooted my tmobile LG G2 with Kitkat, ran for awhile than did something (don't know what) that removed okay google function from home screen and slowed the google search to a snails pace.
So, like an idiot, I thought I'd just put it back to stock with the D80120a.KDZ. rebooted and restarted everything. BUT the phone still shows rooted in download mode, but rootchecker says I'm not rooted. Also tried to run SuperSU but it says no binary and won't load. Tried Flashify (to try and flash the SU zip) but it also said I couldn't flash because I'm not rooted.
So I ran LG R&D, none of my phone info shows - ran upgrade trying to return it to D80110c/g, but each time it says I'm current and nothing happens.
Have googled every possible search and can't find a fix.
No longer have recovery, because of the stock flash... So I'm in dire need of assistance. Can anyone help me?
Hey,
I got my Galaxy S4 AT&T SGH-I337 as I337UCUAMDB, and ever since then was running cyanogenmod 11.
Recently after a stupid mistake (updating to a nightly, then to M10) I had to return to stock ROM, and on a CM dev's lead installed a NB1 ROM.
Since then, I wasn't able to install TWRP (installing it would make the phone boot only into download mode), and installing CM would produce constant "com.android.phone/acore/media" errors.
Right now I'm running Google Edition for SafeStrap (v1.1 - 4.4.4), which, TBH, isn't nearly as good as CM11 and still very buggy...
I read as much as I could about the whole AT&T GS4 bootloader situation, but still haven't understood it fully:
Could my bootloader have been locked by the update?
If not, why can't I install a custom recovery and CM again?
If so, is there anyway I can downgrade back to MDB (maybe from here?) Or to anything that can allow me to install CM again?
Thanks in advance,
Yuval.
Edit: If I can still use safestrap to install any custom ROM, why can't I install CM? (I did a clean install [full wipe] a couple of times, w/ and w/o gapps, to no avail) Or did I not understand well the safestrap custom ROM options?
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
RAID Xero said:
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
Click to expand...
Click to collapse
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
novikyuval said:
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
Click to expand...
Click to collapse
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Sent from my Nexus 5 using XDA Free mobile app
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
jd1639 said:
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Click to expand...
Click to collapse
RAID Xero said:
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
Click to expand...
Click to collapse
Okay, I think I now fully understand this. Thank you RAID Xero and jd1639 for the help!
I guess I learnt my lesson to look into evil AT&T ROMs before updating to and from them
Also, too bad I never noticed any warning regarding this on Cyanogenmod's website (or maybe I just missed it)...
Thanks again, and unless there's a new magical way to bypass the locking, this thread may be marked as locked.
You're welcome, and happy flashing!
Q&A for [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
NEO2598 said:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
Click to expand...
Click to collapse
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
MeestaAytch said:
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
It has been stated in the ROM thread multiple times that you must use a 4.2 STOCK JB MODEM for best compatibility. Any other modems you guys use is solely at YOUR OWN DISCRETION. @MeestaAytch they should know what to use at this point but thanks for clarifying again for those who don't want to search before posting :highfive:
@jakew02 no problem. I know it's tiring repeating the same information but from what I've seen in my time using XDA.... It'll never change.
I'm glad you devs still continue doing what you're doing for us though knowing this nonsense goes on.
Sent from my LG-LS980 using Tapatalk
A few bugs
Hi,
The thread is too big for me to go thru it post by post so I'll just make a few questions and hopefully I'll get some answers. I flashed this ROM and it was working flawlessly. I only found very few bugs like not being able to set up multiple recurrent alarms because the app would freeze and there was another bug but I can't remember. The problem I find frustrating is with the text messages or SMSs. At first I was not receiving SMSs. Then I was receiving them but I couldn't send any. I returned back to stock VS98024a and I'm still having the same problem but at least I'm getting a pop-up when "General problems: cause code 96". I have googled this several times in several ways and can't seem to find a solution, not even on the Verizon site or help app on the phone. I need help with this please.
How to keep the back home task manager buttor on the screen?
battery life? i want to install on lg d800 and its beta only..
dori kernel
Hi,
From where you get Dorimanx kernel for AOSP ROMs ?
My phone says it can't connect to the camera, and the torch. Does anyone know how to solve this?
Sent from my LG-LS980 using XDA Free mobile app
LG G2 D802 SIM not recognized
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
a13xch1 said:
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
Click to expand...
Click to collapse
Please state exact filename and order of wipe/flash.
Just tried the test build for D802. Booted at LG logo for a while then screen turned black with 2 red lines and one green vertical line. I was so sure I was gonna get the permanent black lines but then again I read that the damaged screens are caused by already faulty hardware under high heat.
Anyways, I panicked and then I restarted the phone by pressing power + down. Then I got the weird boot sequence like everyone above describes and it boots into the OS. Thank God I got no black lines! However it wasn't stable for me as the phone rebooted itself twice within the span of 20 minutes. I'm going back to 13/10 build for now.
Any d802 users flashing latest twitter released rom can you please report here if jdi or lgd and whether or not weird logo appeared?
I'm on jdi and had weird logo appeared after clean flash. I did not let the rom boot and reflashed previous version without further problems
FYI, houston's latest works great so far on the VS980. Clean flash, using RenderKernel R24.
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
jclemens23 said:
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
Click to expand...
Click to collapse
Migrating from one ROM to another is for me like this:
1. Nandroid backup
2. Wipe all except sdcard (yes, wipe system)
3. Flash new ROM
Be sure to always have a Nandroid backup!
And always check what baseband (aka radios or modem) your new ROM is requiring.
-___-
If you are UPDATING your current ROM, I.e. flashing a new build of let's say paranoid android, you can flash the updated file right on top of your old system. That is called DIRTY FLASHING and it's actually risky, so please, always do Nandroid backups!
-____-
Peace
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
jclemens23 said:
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
Click to expand...
Click to collapse
Ok
I would;
Update my custom recovery to the latest
Download recommended baseband, to be on the safe side
Redownload the ROM
Check the md5-checksum
Retry to install it
Flash the recommended baseband, better safe than sorry
Never give up
Peace
Hi guys i just flashed the newest build and out of all the roms i have flashed i have never seen this problem. After i flashed i have no sim service at all. Done a clean install still no good.
I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Taymar said:
I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Click to expand...
Click to collapse
Yea, you can't flash cm or pa on your device. They can only be flashed on devices with the mdb or mdl bootloader. If you're using safestrap, and it's the only recovery you can use, you're probably on 4.4.4, nb1 or nc1 or nj4, bootloader. You'll need tw based roms. See the ones that work with safestrap.
Sent from my Nexus 9 using XDA Free mobile app
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Taymar said:
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Click to expand...
Click to collapse
Your stuck to 4.4.4 unless you do the method mentioned on the forums and GoldenEye comments.
But a caution its not for the new, is risky and you lose the safestrap recovery boot because safestrap is not lollipop compatible right now.
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
I don't own it so I couldn't tell you but I would look up the forum for it before hand and see what they say about it.
If it's not an ATT and Verizon phone most likely it's not boot loader locked.
Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
Oneplus you will be able to root and recovery, I believe even unlock the bootloader. You just have to pay full price of the phone of course, but it's separate from carrier so no root patching OTAs.
Awesome. Thank you so much guys. I think I'm going to try out the oneplus one. Sounds like it'll be a lot more straightforward than with AT&T's devices.