[ROOT][IOroot] Root your LG G Pro 2 [F350][Woohoo!]

Search This thread

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875

IOroot
IOroot was originally a Windows script to root the LG G2 on 4.2.2 made by IOMonster... based on the original adb backdoor found by GiantPune and later posted by jcase.
The script has grown to support various other LG devices on Android 4.0 - 4.4.2... 4.4.2 kk_root.zip by autoprime. Current IOroot25r1 by autoprime.
Supported devices include LG Optimus G, G2, G3, G Pro, G Pro 2, G Flex and G Pad just to name a few.

4.4.2 root will NOT work for you if you cannot get into the stock recovery menu w/the "adb reboot recovery" command.
Check the supported devices list below. You may have to downgrade to 4.2.2 or below and root that instead.
Or your device may not be supported at all. Again.. check the supported device list below.


Current Version - IOroot25 refresh 1

Download IOroot zip, extract and run script to root. ADB must be enabled (USB Debugging ON).
Click the button below for IOroot device support list, manual and automated root and other info.


Device Model and Firmware Supported List:


LG Optimus G - all 4.2.2 and 4.4.2

LG G2:
AT&T D800 - D80010d/D80010o/4.4.2
D801 - TMO(all 4.2.2 // No 4.4.2 support), CLR(all 4.2.2 // 4.4.2 ??), WND(all 4.2.2 // 4.4.2 ??), VTR(all 4.2.2 // 4.4.2 ??)
D802 - all 4.2.2 and 4.4.2
D803 - all
D805 - all
D806 - all
F320K - Shipping 4.2.2 ROM/F320K20a/20f // 4.4.2 ??
F320L - Shipping 4.2.2 ROM/F320L20b/20e // 4.4.2 ??
F320S - Shipping 4.2.2 ROM/F320S20a/20g // 4.4.2 ??
Sprint LS980 - All 4.2.2 and 4.4.2
Verizon VS980 - All 4.2.2 and 4.4.2

LG G Flex:
F340 series - All 4.2.2 // 4.4.2 ??
D950 - All 4.2.2 // No 4.4.2 support
D955 series - All 4.2.2
D958 series - All 4.2.2 // No 4.4.2 support
D959 - All 4.2.2 // No 4.4.2 support
LS995 - All 4.2.2 and 4.4.2

LG G Pro - All 4.4.2 Only

LG G Pro 2:
F350 series - Shipping ROM // 4.4.2 ??
D838 - Shipping ROM // 4.4.2 ??

LG G Pad - 4.4.2 Only

LG G3
F400 Series - Shipping ROM


Manual Root Method:

Code:
[B][SIZE="2"]Windows Drivers:[/SIZE][/B]
[I]Verizon Drivers - [URL="http://bit.ly/1ibRvc3"]HERE[/URL]
Drivers for everyone else - [URL="http://bit.ly/18EPHZN"]HERE[/URL][/I]

[B]4.4.2 Manual Root:[/B]
[SIZE="1"]
Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode. 
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]

[B]1. adb devices[/B]
[B]2. adb reboot recovery[/B]
(when booted in recovery, select: 'apply update from adb' with power button)
[B]3. adb sideload kk_root.zip[/B]

reboot when zip finishes flashing. done.




[B]4.2.2 Manual Root:[/B]
[SIZE="1"]Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode. 
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]

copy/paste commands below.. hitting enter/return after each line. 
Linux/Mac users may have to enter ./ before adb on each line. 
Example: ./adb push g2_security /sdcard/g2_security

[SIZE="1"][B]1:[/B] [B][I]adb devices[/I][/B]
(make sure it sees your device; if "offline" turn on phone/unlock and accept RSA key prompt)
[B]2:[/B] Choose next line based on model and firmware version:
AT&T D80010d (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
AT&T D80010o/10q: [B][I]adb push ytiruces_1a_att /sdcard/ytiruces_1a[/I][/B]
KT F320k (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
KT F320K20a/20f (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
LGU F320L (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
LGU F320L20b/20e (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
D802(T) (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
D803 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
D805 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
D806 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
SKT F320S (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
SKT F320S20a/20g (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
Sprint LS980ZV7/ZV8: [B][I]adb push g2_security_spr /sdcard/g2_security[/I][/B]
Sprint LS980ZVA (OTA): [B][I]adb push ytiruces_1a_ls980 /sdcard/ytiruces_1a[/I][/B]
T-Mobile D80110c (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
T-Mobile D80110g (OTA): [B][I]adb push ytiruces_1a_tmo /sdcard/ytiruces_1a[/I][/B]
Verizon VS98010B (Shipping ROM): [B][I]adb push g2_security_vzw /sdcard/g2_security[/I][/B]
Verizon VS98011A/12B (OTA): [B][I]adb push ytiruces_1a_vzw /sdcard/ytiruces_1a[/I][/B]
Videotron D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
Wind D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]

F340-Series (4.2.2): [B][I]adb push ytiruces_1a_F340JB /sdcard/ytiruces_1a[/I][/B]
D950 (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D955-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D956-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D958-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
D959 (4.2.2): [B][I]adb push ytiruces_sumtz /sdcard/ytiruces_sumtz[/I][/B]
LS995 (4.2.2): adb push ytiruces_1a_ls995 /sdcard/ytiruces_1a

F350K/L/S (4.4.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]

[B]********************************************************
This next depends on your computer/phone model...

USB Connection Mode needs to be toggled.
Ways to do this are listed below...

a. Unplug usb cable from phone then re-plug.
b. Toggle USB mode from Charge to MTP back to Charge
c. Toggle USB mode from Ethernet to MTP back to Ethernet (VZW users)
********************************************************[/B]

[B]3:[/B] [B][I]adb shell[/I][/B]
(you should now see a # instead of a $. # = root)
[B]4:[/B] [B][I]exit[/I][/B]
[B]5:[/B] [B][I]adb shell "mount -o remount,rw /system"[/I][/B]
[B]6:[/B] [B][I]adb push su /system/xbin/su[/I][/B]
[B]7:[/B] [B][I]adb push su /system/xbin/daemonsu[/I][/B]
[B]8:[/B] [B][I]adb push install-recovery.sh /system/etc/install-recovery.sh[/I][/B]
[B]9:[/B] [B][I]adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"[/I][/B]
[B]10:[/B] [B][I]adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"[/I][/B]
[B]11:[/B] [B][I]adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.sh"[/I][/B]
[B]12:[/B] [B][I]adb shell "sync;mount -o remount,ro /system"[/I][/B]
[B]13:[/B] [B][I]adb install Superuser.apk[/I][/B]

REBOOT AFTER STEP #13
[/SIZE]





v

Automated .bat/.sh Directions:


Download latest ioroot.zip. Unzip and run bat/sh. Follow the onscreen instructions.
4.4.2 is rooted through stock recovery. Once in recovery use volume keys to select "update with adb" then hit the power button... then continue with the script.

Windows:
Download and install proper ADB driver. Enable USB Debugging. Double-click on root.bat

Linux:
cd into /IOroot/ folder
chmod +x root.sh
./root.sh

Mac:
cd into /IOroot/mac/ folder
chmod +x root.sh
./root.sh



Windows Drivers:
Verizon Drivers - HERE
Drivers for everyone else - HERE


EFS Backup:

EFS is automatically backed up for all 4.2.2(and below) devices.
EFS is backed up into the ioroot folder on your computer. If running ioroot on mac.. it'll be in the ioroot/mac folder.
Store backed up EFS partitions somewhere safe.

4.4.2 devices will not have automatic EFS backup.
Use the commands below to backup EFS.

Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img

Not Working?

If you are on 4.4.2 and cannot get into a stock recovery menu with adb reboot recovery then you CANNOT root 4.4.2 on your device.
You must downgrade to 4.2.2 with stock tot or kdz, retain root and take OTA updates to 4.4.2
OR
downgrade to 4.2.2 and install custom recovery and manually upgrade your way to 4.4.2 by flashing a KK rom + modem.


Make sure to read all of the scripts on-screen text or you may miss something. Hitting a button when it's not time to do so or not reading everything on screen can cause problems. Make sure the phone is unlocked with the screen on whenever possible as well.

If the scripts fail for you check out the manual directions further down the page. The manual method is only a few ADB commands and can help if I've messed up in the scripts somewhere... or if the scripts just don't seem to be working for you. Taking it one step at a time manually almost always results in success.


Still not working?
I need the output from the 4 ADB commands below along with IOroot version and if it was on Windows/Linux/Mac. Any errors you come across would help as well...
adb shell "getprop ro.product.model"
adb shell "getprop ro.build.target_operator"
adb shell "getprop ro.lge.swversion"
adb shell "getprop ro.build.fingerprint"


What's Next?

Confirm full root with rootchecker. ( @joeykrim )
Support a great dev by buying the Pro version.

If you only did the "temp root/adb only root" then you can confirm root by opening adb shell and seeing # instead of $.

For custom recovery(TWRP/CWM) on 4.2.2 and below run FreeGee ( @Shelnutt2 )
Check out the FreeGee donate version if you want to support a great dev.

For custom recovery(TWRP) on 4.4.2 run AutoRec by @Cloudyfa for a safe and easy install.


IOroot25r1 Download: HERE


Changelog:

v25r1: Fixed LG OG EFS backup. Added D802T 4.2.2 support. Script checks for 4.4.2 first. G3 supported.
v25: Added root for 4.4.2 devices. Now works on most LG 4.4.2 devices. Thanks to @jarari2 for the idea to go through stock recovery.
v24: added support for G2 D800 10q, G Flex D956 and G Pro 2 F350K/L/S(thanks to @hkfriends for confirming ioroot method still works)
v23: added support for AT&T G Flex D950 10c.
v22: added support for TMO D959 G Flex. Tweaked scripts EFS backup... hopefully no more errors.
v21: added support for Sprint LS980ZVA update. Added EFS backup support.
v20: added support for all D802/D805/D806. Updated all scripts. Added LG Optimus G and LG G Flex support. SuperSu now installed in /system.
v19: added support for MORE F320 4.4 firmware. Added Singtel D802 support. Linux/Mac script fixes.
v18: added support for MORE F320 4.4 firmware. Added Vodafone(VDF) carrier(should work with at least Shipping ROM). Tweaked scripts.
v17: added F320* 4.4 KitKat root. Added SuperSu.4.4 users must reboot after running root script(mac/linux)
v16: added TMO 10g root and "SCA" root(D802/D805)
v15: added ATT 10o root.
v12: added Verizon 12B root.
v11: added linux support and Sprint LS980 root(both thanks to @Shelnutt2)


y u no hit thanks button?
 
Last edited:

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875
Success!! using manual method, though.
Thanks

nice. did you use manual method because the bat failed? or you just preferred manual method? just curious if the script failed.. because it should be doing exactly what the manual method is.

can you(or anyone else with a rooted g pro 2) pull your aboot partition and upload it? with the commands below it'll put the aboot.img on your internal sdcard.

adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
 

magicbbird

Member
Apr 15, 2005
44
1
nice. did you use manual method because the bat failed? or you just preferred manual method? just curious if the script failed.. because it should be doing exactly what the manual method is.

can you(or anyone else with a rooted g pro 2) pull your aboot partition and upload it? with the commands below it'll put the aboot.img on your internal sdcard.

adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img

I use the manual method because somehow I couldn't cd to the ioroot24 folder path, so I need to type out the full path for each action.

I will try to get that file for you. I just root but never learn programming, what that file does for you?
 

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875
I use the manual method because somehow I couldn't cd to the ioroot24 folder path, so I need to type out the full path for each action.

I will try to get that file for you. I just root but never learn programming, what that file does for you?

it will determine if the bootloader can be exploited so custom roms can be flashed on G Pro 2
 

magicbbird

Member
Apr 15, 2005
44
1
it will determine if the bootloader can be exploited so custom roms can be flashed on G Pro 2

Please excuse my newbie question: I cannot transfer that file to desktop. I can see it with ES file explorer, but cannot copy/move to other places. I use mac, and use Android file transfer desktop program. It does not see that file.
 

Hendrickson

Senior Member
Aug 24, 2008
988
713
Denia, Spain
www.youtube.com
I had issues, permission denied on the system folders. I managed to root an easy way. I've uploaded a vid on youtube of how I did it for newbs http://www.youtube.com/watch?v=s2sKkFuv5ew&feature=youtu.be

Now all I need is to get xposed installer to run and CWM or TRWP recovery and I'm set!

There are no recovery firmwares uploaded yet from LG so I'm not doing much as to risk a soft brick would be a set back. LG have yet to publish the KDZ files.
 

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875
Please excuse my newbie question: I cannot transfer that file to desktop. I can see it with ES file explorer, but cannot copy/move to other places. I use mac, and use Android file transfer desktop program. It does not see that file.

can you email it to yourself or something thru es file explorer? or send to your computer over bluetooth? not sure why it wouldnt be showing up on android file transfer.
 

ahmadcentral

Senior Member
Oct 28, 2011
219
30
London
Thanks for the guide.


Now there is small matter of getting LTE working on this Korean version.
As the phone thinks its roaming when out of Korea, and therefore defaults to WCDMA/GSM and blocks the LTE option.
There is pretty much no way to enable LTE. Does anyone have any ideas?
 

Epix4G

Senior Member
Sep 14, 2011
2,665
1,028
phoenix
Is loki patched ? The g2 is patched but they can downgrade aboot ? Will you be able to have a custom recovery? ?? Too early to know ?

Sent from my SM-N900P using Xparent BlueTapatalk 2
 

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875
Is loki patched ? The g2 is patched but they can downgrade aboot ? Will you be able to have a custom recovery? ?? Too early to know ?

Sent from my SM-N900P using Xparent BlueTapatalk 2

loki is patched/blocked on F350.
 
Last edited:

moviejimmy

Member
Nov 13, 2012
24
0

IOroot
Root your LG G Pro 2 without any funny business. Original IOroot thread for LG G2 HERE.
Thanks to @hkfriends for confirming ioroot method still works on F350 G Pro 2!
Currently supports the LG G Pro 2 F350K, F350L and F350S models
Also supports the LG Optimus G, LG G2 and G Flex.
Current Version - IOroot24

As of IOroot21... EFS backup has been added to the root script. EFS is backed up after fully rooting.. the last step in the script.
EFS is backed up into the ioroot folder on your computer. If running ioroot on mac.. it'll be in the ioroot/mac folder.
This will hopefully reduce future issues where EFS is corrupted and the user never made a backup of EFS.
Store backed up EFS partitions somewhere safe.



Directions:
Confirm your device is supported below.
Download latest IOroot zip and extract it.
Set phone in USB Debugging mode.
Set USB mode to Charging only(this may vary based on model).
Run script and follow the onscreen instructions.

Windows: Download and install proper ADB driver. Double-click on root.bat
Linux: cd into IOroot folder -> chmod +x root.sh -> sh ./root.sh
Mac: cd into /IOroot/mac folder -> chmod + x root.sh -> ./root.sh


Windows Drivers: HERE


Device Model and Firmware Supported:

LG Optimus G - All

LG G2:
D800 - D80010d/D80010o/D80010q
D801 - TMO, CLR, WND, VTR [all 4.2.2. firmware. 4.4.2 not yet.]
D802 - all 4.2.2 firmware. 4.4.2 not yet.
D803 - all 4.2.2 firmware. 4.4.2 not yet.
D805 - all 4.2.2 firmware. 4.4.2 not yet.
D806 - all 4.2.2 firmware. 4.4.2 not yet.
F320K (Shipping ROM)
F320K - F320K20a/20f
F320L (Shipping ROM)
F320L - F320L20b/20e
F320S (Shipping ROM)
F320S - F320S20a/20g
Sprint LS980 - All
Verizon VS980 - All

LG G Flex:
F340 series - All
AT&T D950 - All
D955 series - All
D956 series - All
D958 series - All
D959 series - All
Sprint LS995 - All

G Pro 2
F350K/L/S - All firmware as of March 04, 2014



Not Working?
Make sure to read all of the scripts on-screen text or you may miss something. Hitting a button when it's not time to do so or not reading everything on screen can cause problems. Make sure the phone is unlocked with the screen on whenever possible as well.

If the scripts fail for you check out the manual directions further down the page. The manual method is only a few ADB commands and can help if I've messed up in the scripts somewhere... or if the scripts just don't seem to be working for you. Taking it one step at a time manually almost always results in success.


Still not working?
I need the output from the 4 ADB commands below along with IOroot version and if it was on Windows/Linux/Mac. Any errors you come across would help as well...
adb shell "getprop ro.product.model"
adb shell "getprop ro.build.target_operator"
adb shell "getprop ro.lge.swversion"
adb shell "getprop ro.build.fingerprint"


WITHOUT POSTING ALL OF THE ABOVE INFO I WILL NOT BE ABLE TO HELP.
ONLY THE MOST RECENT VERSION OF IOROOT IS SUPPORTED!!


We be chillin' on IRC. Join us in #lg-g2 on Freenode.
If you're new to IRC, click here http://webchat.freenode.net/?channels=#gflex and it'll connect you to the channel.



What's Next?
Confirm full root with rootchecker. ( @joeykrim )
Support a great dev by buying the Pro version.

If you only did the "temp root/adb only root" then you can confirm root by opening adb shell and seeing # instead of $.


Manual Root Method:
Code:
[SIZE="1"]
Download and extract the latest IOroot.zip
Enable USB Debugging.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]

copy/paste commands below.. hitting enter/return after each line. 
Linux/Mac users may have to enter ./ before adb on each line. 
Example: ./adb push g2_security /sdcard/g2_security

[SIZE="1"][B]1:[/B] [B][I]adb devices[/I][/B]
(make sure it sees your device; if "offline" turn on phone/unlock and accept RSA key prompt)
[B]2:[/B] Choose next line based on model and firmware version:
F350K/L/S (4.4.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]

[B]********************************************************
This next depends on your computer/phone model...

USB Connection Mode needs to be toggled.
Ways to do this are listed below...

a. Unplug usb cable from phone then re-plug. (confirmed for G Pro 2)
b. Toggle USB mode from Charge to MTP back to Charge
c. Toggle USB mode from Ethernet to MTP back to Ethernet (VZW users)
********************************************************[/B]

[B]3:[/B] [B][I]adb shell[/I][/B]
(you should now see a # instead of a $. # = root)
[B]4:[/B] [B][I]exit[/I][/B]
[B]5:[/B] [B][I]adb shell "mount -o remount,rw /system"[/I][/B]
[B]6:[/B] [B][I]adb push su /system/xbin/su[/I][/B]
[B]7:[/B] [B][I]adb push su /system/xbin/daemonsu[/I][/B]
[B]8:[/B] [B][I]adb push install-recovery.sh /system/etc/install-recovery.sh[/I][/B]
[B]9:[/B] [B][I]adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"[/I][/B]
[B]10:[/B] [B][I]adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"[/I][/B]
[B]11:[/B] [B][I]adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.sh"[/I][/B]
[B]12:[/B] [B][I]adb shell "sync;mount -o remount,ro /system"[/I][/B]
[B]13:[/B] [B][I]adb install Superuser.apk[/I][/B][/SIZE]

REBOOT AFTER STEP #13

Confirm root with [URL="http://xdaforums.com/showthread.php?t=927629"]rootchecker[/URL]. (joeykrim)







v


IOroot Download: HERE


Changelog:
v24: added support for G2 D800 10q, G Flex D956 and G Pro 2 F350K/L/S(thanks to @hkfriends for confirming ioroot method still works)
v23: added support for AT&T G Flex D950 10c.
v22: added support for TMO D959 G Flex. Tweaked scripts EFS backup... hopefully no more errors.
v21: added support for Sprint LS980ZVA update. Added EFS backup support.
v20: added support for all D802/D805/D806. Updated all scripts. Added LG Optimus G and LG G Flex support.
v19: added support for MORE F320 4.4 firmware. Added Singtel D802 support. Linux/Mac script fixes.
v18: added support for MORE F320 4.4 firmware. Added Vodafone(VDF) carrier(should work with at least Shipping ROM). Tweaked scripts.
v17: added F320* 4.4 KitKat root. Added SuperSu.4.4 users must reboot after running root script(mac/linux)
v16: added TMO 10g root and "SCA" root(D802/D805)
v15: added ATT 10o root.
v12: added Verizon 12B root.
v11: added linux support and Sprint LS980 root(both thanks to @Shelnutt2)

y u no hit thanks button?

No brainer! Many thanks! Used automatic. G Pro 2.
 

haared

Member
Jun 1, 2007
32
4
How to Flash back to stock using backed up EFS Back up?

My phone (LG G PRO2 F350S SKT) Model is not booting any more after rooting. I cannot enter in to recovery mode by using power and volume down buttons. Can somebody help me to get my phone boot back by using EFS back up files or any other method. I know that as on date there are no kdz files for my phone that is F350S SKT Model.
 

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875
My phone (LG G PRO2 F350S SKT) Model is not booting any more after rooting. I cannot enter in to recovery mode by using power and volume down buttons. Can somebody help me to get my phone boot back by using EFS back up files or any other method. I know that as on date there are no kdz files for my phone that is F350S SKT Model.

you were messing with system files after rooting or somethin? root alone would not softbrick the phone.

if you cannot boot into rom or recovery.. you must wait for tot or kdz to flash in download mode.
 

hkfriends

Senior Member
Aug 24, 2007
582
149
you were messing with system files after rooting or somethin? root alone would not softbrick the phone.

if you cannot boot into rom or recovery.. you must wait for tot or kdz to flash in download mode.


Exactly, rooting is only inject necessary binary files and grant permission where in needed...
softbrick more or less touching on boot partition or recovery, as when boot up, LG will has boot loader program to check around.

Up to now, no cutstom recovery yet or lokis by djrbliss.... if you still can get download mode, only choice is get TOT file and flash it over

I knew china website has these (L/K/S) TOTs already and required DLL, but it need to pay money unfortunately :(
 

moviejimmy

Member
Nov 13, 2012
24
0
There is another software update to the LG G Pro 2. I don't want to upgrade and it keeps annoying me and I cannot turn the notifications off. If I did upgrade, would I need to ROOT again?
 

l344364737

Member
Jun 27, 2010
17
8

IOroot
Root your LG G Pro 2 without any funny business. Original IOroot thread for LG G2 HERE.
Thanks to @hkfriends for confirming ioroot method still works on F350 G Pro 2!
Currently supports the LG G Pro 2 F350K, F350L and F350S models
Also supports the LG Optimus G, LG G2 and G Flex.
Current Version - IOroot24

As of IOroot21... EFS backup has been added to the root script. EFS is backed up after fully rooting.. the last step in the script.
EFS is backed up into the ioroot folder on your computer. If running ioroot on mac.. it'll be in the ioroot/mac folder.
This will hopefully reduce future issues where EFS is corrupted and the user never made a backup of EFS.
Store backed up EFS partitions somewhere safe.



Directions:
Confirm your device is supported below.
Download latest IOroot zip and extract it.
Set phone in USB Debugging mode.
Set USB mode to Charging only(this may vary based on model).
Run script and follow the onscreen instructions.

Windows: Download and install proper ADB driver. Double-click on root.bat
Linux: cd into IOroot folder -> chmod +x root.sh -> sh ./root.sh
Mac: cd into /IOroot/mac folder -> chmod + x root.sh -> ./root.sh


Windows Drivers: HERE


Device Model and Firmware Supported:

LG Optimus G - All

LG G2:
D800 - D80010d/D80010o/D80010q
D801 - TMO, CLR, WND, VTR [all 4.2.2. firmware. 4.4.2 not yet.]
D802 - all 4.2.2 firmware. 4.4.2 not yet.
D803 - all 4.2.2 firmware. 4.4.2 not yet.
D805 - all 4.2.2 firmware. 4.4.2 not yet.
D806 - all 4.2.2 firmware. 4.4.2 not yet.
F320K (Shipping ROM)
F320K - F320K20a/20f
F320L (Shipping ROM)
F320L - F320L20b/20e
F320S (Shipping ROM)
F320S - F320S20a/20g
Sprint LS980 - All
Verizon VS980 - All

LG G Flex:
F340 series - All
AT&T D950 - All
D955 series - All
D956 series - All
D958 series - All
D959 series - All
Sprint LS995 - All

G Pro 2
F350K/L/S - All firmware as of March 04, 2014



Not Working?
Make sure to read all of the scripts on-screen text or you may miss something. Hitting a button when it's not time to do so or not reading everything on screen can cause problems. Make sure the phone is unlocked with the screen on whenever possible as well.

If the scripts fail for you check out the manual directions further down the page. The manual method is only a few ADB commands and can help if I've messed up in the scripts somewhere... or if the scripts just don't seem to be working for you. Taking it one step at a time manually almost always results in success.


Still not working?
I need the output from the 4 ADB commands below along with IOroot version and if it was on Windows/Linux/Mac. Any errors you come across would help as well...
adb shell "getprop ro.product.model"
adb shell "getprop ro.build.target_operator"
adb shell "getprop ro.lge.swversion"
adb shell "getprop ro.build.fingerprint"


WITHOUT POSTING ALL OF THE ABOVE INFO I WILL NOT BE ABLE TO HELP.
ONLY THE MOST RECENT VERSION OF IOROOT IS SUPPORTED!!


We be chillin' on IRC. Join us in #lg-g2 on Freenode.
If you're new to IRC, click here http://webchat.freenode.net/?channels=#gflex and it'll connect you to the channel.



What's Next?
Confirm full root with rootchecker. ( @joeykrim )
Support a great dev by buying the Pro version.

If you only did the "temp root/adb only root" then you can confirm root by opening adb shell and seeing # instead of $.


Manual Root Method:
Code:
[SIZE="1"]
Download and extract the latest IOroot.zip
Enable USB Debugging.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]

copy/paste commands below.. hitting enter/return after each line. 
Linux/Mac users may have to enter ./ before adb on each line. 
Example: ./adb push g2_security /sdcard/g2_security

[SIZE="1"][B]1:[/B] [B][I]adb devices[/I][/B]
(make sure it sees your device; if "offline" turn on phone/unlock and accept RSA key prompt)
[B]2:[/B] Choose next line based on model and firmware version:
F350K/L/S (4.4.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]

[B]********************************************************
This next depends on your computer/phone model...

USB Connection Mode needs to be toggled.
Ways to do this are listed below...

a. Unplug usb cable from phone then re-plug. (confirmed for G Pro 2)
b. Toggle USB mode from Charge to MTP back to Charge
c. Toggle USB mode from Ethernet to MTP back to Ethernet (VZW users)
********************************************************[/B]

[B]3:[/B] [B][I]adb shell[/I][/B]
(you should now see a # instead of a $. # = root)
[B]4:[/B] [B][I]exit[/I][/B]
[B]5:[/B] [B][I]adb shell "mount -o remount,rw /system"[/I][/B]
[B]6:[/B] [B][I]adb push su /system/xbin/su[/I][/B]
[B]7:[/B] [B][I]adb push su /system/xbin/daemonsu[/I][/B]
[B]8:[/B] [B][I]adb push install-recovery.sh /system/etc/install-recovery.sh[/I][/B]
[B]9:[/B] [B][I]adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"[/I][/B]
[B]10:[/B] [B][I]adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"[/I][/B]
[B]11:[/B] [B][I]adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.sh"[/I][/B]
[B]12:[/B] [B][I]adb shell "sync;mount -o remount,ro /system"[/I][/B]
[B]13:[/B] [B][I]adb install Superuser.apk[/I][/B][/SIZE]

REBOOT AFTER STEP #13

Confirm root with [URL="http://xdaforums.com/showthread.php?t=927629"]rootchecker[/URL]. (joeykrim)







v


IOroot Download: HERE


Changelog:
v24: added support for G2 D800 10q, G Flex D956 and G Pro 2 F350K/L/S(thanks to @hkfriends for confirming ioroot method still works)
v23: added support for AT&T G Flex D950 10c.
v22: added support for TMO D959 G Flex. Tweaked scripts EFS backup... hopefully no more errors.
v21: added support for Sprint LS980ZVA update. Added EFS backup support.
v20: added support for all D802/D805/D806. Updated all scripts. Added LG Optimus G and LG G Flex support.
v19: added support for MORE F320 4.4 firmware. Added Singtel D802 support. Linux/Mac script fixes.
v18: added support for MORE F320 4.4 firmware. Added Vodafone(VDF) carrier(should work with at least Shipping ROM). Tweaked scripts.
v17: added F320* 4.4 KitKat root. Added SuperSu.4.4 users must reboot after running root script(mac/linux)
v16: added TMO 10g root and "SCA" root(D802/D805)
v15: added ATT 10o root.
v12: added Verizon 12B root.
v11: added linux support and Sprint LS980 root(both thanks to @Shelnutt2)

y u no hit thanks button?

The IOroot24 failed on my F350L, the firmware is F350L10g(someone said it also failed on F350S10g), I tried the ROOT.bat but got “device not found”, then I tried the manual methods but did not work ether, Here are what I got when I did the manual methods from the cmd windows.

C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb devices

List of devices attached

041f33f4d86974ce device





C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb push ytiruces_1a_kk /sdcard/ytiruces_1a

21 KB/s (288 bytes in 0.013s)



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell

shell@b1:/ $ exit

exit



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell "mount -o remount,rw /system"

mount: Operation not permitted



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb push su /system/xbin/su

failed to copy 'su' to '/system/xbin/su': Read-only file system



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb push su /system/xbin/daemonsu

failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb push install-recovery.sh /system/etc/install-recovery.sh

failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-only file system



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"

Unable to open /system/xbin/su: No such file or directory

Unable to open /system/xbin/su: No such file or directory




C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"

Unable to open /system/xbin/daemonsu: No such file or directory

Unable to open /system/xbin/daemonsu: No such file or directory




C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"

Unable to open /system/xbin/daemonsu: No such file or directory

Unable to open /system/xbin/daemonsu: No such file or directory




C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.

sh"

Unable to open /system/etc/install-recovery.sh: No such file or directory

Unable to open /system/etc/install-recovery.sh: No such file or directory




C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb shell "sync;mount -o remount,ro /system"

mount: Operation not permitted



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>adb install Superuser.apk

2015 KB/s (2558746 bytes in 1.240s)

pkg: /data/local/tmp/Superuser.apk

Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]



C:\Users\Administrator\Downloads\LG F350LSK ROOT\LG F350LSK ROOT>

is there any more information i can provide?
 

hkfriends

Senior Member
Aug 24, 2007
582
149
It seems that F350 S / L => after upgrade to v10G will failed to root (IOroot v2.4)

F350K is still in v10E, it is still able to root.
 

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,630
11,875
It seems that F350 S / L => after upgrade to v10G will failed to root (IOroot v2.4)

F350K is still in v10E, it is still able to root.

yes this is correct. the korean phones update too much... and i will not be keeping up with every single update.

the original F350 firmware is able to be rooted.. i most likely will not be supporting any others.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 33

    IOroot
    IOroot was originally a Windows script to root the LG G2 on 4.2.2 made by IOMonster... based on the original adb backdoor found by GiantPune and later posted by jcase.
    The script has grown to support various other LG devices on Android 4.0 - 4.4.2... 4.4.2 kk_root.zip by autoprime. Current IOroot25r1 by autoprime.
    Supported devices include LG Optimus G, G2, G3, G Pro, G Pro 2, G Flex and G Pad just to name a few.

    4.4.2 root will NOT work for you if you cannot get into the stock recovery menu w/the "adb reboot recovery" command.
    Check the supported devices list below. You may have to downgrade to 4.2.2 or below and root that instead.
    Or your device may not be supported at all. Again.. check the supported device list below.


    Current Version - IOroot25 refresh 1

    Download IOroot zip, extract and run script to root. ADB must be enabled (USB Debugging ON).
    Click the button below for IOroot device support list, manual and automated root and other info.


    Device Model and Firmware Supported List:


    LG Optimus G - all 4.2.2 and 4.4.2

    LG G2:
    AT&T D800 - D80010d/D80010o/4.4.2
    D801 - TMO(all 4.2.2 // No 4.4.2 support), CLR(all 4.2.2 // 4.4.2 ??), WND(all 4.2.2 // 4.4.2 ??), VTR(all 4.2.2 // 4.4.2 ??)
    D802 - all 4.2.2 and 4.4.2
    D803 - all
    D805 - all
    D806 - all
    F320K - Shipping 4.2.2 ROM/F320K20a/20f // 4.4.2 ??
    F320L - Shipping 4.2.2 ROM/F320L20b/20e // 4.4.2 ??
    F320S - Shipping 4.2.2 ROM/F320S20a/20g // 4.4.2 ??
    Sprint LS980 - All 4.2.2 and 4.4.2
    Verizon VS980 - All 4.2.2 and 4.4.2

    LG G Flex:
    F340 series - All 4.2.2 // 4.4.2 ??
    D950 - All 4.2.2 // No 4.4.2 support
    D955 series - All 4.2.2
    D958 series - All 4.2.2 // No 4.4.2 support
    D959 - All 4.2.2 // No 4.4.2 support
    LS995 - All 4.2.2 and 4.4.2

    LG G Pro - All 4.4.2 Only

    LG G Pro 2:
    F350 series - Shipping ROM // 4.4.2 ??
    D838 - Shipping ROM // 4.4.2 ??

    LG G Pad - 4.4.2 Only

    LG G3
    F400 Series - Shipping ROM


    Manual Root Method:

    Code:
    [B][SIZE="2"]Windows Drivers:[/SIZE][/B]
    [I]Verizon Drivers - [URL="http://bit.ly/1ibRvc3"]HERE[/URL]
    Drivers for everyone else - [URL="http://bit.ly/18EPHZN"]HERE[/URL][/I]
    
    [B]4.4.2 Manual Root:[/B]
    [SIZE="1"]
    Download and extract the latest IOroot.zip
    Enable USB Debugging. VZW users must also enable ethernet mode. 
    Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
    (windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]
    
    [B]1. adb devices[/B]
    [B]2. adb reboot recovery[/B]
    (when booted in recovery, select: 'apply update from adb' with power button)
    [B]3. adb sideload kk_root.zip[/B]
    
    reboot when zip finishes flashing. done.
    
    
    
    
    [B]4.2.2 Manual Root:[/B]
    [SIZE="1"]Download and extract the latest IOroot.zip
    Enable USB Debugging. VZW users must also enable ethernet mode. 
    Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
    (windows users can hold shift key, right click in ioroot folder. Select "[URL="http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm"]open command window[/URL]" option.[/SIZE]
    
    copy/paste commands below.. hitting enter/return after each line. 
    Linux/Mac users may have to enter ./ before adb on each line. 
    Example: ./adb push g2_security /sdcard/g2_security
    
    [SIZE="1"][B]1:[/B] [B][I]adb devices[/I][/B]
    (make sure it sees your device; if "offline" turn on phone/unlock and accept RSA key prompt)
    [B]2:[/B] Choose next line based on model and firmware version:
    AT&T D80010d (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    AT&T D80010o/10q: [B][I]adb push ytiruces_1a_att /sdcard/ytiruces_1a[/I][/B]
    KT F320k (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    KT F320K20a/20f (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
    LGU F320L (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    LGU F320L20b/20e (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
    D802(T) (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    D803 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
    D805 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    D806 (4.2.2): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    SKT F320S (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    SKT F320S20a/20g (KitKat): [B][I]adb push ytiruces_1a_kk /mnt/shell/emulated/0/ytiruces_1a[/I][/B]
    Sprint LS980ZV7/ZV8: [B][I]adb push g2_security_spr /sdcard/g2_security[/I][/B]
    Sprint LS980ZVA (OTA): [B][I]adb push ytiruces_1a_ls980 /sdcard/ytiruces_1a[/I][/B]
    T-Mobile D80110c (Shipping ROM): [B][I]adb push g2_security /sdcard/g2_security[/I][/B]
    T-Mobile D80110g (OTA): [B][I]adb push ytiruces_1a_tmo /sdcard/ytiruces_1a[/I][/B]
    Verizon VS98010B (Shipping ROM): [B][I]adb push g2_security_vzw /sdcard/g2_security[/I][/B]
    Verizon VS98011A/12B (OTA): [B][I]adb push ytiruces_1a_vzw /sdcard/ytiruces_1a[/I][/B]
    Videotron D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
    Wind D801 (4.2.2): [B][I]adb push ytiruces_1a_d803 /sdcard/ytiruces_1a[/I][/B]
    
    F340-Series (4.2.2): [B][I]adb push ytiruces_1a_F340JB /sdcard/ytiruces_1a[/I][/B]
    D950 (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
    D955-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
    D956-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
    D958-Series (4.2.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
    D959 (4.2.2): [B][I]adb push ytiruces_sumtz /sdcard/ytiruces_sumtz[/I][/B]
    LS995 (4.2.2): adb push ytiruces_1a_ls995 /sdcard/ytiruces_1a
    
    F350K/L/S (4.4.2): [B][I]adb push ytiruces_1a_kk /sdcard/ytiruces_1a[/I][/B]
    
    [B]********************************************************
    This next depends on your computer/phone model...
    
    USB Connection Mode needs to be toggled.
    Ways to do this are listed below...
    
    a. Unplug usb cable from phone then re-plug.
    b. Toggle USB mode from Charge to MTP back to Charge
    c. Toggle USB mode from Ethernet to MTP back to Ethernet (VZW users)
    ********************************************************[/B]
    
    [B]3:[/B] [B][I]adb shell[/I][/B]
    (you should now see a # instead of a $. # = root)
    [B]4:[/B] [B][I]exit[/I][/B]
    [B]5:[/B] [B][I]adb shell "mount -o remount,rw /system"[/I][/B]
    [B]6:[/B] [B][I]adb push su /system/xbin/su[/I][/B]
    [B]7:[/B] [B][I]adb push su /system/xbin/daemonsu[/I][/B]
    [B]8:[/B] [B][I]adb push install-recovery.sh /system/etc/install-recovery.sh[/I][/B]
    [B]9:[/B] [B][I]adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su"[/I][/B]
    [B]10:[/B] [B][I]adb shell "chown 0.0 /system/xbin/daemonsu;chmod 06755 /system/xbin/daemonsu"[/I][/B]
    [B]11:[/B] [B][I]adb shell "chown 0.2000 /system/etc/install-recovery.sh;chmod 755 /system/etc/install-recovery.sh"[/I][/B]
    [B]12:[/B] [B][I]adb shell "sync;mount -o remount,ro /system"[/I][/B]
    [B]13:[/B] [B][I]adb install Superuser.apk[/I][/B]
    
    REBOOT AFTER STEP #13
    [/SIZE]
    
    
    
    
    
    v

    Automated .bat/.sh Directions:


    Download latest ioroot.zip. Unzip and run bat/sh. Follow the onscreen instructions.
    4.4.2 is rooted through stock recovery. Once in recovery use volume keys to select "update with adb" then hit the power button... then continue with the script.

    Windows:
    Download and install proper ADB driver. Enable USB Debugging. Double-click on root.bat

    Linux:
    cd into /IOroot/ folder
    chmod +x root.sh
    ./root.sh

    Mac:
    cd into /IOroot/mac/ folder
    chmod +x root.sh
    ./root.sh



    Windows Drivers:
    Verizon Drivers - HERE
    Drivers for everyone else - HERE


    EFS Backup:

    EFS is automatically backed up for all 4.2.2(and below) devices.
    EFS is backed up into the ioroot folder on your computer. If running ioroot on mac.. it'll be in the ioroot/mac folder.
    Store backed up EFS partitions somewhere safe.

    4.4.2 devices will not have automatic EFS backup.
    Use the commands below to backup EFS.

    Code:
    adb shell
    su
    dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
    dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img

    Not Working?

    If you are on 4.4.2 and cannot get into a stock recovery menu with adb reboot recovery then you CANNOT root 4.4.2 on your device.
    You must downgrade to 4.2.2 with stock tot or kdz, retain root and take OTA updates to 4.4.2
    OR
    downgrade to 4.2.2 and install custom recovery and manually upgrade your way to 4.4.2 by flashing a KK rom + modem.


    Make sure to read all of the scripts on-screen text or you may miss something. Hitting a button when it's not time to do so or not reading everything on screen can cause problems. Make sure the phone is unlocked with the screen on whenever possible as well.

    If the scripts fail for you check out the manual directions further down the page. The manual method is only a few ADB commands and can help if I've messed up in the scripts somewhere... or if the scripts just don't seem to be working for you. Taking it one step at a time manually almost always results in success.


    Still not working?
    I need the output from the 4 ADB commands below along with IOroot version and if it was on Windows/Linux/Mac. Any errors you come across would help as well...
    adb shell "getprop ro.product.model"
    adb shell "getprop ro.build.target_operator"
    adb shell "getprop ro.lge.swversion"
    adb shell "getprop ro.build.fingerprint"


    What's Next?

    Confirm full root with rootchecker. ( @joeykrim )
    Support a great dev by buying the Pro version.

    If you only did the "temp root/adb only root" then you can confirm root by opening adb shell and seeing # instead of $.

    For custom recovery(TWRP/CWM) on 4.2.2 and below run FreeGee ( @Shelnutt2 )
    Check out the FreeGee donate version if you want to support a great dev.

    For custom recovery(TWRP) on 4.4.2 run AutoRec by @Cloudyfa for a safe and easy install.


    IOroot25r1 Download: HERE


    Changelog:

    v25r1: Fixed LG OG EFS backup. Added D802T 4.2.2 support. Script checks for 4.4.2 first. G3 supported.
    v25: Added root for 4.4.2 devices. Now works on most LG 4.4.2 devices. Thanks to @jarari2 for the idea to go through stock recovery.
    v24: added support for G2 D800 10q, G Flex D956 and G Pro 2 F350K/L/S(thanks to @hkfriends for confirming ioroot method still works)
    v23: added support for AT&T G Flex D950 10c.
    v22: added support for TMO D959 G Flex. Tweaked scripts EFS backup... hopefully no more errors.
    v21: added support for Sprint LS980ZVA update. Added EFS backup support.
    v20: added support for all D802/D805/D806. Updated all scripts. Added LG Optimus G and LG G Flex support. SuperSu now installed in /system.
    v19: added support for MORE F320 4.4 firmware. Added Singtel D802 support. Linux/Mac script fixes.
    v18: added support for MORE F320 4.4 firmware. Added Vodafone(VDF) carrier(should work with at least Shipping ROM). Tweaked scripts.
    v17: added F320* 4.4 KitKat root. Added SuperSu.4.4 users must reboot after running root script(mac/linux)
    v16: added TMO 10g root and "SCA" root(D802/D805)
    v15: added ATT 10o root.
    v12: added Verizon 12B root.
    v11: added linux support and Sprint LS980 root(both thanks to @Shelnutt2)


    y u no hit thanks button?
    6
    EVERYONE'S root problems may have just been solved today. @geohot has released towelroot to root the att/vzw gs5.
    Well, it works on my LG G2 LS980 on 4.4.2. So TMO D801 4.4.2 users... G Flex 4.4.2 users... G Pro 2 users... anyone else on 4.4.2 or less... you should now have root.

    go to http://towelroot.com - install apk - run app - reboot - install supersu
    be sure to thank geohot.
    6
    ioroot25

    4.4.2 root is here.

    Download HERE

    Changelog:
    v25 - Added root for 4.4.2 devices. Added G Pro 2 D838 support. Thanks to @jarari2 for the idea to go through stock recovery.

    Scripts need testing!! I am 99% sure the method works across all ioroot support devices but I am NOT 100% sure if the script/bat files are perfect.

    Manual method below if you don't wanna use script:
    Code:
    [SIZE="1"]Download and extract the latest IOroot.zip
    Enable USB Debugging. VZW users must also enable ethernet mode. 
    Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
    (windows users can hold shift key, right click in ioroot folder. Select "open command window" option.
    
    copy/paste commands below.. hitting enter/return after each line. [/SIZE]
    
    [B][I]adb devices
    adb reboot recovery
    adb sideload kk_root.zip[/I][/B]
    
    reboot when zip finishes flashing. done.


    *ATTENTION*
    shucks.. apparently this still wont work with D838. no way to get into the stock recovery.

    ioroot25 will root any LG 4.4.2 phone if it can get into recovery.
    2
    I have f350s tot and dll. Could you help to build the kernel?

    sure! please PM me and upload to gdrive or baidu

    Edit 1: OK I found out a TOT for S (v10e + v10g)


    << I don't take any responsibility for the following procedures. please take extra care on how to flash a TOT file. It may result to brick your mobile phone permanently>>


    Note: your warranty will/may be void if you do a rooting to your mobile phone :)


    Required:
    LG drivers: http://pan.baidu.com/s/1hqiMUbi
    LG Flash Tool: http://pan.baidu.com/s/1c06BDuC (remember to overwite the MegaLock.dll to the LGFlashTool directory)

    Tutorial on how to use LG Flash Tool
    http://xdaforums.com/showthread.php?t=2475045
    Chinese: http://pan.baidu.com/s/1gd7R6Jh



    !!! BACK UP all your data from /sdcard partition, LG Flash tool will erase /sdcard even though only flash a boot image. While other partitions are safe.




    All TOT files are stored in google drive, click the link and then press CTRL + S to download the rar file



    KR F350S 32GB
    1) Flash f350s_root_kernel.TOT
    https://drive.google.com/file/d/0BxC_n8Lmue8vNDNuQkJrTTRDTDQ/edit?usp=sharing

    2) root it by IOroot 2.4 (please refer to #1 of this post)

    3) Once rooted, you can flash back the S stock kernel

    For f350s stock v10e
    https://drive.google.com/file/d/0BxC_n8Lmue8vUHpmd0hja0t5ZTA/edit?usp=sharing
    or
    For f350s stock v10g
    https://drive.google.com/file/d/0BxC_n8Lmue8vZC1HTkVlRG9fWEU/edit?usp=sharing


    In case of any issue, you can flash back to fully stock rom image

    v10e
    http://optimusforums.com/threads/g-pro-2-f350s-v10e-tot.11712/

    v10g
    http://bbs.gfan.com/android-7376941-1-1.html

    Good Luck


    Edit 2:
    HK D838 32GB
    d838_root_kernel
    https://drive.google.com/file/d/0BxC_n8Lmue8vck8yQ1A1YW1XNjg/edit?usp=sharing
    d838_v10a_kernel
    https://drive.google.com/file/d/0BxC_n8Lmue8vcUQxUXVZb3hQN1k/edit?usp=sharing
    d838_v10b_kernel
    https://drive.google.com/file/d/0BxC_n8Lmue8vd29jcDBacHMwTVk/edit?usp=sharing

    KR F350K 32GB
    f350k_root_kernel_v10e
    https://drive.google.com/file/d/0BxC_n8Lmue8vdXJOWjFZUjVlVkk/edit?usp=sharing
    f350k_kernel_v10h
    https://drive.google.com/file/d/0BxC_n8Lmue8vTmdQMU9vbFRLcDA/edit?usp=sharing
    1
    Success!! using manual method, though.
    Thanks