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

Root Unofficial CyanogenMod 13.0 for LG L70 D320 D320n D325 MS323

Cm 13 is fast but the bugs killing the ROM . *can't screenshot .. *Auto rotation not functioning properly . is there any fix to these ?
 
fenokiyo said:
Cm 13 is fast but the bugs killing the ROM . *can't screenshot .. *Auto rotation not functioning properly . is there any fix to these ?
Click to expand...
6787e97f454059a972b3d67788992268.jpg


I used cm13 and auto rotate works fine for me. I'm not using the latest nightly though.[emoji4]
 
hacko3 said:
Someone have problems with the volume of the principal speaker?

Yes, I have this problem too.
It sounds very weak in conversations!
I've gone back to 12.1, for this reason.
CM 13 is very ok and the phone moves excellent
if it would solve this issue would be wonderful ...

Waiting to get back to CM 13 ....I hope as soon as possible......:)
Click to expand...
 
Edje11 said:
I really messed up my L70-D320. I was installing Cynagenmod 13 with adb sideload cm-13.0-20160114-NIGHTLY-w5.zip
Update crashed and now there's nothing, No TWRP, No bootloader, No fastboot :eek:
The only thing that's still working is ADB. Trying opening a shell in adb will give adb /system/bin/sh failed: no such file or directory.
Tried this Unbrick trick with Linux, but unfortunately that's also not working.
Looks like the partition table is damaged.

Somebody an idea to get it back a life?
Click to expand...
Did you fix it?
 
HI
REQUEST:FOR MAKING SYSTEMLESS ROOT FOR LG L70 D325 CM 13

I know the CM 13 rom is pre rooted...but some apps like xmod games any many othes does not work properly with this type of root permission...they want permission from SuperSU....so please kindly help....all the LG L70 USERS WILL BE GLAD IF YOU KINDLY HELP US..
 
Good Morning.
I have problems with a Micro SD SanDisk 32GB Class 10 in my Lg L70 MS323 with CM13 and it happens that when I format internal memory as not accepting it. Greetings and hope to answer if it happened to someone and as resolved.
 
Hi there,
I'd like to use link2sd but it doesn't mount a dedicated sdcard partion during boot properly. It relies on a script in init.d. I fixed the script but it still doesn't work as long as scripts from init.d are not run during boot time anymore.
Is is a bug or a feature? Is there any other place where to place a script so it gets fired during boot?
 
Hurry, i flash 20160226 with twrp and yes bugs fixed, but the camera dont working. And i dont return to android 4. I have d320 and i see others users can fix camera but me not. Help me!!! :(
 
Just installed the latest build (cm-13.0-20160305-UNOFFICIAL-w5.zip) on my D325f8 and everything went smoothly, except for one tiny detail that I forgot about: approximately the lowest 130 pixels of my touch screen do not work. It is a hardware problem and I won't be able to fix it in a long time. Therefore, I cannot get past the welcome screen :'( I can't click next or anything like that!

I was previously using my cellphone with this easy fix to bypass the non-working portion of the screen:
Code: 
adb shell wm overscan 0,0,0,100
And then:
Code: 
adb shell wm density 216
This way nothing was drawn on the faulty part of the screen and nothing on any interface was cut. Now I installed cyanogen I simply can't click next and
Code: 
adb devices
can't find my device (probably because USB debugging isn't even enabled...), so I can't fix the screen problem.

Searched everywhere on how to fix this issue in some way but couldn't find anything remotely related.
 
Regarding my issue, I was finally able to boot up TWRP and tried reinstalling any other nightly of CM13 I could find for L70 D325f but all of them have the "next" button on the welcome screen on the right lower corner, and I can't click it! Looks like I'm out of luck. Several things would solve my problem, such as:

- Being able to turn on USB debugging and authorizing my PC, so I could use "adb shell wm overscan 0,0,0,100" and "bump up" the screen a little
- If the welcome screen rotated as my phone rotated (potrait view), making the button clickable.
- If the button was somewhere else
- If I could turn on soft keys, as that would also bump up the button a little, making it clickable.

But ALL my attemps to use one of these solutions failed! I've tried everything, including modifying the build.prop using TWRP's file manager, but after I do that the phone simply doesn't boot into cyanogen, the screen goes black and I can't even turn the phone on again until I remove the battery.

Edit:

By the way, I did not encounter this problem with CM 12.1. When I got to the welcome screen there and inserted the USB cable, a window appeared asking me if I wanted to turn on USB Debugging. I said yes, of course, and then I could fix my screen with the adb comands. Seems strange that the exactly same thing doesn't happen in CM 13.0. A bug?
 
Last edited:
Hey guys I have an LG - D325 . After flashing cm 13 my phone cannot detect any SIM card. I have CWM recovery installed. Does anyone know of a solution?
 
They do have an unofficial TWRP for d325 but it causes the same pink screen error with fastboot as well . Anyways, I don't think CM 13 's functionality should be dependent on which custom recovery we are using....
 
sdfaf said:
They do have an unofficial TWRP for d325 but it causes the same pink screen error with fastboot as well . Anyways, I don't think CM 13 's functionality should be dependent on which custom recovery we are using....
Click to expand...
I had issues with network and button layout until I used twrp. There is a reason it says twrp as a requirement in the cm13 post
 
Tweakforce_LG said:
I never used flashify as it caused a purple screen. Fastboot worked for me but I guess they don't have twrp for the d325?
Click to expand...

They do have an unofficial TWRP for d325 but it causes the same pink screen error with fastboot as well . Anyways, I don't think CM 13 's functionality should be dependent on which custom recovery we are using. The uploader of CM 13 does mention we should have the correct variant of our model's bootloader for sim detection to work. I wonder if that's where the problem lies....
 
sdfaf said:
They do have an unofficial TWRP for d325 but it causes the same pink screen error with fastboot as well . Anyways, I don't think CM 13 's functionality should be dependent on which custom recovery we are using. The uploader of CM 13 does mention we should have the correct variant of our model's bootloader for sim detection to work. I wonder if that's where the problem lies....
Click to expand...
I didn't have to touch my bootloader once I unlocked it. You could look into that though.
 
sdfaf said:
They do have an unofficial TWRP for d325 but it causes the same pink screen error with fastboot as well . Anyways, I don't think CM 13 's functionality should be dependent on which custom recovery we are using. The uploader of CM 13 does mention we should have the correct variant of our model's bootloader for sim detection to work. I wonder if that's where the problem lies....
Click to expand...

Actually TWRP is required to properly install cm13 as it has been said a couple of times. CWM is unable to properly execute cm13 install scripts, and that's why there are some users having issues when using CWM.
 
But it seems TWRP doesn't work on LG D325 (firmware - D32510f_00) . I have followed both the methods given in below link from androidforums and each time I got the same pink screen error. Do you know of any other method to flash twrp?

http://androidforums.com/threads/twrp-ms323-d320n-d325-team-win-recovery-pro-3-0.911656/
Mystery_Flasher said:
Actually TWRP is required to properly install cm13 as it has been said a couple of times. CWM is unable to properly execute cm13 install scripts, and that's why there are some users having issues when using CWM.
Click to expand...

Tweakforce_LG said:
Couldn't have said it better thanks :)
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom