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

Root Unofficial CyanogenMod 12 for LG L70 D320 D320n D325

Status
Not open for further replies.
HELP!!!!!!!!!!!!!!!!!!!!
 

Attachments

  • Screenshot_2015-03-12-11-02-52.png
    Screenshot_2015-03-12-11-02-52.png
    80.9 KB · Views: 99
I want thank the author for making this impressive port yet it still seems to be a good 4-6 months before its probably ready for an everyday use phone . Seems like this rom is still in alpha stage and we are basically the testers ironing out the bugs .I really want this project to thrive as the L70 is a common yet fairly decent lower end $75 USD android phone and it deserves a lolipop port. However the process of unlocking the bootloader for the L70 is difficult for the novice and is something I purely got lucky on. I followed some 2 step guide and could only get through step 1 as it involved command line and busybox. Somehow using an app called Flashify enabled me to flash the recovery rom CWM 6.0.5.0 from within Android itself. After that I was able to boot into Clockworkmod and install Cyanogenmod. I basically accidently stumbled upon a solution that most people wouldn't have tried. Finding a better more straight forward method with maybe a GUI overlay to unlock the bootloader for the L70 seems to be a need as well to get further interest going in this project. The bootloader just seems like way too much for work ATM since its considered a lower end phone.

TLDR=The reason I went down the custom rom road I did with my LG L70 MS323 is that the phone would randomly reboot when it went into lock mode after 2 minute of inactivity and would drain battery power like crazy even after factory reset. I tried changing the battery and using 3 different .kaz files released from Metro and it still did the same thing. I wanted to use the D321 kdz from Cricket but LG Tool 2014 wouldn't allow me to flash it to that so I was basically stuck with a phone that couldn't go into power saving mode without shutting off.
 
Last edited:
My main problem is now is the "Unfortunately, System UI has stopped" anytime I press the power button on my phone and never stops until I factory reset the phone again. I think me not clearing the cache is the cause yet I can't even get back into clockworkmod recovery as I didn't install GAPPs at the time so I have no Google Play to download some apps to clear the cache. Even trying to put .APK files that could fix the cache issue crashes in settings and I don't even know how to turn on allow unauthorized apps so I am now at a dead end trying to fix the SystemUI problem.
 
dleejuly83 said:
My main problem is now is the "Unfortunately, System UI has stopped" anytime I press the power button on my phone and never stops until I factory reset the phone again. I think me not clearing the cache is the cause yet I can't even get back into clockworkmod recovery as I didn't install GAPPs at the time so I have no Google Play to download some apps to clear the cache. Even trying to put .APK files that could fix the cache issue crashes in settings and I don't even know how to turn on allow unauthorized apps so I am now at a dead end trying to fix the SystemUI problem.
Click to expand...
Most people are saying it's a lockscreen error. I get fc from startup no lock screen even with factory reset.

@vm03 ill provide the images. Want them from an fcing or non fcing cm12 build? Might as well fix the bug before cm12.1...
 
I Installed this ROM only first and faced the below issues and gone to MIUI ROM
1. "Unfortunately, System UI has stopped":eek:
2. Not able to enter the recovery, (To enter i must Hard Reset the Phone):(
3. Unknown Sources option for installing third party apps from GPlay is unavailable in Security.:(
4. If the step 1 is fixed then i could test more and report the bugs here to make this a stable ROM ASAP......;)
 
Please help me to install/update the framework.. I have download, install and check the modules box and then I can't tap install/update framework.. If I just reboot, there will be no impact on the modules.
 

Attachments

  • Screenshot_2015-03-12-19-31-50.png
    Screenshot_2015-03-12-19-31-50.png
    64.5 KB · Views: 99
Status
Not open for further replies.
Back
Top Bottom