• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Unofficial CyanogenMod 12.1 for LG L70 D320 D320n D325 MS323

what bugs contained in this rom? i would flash it but people say . that mtp usb cant work on my windows>?:( how to fix that bug?
 
Defnof said:
Yes, I wipe all partitions except for storage ones, then I flash the ROM GApps and Facelock, at this point it boots fine and I go through the Setup Wizard after which I try to flash latest Xposed zip file which results in a bootloop.
EDIT: Nevermind It booted after I wiped my SD card redownloaded the files and flashed all over again, however I didn't flash facelock zip this time so that might have been the issue.
Click to expand...
Glad you overcome it. Fyi, I never flash facelock either.
 
Question. I'm on ms323 on 2/19 build. If I flash latest ROM, I don't have to flash the system ui fix right? Like its already patched in the ROM itself? And another, when I want to install 3rd party apps, do I put the app on SD, then flash it from twrp like I would gapps? If not , then how can I turn on "unknown sources" since that force closes? Or is that patched to??? Thanks in advance
 
Camponuevo said:
Question. I'm on ms323 on 2/19 build. If I flash latest ROM, I don't have to flash the system ui fix right? Like its already patched in the ROM itself? And another, when I want to install 3rd party apps, do I put the app on SD, then flash it from twrp like I would gapps? If not , then how can I turn on "unknown sources" since that force closes? Or is that patched to??? Thanks in advance
Click to expand...
You should just be able to flash it and everything should work, I'm using the latest build with no problems.
 
When I flashed the home button, Security settings and uninstalling apps didnt work ( every time I go to uninstall a app it restarts my phone ) I have since flashed to 3 other version of this to see if it was just a build glitch but all have these issues. Any help would be awesome!
 
Latest 0524 update killed my 8GB ultra fast SD and 32GB another sd read as 8.700 MB and another issue when plugin pc phone is turning off or it's freezed on black screen because need to push power button for 10 sec or more to boot.
Same issue with another micro SD if the phone is working, screen OFF nothing work.

Edit:
Don't let you phone auto lock he will turn OFF !!!
 
Last edited:
ant0ni0411 said:
Latest 0524 update killed my 8GB ultra fast SD and 32GB another sd read as 8.700 MB and another issue when plugin pc phone is turning off or it's freezed on black screen because need to push power button for 10 sec or more to boot.
Same issue with another micro SD if the phone is working, screen OFF nothing work.

Edit:
Don't let you phone auto lock he will turn OFF !!!
Click to expand...
Can you be a little more specific? I can see you are frantic about the situation, but we need to know what variant of the L70 you have before we can help.
 
I'm using d320n 8GB ultra sandisk sd not working in other phones, in my phone with newest update is hot as hell (also not working).
other SD its ok i formated the sd and now its 32GB.
I go back to 0520 full wipe all ok now execpt SD card it's fried i think.
 
ant0ni0411 said:
I'm using d320n 8GB ultra sandisk sd not working in other phones, in my phone with newest update is hot as hell (also not working).
other SD its ok i formated the sd and now its 32GB.
I go back to 0520 full wipe all ok now execpt SD card it's fried i think.
Click to expand...
We can't fix fried SDCards. So sorry that it broke. But that's the risk you take when flashing ROMs.
 
LitrosNub said:
No, it's not supported in Lollipop, it's been stated over 100 times and there's even a thread someone made that said if there was a fix.

The answer: no.
Click to expand...
That's in fact a incorrect statement. I just upgraded from 5.0 (lollipop) and it was working. So it does work on "lollipop". Its a problem with 5.1, so I asked if there was a fix, since the bug isn't with lollipop in general. Thanks for your input though.
 
Camponuevo said:
That's in fact a incorrect statement. I just upgraded from 5.0 (lollipop) and it was working. So it does work on "lollipop". Its a problem with 5.1, so I asked if there was a fix, since the bug isn't with lollipop in general. Thanks for your input though.
Click to expand...
I see, I'm sorry. I thought it was unsupported without doing some fixed with the SELinux and you couldn't do that.
 
You must log in or register to reply here.
Back
Top Bottom