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

Root Official CyanogenMod 13.0 for LG L70 D320 D320n D325 MS323

Stargate2401 said:
Firstly, thank you very much for trying to help me, I appreciate it.
So in order to unlock my bootloader(D320N) I have to follow instructions here?:http://forum.xda-developers.com/showpost.php?p=53966360&postcount=3 I suppose that aboot.bin and the other files in the google drive link are appropriate for D320?? I replaced CWM_L70_V2.img with TWRP from here: http://vasy.ru/TWRP/w5/ but when I run the adb.exe from the files I extracted it only opens runs a thousands commands and closes after 1,5 seconds without anything happening.
Click to expand...

Before launching adb, make sure that :
  1. Your phone is rooted
  2. You installed SuperSu from Play Store and it's working
  3. Your phone is connected to a pc using USB debugging. You may turn USB debugging on in developers settings
 
Mystery_Flasher said:
Before launching adb, make sure that :
  1. Your phone is rooted
  2. You installed SuperSu from Play Store and it's working
  3. Your phone is connected to a pc using USB debugging. You may turn USB debugging on in developers settings
Click to expand...
Again nothing happens. I extracted the zip in an empty folder, I replaced the CWM_L70_V2.img with twrp-3.0.2-0-20160407-w5.img which I then renamed to stockrecoverymod.img and when I run adb.exe from the files I extracted(even with admin run), it opens a command prompt with rapidly appearing commands(50+ lines) and it closes 0,83 seconds after I opened it. The phone is rooted and supersu was installed along with the rooting process and I updated it from the google play store, usb debugging is enabled and granted this computer permission, I tried switching between charge only, MTP, PTP nothing worked. Could avast antivirus(on the phone) be responsible for this? If you don't have any other suggestions Mystery_Flasher, I'll simply continue using stock ROM. It's ok, thank you again for all your help. :D
 
Stargate2401 said:
Again nothing happens. I extracted the zip in an empty folder, I replaced the CWM_L70_V2.img with twrp-3.0.2-0-20160407-w5.img which I then renamed to stockrecoverymod.img and when I run adb.exe from the files I extracted(even with admin run), it opens a command prompt with rapidly appearing commands(50+ lines) and it closes 0,83 seconds after I opened it. The phone is rooted and supersu was installed along with the rooting process and I updated it from the google play store, usb debugging is enabled and granted this computer permission, I tried switching between charge only, MTP, PTP nothing worked. Could avast antivirus(on the phone) be responsible for this? If you don't have any other suggestions Mystery_Flasher, I'll simply continue using stock ROM. It's ok, thank you again for all your help. :D
Click to expand...

You use adb in a wrong way :p
You should enter the folder when it's placed and run cmd by using right mouse button and left shift. There should be an option called Run command prompt here, etc. From there you type all the commands or copy-paste them.

So, opening exe is not a proper way this time :D
 
Mystery_Flasher said:
You use adb in a wrong way :p
You should enter the folder when it's placed and run cmd by using right mouse button and left shift. There should be an option called Run command prompt here, etc. From there you type all the commands or copy-paste them.

So, opening exe is not a proper way this time :D
Click to expand...
Wow thanks. So I moved the files where adb is located. I opened up cmd and changed directory to where adb is located. I entered the command adb. Then I did enter successfully these commands:
adb push aboot.bin /sdcard/aboot.bin
adb push stockrecoverymod.img /sdcard/stockrecoverymod.img
adb shell
su

but when I enter the next commands it says unknown operand if. what does this mean?
 

Attachments

  • bootloader.png
    bootloader.png
    8.2 KB · Views: 89
Stargate2401 said:
Wow thanks. So I moved the files where adb is located. I opened up cmd and changed directory to where adb is located. I entered the command adb. Then I did enter successfully these commands:
adb push aboot.bin /sdcard/aboot.bin
adb push stockrecoverymod.img /sdcard/stockrecoverymod.img
adb shell
su

but when I enter the next commands it says unknown operand if. what does this mean?
Click to expand...

Look at the commands again, I see you typed the last command twice, that's why you get an error. You may only use one command at the time and press enter afterwards.
 
Mystery_Flasher said:
Look at the commands again, I see you typed the last command twice, that's why you get an error. You may only use one command at the time and press enter afterwards.
Click to expand...
The problem was that there were spaces in the commands i copied. insted of dd if = / dev / block / mmcblk0p6 of = / sdcard / abootorg.bin it should be dd if=/dev/block/mmcblk0p6 of=/sdcard/abootorg.bin
After I did those it now says cannot open for read: No such file or directory
 

Attachments

  • bootloader2.png
    bootloader2.png
    23.3 KB · Views: 114
Mystery_Flasher said:
It works for me. I've restored a 3.02 backup a couple of times.
I'm not using an adaptive storage, BTW. Don't know if this can be related to your issue.
Click to expand...
I made a new installation, had the old partition table, then restore 2.8.7.0 to restore stock and then the new partition table once I installed everything and reinstall 3.0.2.0 does not pass the logo
I have no problem to flash from 2.8.7.0 I flashify premium and works the same, but I would like to put the 3.0.2.0
a greeting
 
Mg977 said:
when I try to restore the TWRP recovery 3.0.2.0 does not pass the logo
Click to expand...
solved, if you use the sd as internal does not allow you to flash any recovery, he went back to the normal format to put the TWRP 3.0.2.0 and returned to internal format and ready
 
Deadpoolddt said:
Hey Mystery! Quick question here... Soo once i install the las nightly can i repaprtition back again or not?
Click to expand...

Hi ;) the answer is no, you can't.
All future nightlies will require your system partition to store 1100 MB or more. Trying to flash them will probably lead to "not enough space" warning or will stuck at "patching system unconditionally " within TWRP
 
You must log in or register to reply here.
Back
Top Bottom