Develop Bugs

[HOW-TO] Simplified Root + Recovery + Custom ROM

This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition

titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too

help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks

Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.

Thanks a lot.Real helpful

Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.

KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.

Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.

Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).

I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?

cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.

bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.

cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.

Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.

bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.

Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?

luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839

Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks

Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?

ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.

How to Fix Boot Loop (Was How To Disable LG G3 OTA Update Notification)

I have a rooted LG G3. I used autoprime's guide to turn off OTA updates:
Unfortunately, it did not work. (As the disclaimer says, "This worked on LG G2.. hopefully work on G3 but won't be confirmed until OTA comes out".)
Since it did not work and since my phone downloaded the OTA, I have some questions:
1. How can I safely remove this update file and remove the notification?
2. How can I prevent my phone from downloading future updates?
Thanks!
UPDATE: Now I have a real problem! I followed a post that said to delete the downloaded update zip file, then click the notification to install the update. That was supposed to immediately fail and also get rid of the notification.
Instead, what happened (short version) is that my phone is now booting into TWRP only. I see an LG logo, then it goes into TWRP.
In TWRP I can see that all the system files are present. I know that no update could have been written to my system because I deleted it. I hope that this is just a flag set somewhere telling the system to boot into TWRP. Is that so? Can I find this flag and reset it so the system will no longer think it has to boot into recovery to install something?
I appreciate any help!

http://www.reddit.com/r/LGG3/comments/2fzj9t/tmobile_g3_software_update/
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.

Well iam rooted and have twrp installed. Is there anyway to install the ota? Do i need the factory recovery for it? Where can i find it?

indianx said:
Well iam rooted and have twrp installed. Is there anyway to install the ota? Do i need the factory recovery for it? Where can i find it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
There is a link in the OP to download a pure stock rom you can update and re-root from there. Alternatively you can just flash zonerom which has been updated to the post updated version. :good:

[Solved] Help: "Secure Boot error" When trying to boot into recovery

HI everyone.
Today, I managed to root my LG G3(D855) that is on the Lollipop version(OTA update).
The reason for this root was to flash the cyanogenMod 12 rom. I found out that I needed a bump'd twrp recovery image which I got from this page:
I tried using flashify to flash this image which flashify claims was a success but when I try to boot into recovery, it gives me a "Secure boot error" message.
does the same methods that apply for flashing custom recovery in android 4.4.2 on LG G3 not apply to Lollipop versions?
if I do a battery pull and boot up the device normally, the device seems to work alright but I can't boot into recovery.
So, please I need help as I want to install this CM12. it bothers me a lot that my nexus 7 seems faster than my G3
-- Problem Solved---
I was able to fix this problem and booting into a custom recovery by going through this thread: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
Here are the files I used:
"aboot.img" from a kitkat D855 stock rom. (here is the one I used https://docs.google.com/file/d/0B7fkQwhNpU7YNTdfZUQyZlQzLTA)
oversharpening fix flashable zip (here is the one I used http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648 used the latest version at the time of posting.)
a bump'd twrp recovery image for D855 from here: http://downloads.codefi.re/thecubed/lg_g3/bump/
kikat bootstack from here for D855: https://www.androidfilehost.com/?fid=95916177934540501
after getting all these files, move it to the root folder of your SD card.
attempt the process below at your own risk
Here is how I used the files:
I first used flashify (download from play store) to install the bump'd twrp recovery.img.
Then using android terminal emulator (download from play store) I ran this command
Code:
su [b](no need to retype this if you did not exit from the previous Android Terminal session)[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/lollipop-aboot.img [b](this makes a backup to your Internal Storage)[/b]
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](writes “zeroes” to the partition to “wipe” it out)[/b]
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](flashes the Kitkat version aboot.img to the aboot partition)[/b]
from this post: http://forum.xda-developers.com/showpost.php?p=59353812&postcount=44
I then reBooted my device into recovery mode which of course now has become TWRP recovery.
in the twrp recovery I flashed in the oversharpening fix.zip file (I was prompted during the installation to choose a sharpening level, I chose 5. this value doesn't have anything to do with the recovery process, we just need it to bump the lollipop boot.img)
After that, I flashed in the Kitkat boot stack and then rebooted my device.
that's it. I am on CM 12 now. Good luck.
and of course, credit goes to this user: @topet2k12001. He is a G3 superhero.

same
Hey ,i got the same problem ,just rooted my d855 and i want to flash a custom recovery so i can install xposed ,but after flashify reboots the device i get the same message...plz reply me if u found a solution

N00R28 said:
Hey ,i got the same problem ,just rooted my d855 and i want to flash a custom recovery so i can install xposed ,but after flashify reboots the device i get the same message...plz reply me if u found a solution
Click to expand...
Click to collapse
I did but it was a very complex solution. see http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
I am yet to attempt that.

Causes of "Secure Boot Error"
Hi Friends,
"Secure Boot Error" and "Certification Verify" are already "known" errors, and by "known" it means that the causes are already well-established and therefore, can be fixed.
Please visit my thread and read the very first post at Page 1, for the following topics:
1. "The Logic Behind It All"
2. "Troubleshooting and "Q&A"
Heads up: I'm not the type of member who will give a straight answer, so please expect my how-to and posts to be very wordy. I want fellow members to understand what they are doing, not just tell them what they are doing (teach people how to fish, not just give them fish - so to speak).

Sent from my LG-D855 using XDA Free mobile app
Yeah i saw that solution but the kdz extracte thread is not that detailed ...tnx tho

N00R28 said:
Sent from my LG-D855 using XDA Free mobile app
Yeah i saw that solution but the kdz extracte thread is not that detailed ...tnx tho
Click to expand...
Click to collapse
Hi @N00R28,
I agree. That's why I wrote a detailed version of it in my how-to guide.

Sent from my LG-D855 using XDA Free mobile app
Hey,tnx but i will wait for an easier solution ,i would like to do the complicated way as its fun to do but i have exams and dont have much time ,so im gonna wait for something fast and easy :
But may i ask why these problems with lg g3 lollipop?all nexus and Samsung devices r easier and been there since the lunch of lollipop,even rooting g3 was a pain untill last week

N00R28 said:
Sent from my LG-D855 using XDA Free mobile app
Hey,tnx but i will wait for an easier solution ,i would like to do the complicated way as its fun to do but i have exams and dont have much time ,so im gonna wait for something fast and easy :
But may i ask why these problems with lg g3 lollipop?all nexus and Samsung devices r easier and been there since the lunch of lollipop,even rooting g3 was a pain untill last week
Click to expand...
Click to collapse
The explanation is in my how-to thread, Page 1.
I created an easy solution already as well, it's in my how-to thread. I created a script called "Imageprep". It only requires typing a single command in the Terminal. You must have not read the guide fully so you might have missed it. Understandable because you said you have exams.

Sent from my LG-D855 using XDA Free mobile app
Ohh cool ,tnx will check it out tomorrow

N00R28 said:
Hey ,i got the same problem ,just rooted my d855 and i want to flash a custom recovery so i can install xposed ,but after flashify reboots the device i get the same message...plz reply me if u found a solution
Click to expand...
Click to collapse
I was able to decipher the parts I needed in that thread. see my first post for the solution I used.

lordzouga said:
I was able to decipher the parts I needed in that thread. see my first post for the solution I used.
Click to expand...
Click to collapse
Very good, @lordzouga.
This is the reason why as much as possible, I explain the logic and force other members to understand it first. It makes the process easier for them because they know what they are doing.

The method worked perfectly after i bricked my device for the 1st time (was flashing the wrong recovery)after it worked i noticed most of the apps i need dont run on lillipop (due to devs not upgrading the apps to run with ART) so i downgraded to kitkat ......tnx alot for ur help

Thanks, this method worked perfectly.
Sent from my LG-D855 using Tapatalk

Totally bricked my phone with these instructions Won't turn on anymore. Tried everything...only shows a trinagle if I connect to usb without battery.

Super easy to use thank you buddy:d
SUPER EASY TO USE THANK YOU BUDDY
Please explain about sharpening what it actually do ?? what difference it makes..??
lordzouga said:
HI everyone.
Today, I managed to root my LG G3(D855) that is on the Lollipop version(OTA update).
The reason for this root was to flash the cyanogenMod 12 rom. I found out that I needed a bump'd twrp recovery image which I got from this page:
I tried using flashify to flash this image which flashify claims was a success but when I try to boot into recovery, it gives me a "Secure boot error" message.
does the same methods that apply for flashing custom recovery in android 4.4.2 on LG G3 not apply to Lollipop versions?
if I do a battery pull and boot up the device normally, the device seems to work alright but I can't boot into recovery.
So, please I need help as I want to install this CM12. it bothers me a lot that my nexus 7 seems faster than my G3
-- Problem Solved---
I was able to fix this problem and booting into a custom recovery by going through this thread: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
Here are the files I used:
"aboot.img" from a kitkat D855 stock rom. (here is the one I used https://docs.google.com/file/d/0B7fkQwhNpU7YNTdfZUQyZlQzLTA)
oversharpening fix flashable zip (here is the one I used http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648 used the latest version at the time of posting.)
a bump'd twrp recovery image for D855 from here: http://downloads.codefi.re/thecubed/lg_g3/bump/
kikat bootstack from here for D855: https://www.androidfilehost.com/?fid=95916177934540501
after getting all these files, move it to the root folder of your SD card.
attempt the process below at your own risk
Here is how I used the files:
I first used flashify (download from play store) to install the bump'd twrp recovery.img.
Then using android terminal emulator (download from play store) I ran this command
Code:
su [b](no need to retype this if you did not exit from the previous Android Terminal session)[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/lollipop-aboot.img [b](this makes a backup to your Internal Storage)[/b]
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](writes “zeroes” to the partition to “wipe” it out)[/b]
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](flashes the Kitkat version aboot.img to the aboot partition)[/b]
from this post: http://forum.xda-developers.com/showpost.php?p=59353812&postcount=44
I then reBooted my device into recovery mode which of course now has become TWRP recovery.
in the twrp recovery I flashed in the oversharpening fix.zip file (I was prompted during the installation to choose a sharpening level, I chose 5. this value doesn't have anything to do with the recovery process, we just need it to bump the lollipop boot.img)
After that, I flashed in the Kitkat boot stack and then rebooted my device.
that's it. I am on CM 12 now. Good luck.
and of course, credit goes to this user: @topet2k12001. He is a G3 superhero.
Click to expand...
Click to collapse

The reason why recovery wont load if you rooted using LG's lollipop firmware is because they patched the hack that bypasses the Security check. You need to downgrade to kitkat or keep on Lg's lollipop

χχ

My G3 does not start up
lordzouga said:
HI everyone.
Today, I managed to root my LG G3(D855) that is on the Lollipop version(OTA update).
The reason for this root was to flash the cyanogenMod 12 rom. I found out that I needed a bump'd twrp recovery image which I got from this page:
I tried using flashify to flash this image which flashify claims was a success but when I try to boot into recovery, it gives me a "Secure boot error" message.
does the same methods that apply for flashing custom recovery in android 4.4.2 on LG G3 not apply to Lollipop versions?
if I do a battery pull and boot up the device normally, the device seems to work alright but I can't boot into recovery.
So, please I need help as I want to install this CM12. it bothers me a lot that my nexus 7 seems faster than my G3
-- Problem Solved---
I was able to fix this problem and booting into a custom recovery by going through this thread: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
Here are the files I used:
"aboot.img" from a kitkat D855 stock rom. (here is the one I used https://docs.google.com/file/d/0B7fkQwhNpU7YNTdfZUQyZlQzLTA)
oversharpening fix flashable zip (here is the one I used http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648 used the latest version at the time of posting.)
a bump'd twrp recovery image for D855 from here: http://downloads.codefi.re/thecubed/lg_g3/bump/
kikat bootstack from here for D855: https://www.androidfilehost.com/?fid=95916177934540501
after getting all these files, move it to the root folder of your SD card.
attempt the process below at your own risk
Here is how I used the files:
I first used flashify (download from play store) to install the bump'd twrp recovery.img.
Then using android terminal emulator (download from play store) I ran this command
Code:
su [b](no need to retype this if you did not exit from the previous Android Terminal session)[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/lollipop-aboot.img [b](this makes a backup to your Internal Storage)[/b]
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](writes “zeroes” to the partition to “wipe” it out)[/b]
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](flashes the Kitkat version aboot.img to the aboot partition)[/b]
from this post: http://forum.xda-developers.com/showpost.php?p=59353812&postcount=44
I then reBooted my device into recovery mode which of course now has become TWRP recovery.
in the twrp recovery I flashed in the oversharpening fix.zip file (I was prompted during the installation to choose a sharpening level, I chose 5. this value doesn't have anything to do with the recovery process, we just need it to bump the lollipop boot.img)
After that, I flashed in the Kitkat boot stack and then rebooted my device.
that's it. I am on CM 12 now. Good luck.
and of course, credit goes to this user: @topet2k12001. He is a G3 superhero.
Click to expand...
Click to collapse
Please help!!! I followed your instructions and as i powered off my phone, now it does not boot up....can't even go to download mode.... please help!!

paragxx said:
Please help!!! I followed your instructions and as i powered off my phone, now it does not boot up....can't even go to download mode.... please help!!
Click to expand...
Click to collapse
Be careful with this thread, it will brick your phone. On the safe side make sure you remove laf partition and fastboot is working. I got mine bricked.

Does it work for Android 5.0 Lollipop or only Android 4.4 Kitkat?

LG Mobile Support Tool won't download software.

I'm having problems with the LG Mobile Support Tool. When I try "Upgrade recovery" it gets stuck at "Downloading software..."
It starts downloading fast, but after it gets about 30% or so, the download speed drops to nil. My internet is stable and fast. According to NetBalancer, the LG tool starts downloading at a steady 3mb/s, and then drops to short bursts of 50-150kb/sec. I'm not having any connectivity issues with other programs.
I let it keep going earlier today for almost 4 hours. It got to about 60% and then the tool crashed.
There's been a couple of times it said something like "Please check your internet connection, then press retry." The internet connection is fine, and clicking retry will bring it back up to full speed for a few minutes before it slows again.
What can I do?

What version of Windows are you using?
---------- Post added at 04:16 PM ---------- Previous post was at 04:09 PM ----------
Please don't post about the same problems in two different threads. I'm guessing since you using Volume Up to get into Download mode that you have a VK810 variant of the G Pad 8.3, correct?
If so, try one of the KDZs in my signature for the VK810.4G with LG Flash Tool 2014 (Google for it on XDA). That way you don't have to have a tool re-download the KDZ every time you attempt to recover.
If you want root and custom recovery, it's easiest to get both with the 11A KDZ, then flash my ROM in my signature with the latest TWRP v2.8.7.0. If you just want the latest stock unrooted, download the 36B KDZ.
If you don't have the VK810.4G, don't use the KDZs I link to.

What version of Windows are you using?
Click to expand...
Click to collapse
I am using Windows 7 Ultimate 64-bit
...you have a VK810 variant of the G Pad 8.3, correct?
Click to expand...
Click to collapse
Yes, I have the VK810.4G
Please don't post about the same problems in two different threads.
Click to expand...
Click to collapse
I wasn't sure if this should be considered a new problem, or a continuation of the other. But, I can see how that would split people's attention. My bad.
I will try your steps, and let you know how it goes.

Ok, I succesfully got TWRP and 4.2.2 w/root.
Now I have another problem...
When I flash ViKtory Rom and SuperSU, it will not boot. It just gets stuck at the red Verizon screen.
You mentioned that in your ViKtory rom thread:
5.2.2. One user has verified that on their VK810, that once they flash any version of SuperSU.zip that they've tried, including 2.46 and 2.48 beta, the ROM will not boot. You're ONLY recourse is to get into Download mode and use "LG Flash Tool 2014" to Flash the 35A_08 KDZ, and root it using @Hnk1's thread [VK810][ROOT][Lollipop][5.02] No downgrade required.
Click to expand...
Click to collapse
After flashing, I lose the custom recovery and it boots to 5.0.2 without root. None of the root methods in Hnk1's thread succeeded in rooting...
I did this successfully about 6 months ago, so I know it's possible.
EDIT: I just realized that you said to flash the 35A KDZ, and I used the 36B KDZ. I'll download the 35A one and see if I have better luck rooting then.

SlickStretch said:
Ok, I succesfully got TWRP and 4.2.2 w/root.
Now I have another problem...
When I flash ViKtory Rom and SuperSU, it will not boot. It just gets stuck at the red Verizon screen.
You mentioned that in your ViKtory rom thread:
After flashing, I lose the custom recovery and it boots to 5.0.2 without root. None of the root methods in Hnk1's thread succeeded in rooting...
I did this successfully about 6 months ago, so I know it's possible.
EDIT: I just realized that you said to flash the 35A KDZ, and I used the 36B KDZ. I'll download the 35A one and see if I have better luck rooting then.
Click to expand...
Click to collapse
Re: 35A versus 36B, I just haven't updated the OP. Actually these days I recommend the 11A KDZ because:
1. 11A through 24B can be rooted easily with the Stump app in brute force mode.
2. 11A is 4.2.2, so the aboot (bootloader) doesn't need downgraded prior to installing the initial Loki'd TWRP v2.7.0.1.
Did you upgrade to TWRP v2.8.7.0 before flashing the ROM and SuperSU.zip? Flashing KDZs always returns your device to complete unrooted stock just like from the factory. You should always use "CSE" mode of LG Flash Tool 2014. "Normal" mode doesn't wipe Data or Internal Storage, but especially if downgrading, you can expect that to cause problems.
35A is just as hard to root as 36B. I wrote that tip in the OP after I thought @Hnk1 's method was more easily reproducible. Sorry for the runaround and out of date directions, but you should go with the 11A KDZ.
If you had upgraded TWRP to v2.8.7.0 before flashing my ROM and SuperSU.zip and still had problems booting, you can try wiping Cache and Dalvik again (after flashing), but I don't expect that to work. You can also use CWM Recovery (just flash CWM from TWRP). There's a thread for VK810 CWM on here plus I think I have it in my VK810 section on Android File Host as a mirror, and wipe and flash everything from there. Like I said, that's only if you tried flashing from the latest TWRP v2.8.7.0 (available in these sections) for the VK810 and still had this problem. If you do switch to CWM, you can switch back after flashing the ROM for backups and such.
Good luck!

Success!
Success! :laugh: I am now running ViKtory rom! It's debloated and rooted and sweet! Thank you so much for your help. I believe this is the 2nd time you've saved my tablet!
One last question: Do I need to flash aboot to access recovery with your rom?
Here's all the steps I took on my path to success, just in case anybody finds it helpful.
===============================================================================
To return to stock, unbrick, or prepare to root.
===============================================================================
1: Open LG Flash Tool 2014
2: Use the following settings:
- Select Type: CDMA
- PhoneMode: DIAG
- Reset time: 33000
- Select KDZ file: Use newest to go back to stock unrooted
Use 11A if planning to root/twrp
- Upgrade with CSMG Client: Normal Flash will not wipe, SCE Flash will wipe
3: LG Flash Tool will open LG Mobile Update tool. If an error window pops up
saying "Cannot connect to server..." Ignore it. DO NOT CLICK OK! It will run
it's course and the tablet will reboot.
4: Done with that.
===============================================================================
To root
===============================================================================
Use Stump Root app. (Bruteforce)
===============================================================================
To install TWRP custom recovery
===============================================================================
1: Connect tablet in debugging mode.
2: Navigate to where loki_flash and twrp.lok is.
3: Open cmd from this location.
4: Run the following commands:
4a: adb push loki_flash /data/local/tmp/loki_flash
4b: adb push twrp.lok /data/local/tmp/twrp.lok
4c: adb shell
4d: su
4e: cd /data/local/tmp/
4f: chmod 777 loki_flash
4g: ./loki_flash recovery /data/local/tmp/twrp.lok
4h: exit
4i: exit
4j: adb reboot recovery
The tablet should now boot to TWRP
===============================================================================
To install ViKtory rom
===============================================================================
1: Boot to TWRP recovery v2.8.7.0
2: wipe system, data, cache, dalvik and internal storage DO NOT REBOOT
3: Go to Mount > enable MTP
4: Copy ViKtory rom and SuperSU zip files to tablet (and debloat scripts if
desired.)
5: Install zip files (may have to switch between IMG and ZIP to see them.)
6: Reboot.
ALL DONE!

SlickStretch said:
Success! :laugh: I am now running ViKtory rom! It's debloated and rooted and sweet! Thank you so much for your help. I believe this is the 2nd time you've saved my tablet!
One last question: Do I need to flash aboot to access recovery with your rom?
Click to expand...
Click to collapse
Great! You're welcome, I like hearing about successful device adventures.
Yes, the exact directions what I have at the bottom of the first post. I'm unfortunately not knowledgeable enough to solve the boot into TWRP problem with the Lollipop bootloader / getting Lollipop to boot without he Lollipop bootloader on the VK810, although @xdabbeb gave me some ideas to try if I ever find the time.

LG Support tool get stuck at 60% installing new firmware/KDZ files to reset LG ms323 phone to factory settings.
What is the solution to this problem?

Installed twrp, but can't get into it

I did the following
1. Downgraded to V30b-EUR-XXX with LGUP. Went smooth.
2. Rooted phone sucessfully with kingroot.
3. Got a shell with "adb shell"
4. "su"
5. Filled the recovery-partition with zeros from /dev/zero with dd
6. Installed twrp3.2.3-0 with dd on recovery-partition
When I boot into Marshmallow, all is fine. When I boot into recovery, I'm informed about a necessary factory reset. I say "Yes" both times, then the LG Logo and some tiny text is displayed and afterwards the screen goes dark. The LED is blinking blue and red; the only way out of this is to remove the battery.
If I do a factory reset from within marshmallow, the result is the same.
What can I do now? Should I flash a stock recovery with dd? But where to get it? Or should I flash an older version of twrp?

Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.

NetDog75 said:
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
Click to expand...
Click to collapse
Excuse me, but I'm not able to decipher that. What is flashify? What means "on the ROM of course"? Can you give more information please.

- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.

NetDog75 said:
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
Click to expand...
Click to collapse
Don't had to downgrade, because I was in V30b. Got root, installed flashify and flashed twrp - the first time 3.2.3, then 2.8.0. Same result as before.
From what version of android did you install what version of twrp?

Hi,
I use the twrp3.2.3 and no problem.
I'm not expert, I just can recommend some steps...
Maybe good idea to flash again the stock ROM. You can find here on the forum many step by step guide for this. ( tools and steps )
It seems your phone recovery partition is not OK....
I have no more idea...

@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. Since you were connected via adb was it not possible to use fastboot? Flashing the recovery via that should(?) have also worked.
If the recovery partition is messed up you might have to start over. Not sure though as I haven't experienced that problem.
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy

marcdw said:
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. S
Click to expand...
Click to collapse
It's the same partition where I flashed twrp, so the zeros are already overwritten with something else ...
Seriously: Zeroing the partition before writing to it was mentioned in a thread about the installation of a "bumped" recovery.

NetDog75 said:
Hi,
I use the twrp3.2.3 and no problem.
Click to expand...
Click to collapse
OK, that is the version I used also. What android version was installed when you flashed the recovery? Mine is stock V30b.

Hi,
I'm not sure, because I changed to 8.1 (oreo).
Maybe V30N.....

I am having the same problem. There is no "unlock bootloader" in the developer options, and adb reboot bootloader just starts into android again. I might have to reflash the stock firmware, but nowhere in the install instructions for twrp does it say that you first have to unlock the bootloader, and nowhere does it even mention that there might not be such an option. This is genuinely strange.