Root Unofficial CyanogenMod 12 for LG L70 D320 D320n D325

The Seby said:

@vm03, I have some questions... I think I'm not the only one who don't know everything correctly, and if you will ask my questions, all the queries of everybody will disappear.

1. Right now, my phone have FastBoot (no Download Mode, no custom recovery as CWM/TWRP), and original Firmware. If I will install PhliiZ Recovery ( http://androidforums.com/threads/philz-ms323-d320n-d325-philz-recovery-for-lg-l70.889246/ ), I will be able to wipe Data/Cache/Dalvik or ART Cache (I'm not sure wich) and then to install CM12 with it, or I must use CWM/TWRP ? I think PhillZ is the bidder right now..
2. If I will install CM12 with PhillZ and everything will be fine, to update the software using the OTA System, we must go to Settings => About Device => Update Software ?
3. If the answer for point three is 'Yes', where will be the software downloaded ? On the Internal Memory ? And, wich is the smaller free memory we must have free on the Internal SD to be able to download it ?
4. After the download is finished, I think we probably have to click a 'Install Update' button or something like this.. After clicking it, the phone will reboot in a CM Updater, and we'll have just to wait ?
5. If the update will crash, I don't know why, will be the phone bricked, or just the software ?
6. When Updating the Software using OTA System, any backup is automatically made ?

Thank you adviced very much for your time!
I'm sorry if I asked a question wich was already asked, but I didn't found here an answer as I want... If you will answer all my questions, if someone will ask any of it again, I will quote your answer for it, for you to not have to answer over and over again the same thing...

Sorry for my English mistakes!

Click to expand...

crutchcorn said:

What modules you test with?

Click to expand...

ledosladoledi said:

I'm not @vm03 but I'll answer questions I know...
1. You can use any recovery made for our phone (I prefer philz)
2. Settings -> about phone -> cm updates -> there will show updates
3. It will download on internal memory and you need enough space for update ( I think 230 mb) and enough for phone to work
4. After download you can press on update and then install and the phone will reboot to recovery and that is the part u need cyanogen recovery (first post) but first install latest cm version with philz/cwm and then change to cyanogen recovery ( if you try to update without it the phone will just reboot to recovery and then u have to do it manually and then wait...
5. We need someone who knows what will happen
6. When updating using OTA there is NO backup because nothing is wiped... Your data is still there after update...
7. Hate it when ppl say sorry for my English and there is no mistakes... xD

Click to expand...

The Seby said:

I requested vm03 to answer because he is the developer, but thank you for your answer!

I still have some concerns:
1. Quote from first post: "unstable, no backup, wipe if enter by keys, slow bootup...
For full working OTA you need cyanogen recovery. If you use CWM or TWRP you can download OTA and install it manually from recovery." | What means 'wipe if enter by keys' ? If I use Power + Volume UP or something like that, it will wipe everything and enter in recovery ?
And that 'slow bootup' means that the first boot after update will be slow, or all boots ?
2. If I download the update on my Internal Memory from Settings => About Phone => CM Updates, I will be able to move it to my External SD and Install from PhillZ ?
3. How to install CM Recovery from computer (with ADB) ? And if I will install it, I will lose PhillZ, right ?
4. CM Recovery have some menu with options like 'Install Update from Internal SD', etc ?

Thank you!

Click to expand...

ledosladoledi said:

1. idk about wipe if enter by keys but slow bootup means when u do adb reboot recovery there will be black screen and after 1-2 min you'll see cyanogen recovery and that doesnt affect system (when phone's bootin)
2. idk where does it store downloads (updates) on phone but you could basicaly copy/paste it to external (i'll look where it stores downloads)
3. you would need to copy the cyanogen recovery .img to root where is your adb and then reboot the phone to fastboot and do fastboot flash recovery <name of recovery>.img and when u install it you loose philz

[EDIT: you could move the <name of recovery>.img to /sdcard/ and then type: dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery and then u basically flashed cm recovery...

4. you want to install cm and then flash cm recovery because there is no option to install cm from cm recovery, only update...

Click to expand...

The Seby said:

Thank you very much! Your answers were very, very good!

Click to expand...

DevMyAndroid said:

Have you flashed the february 14th nightly?? I am downloading now!! @crutchcorn

Click to expand...

socratev said:

Mobile data is solved in this latest release (cm-12-20150214-UNOFFICIAL-w5.zip ) ?

Click to expand...

ledosladoledi said:

np tell us how it goes!

Click to expand...

The Seby said:

http://androidforums.com/threads/philz-ms323-d320n-d325-philz-recovery-for-lg-l70.889246/page-4
I explained there the problem... Can someone help me ?

I must root this software to install a Recovery ? It's an original firmware installable from recovery, and it's not rooted, and it removed my acces to recovery, or it removed my old recovery, I don't know..

Click to expand...

Gabriel Ortega said:

is there any fix for the data in d320f8??? heeeeelp

Click to expand...

ledosladoledi said:

np tell us how it goes!

Click to expand...

vm03 said:

Yes, i think how to fix it.

Click to expand...

DevMyAndroid said:

When is the camera fix for ms323 coming out?????

Click to expand...

kenboyles72 said:

on another note, went to install xposed framework and said it was incompatible. I know xposed works on cm12 and this phone. Also had this error:

CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by "data/data/de.robv.android.exposed.installer/cache/app_process"; caused by library "libdvm.so" not found.

Click to expand...