[Root][V500] G Pad 4.4.2 Stock w/ IOroot25 [Yippee!]

Search This thread

autoprime

Recognized Dev / Inactive Recognized Contributor
Jun 23, 2010
2,642
11,919

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 G Pad - 4.4.2 Only

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 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]

You should see [URL="http://forum.xda-developers.com/showthread.php?p=51530027"]DAT ROOT[/URL] when finished.
reboot phone. 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.
4.4.2 users will see DAT ROOT when finished rooting. Reboot phone. Done.

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.
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:
Jun 1, 2008
32
6
Faxe
Recovery

I managed to root my 4.4.2 tablet with this method.

I have had no luck to unlock the bootloader or install a custom recovery.

Anybody with advice on this when the tablet is running stock 4.4.2.
 

aicjofs

Senior Member
Nov 6, 2012
1,079
1,023
Portland, Oregon
I managed to root my 4.4.2 tablet with this method.

I have had no luck to unlock the bootloader or install a custom recovery.

Anybody with advice on this when the tablet is running stock 4.4.2.

dd the old aboot. Look at step 3 here. http://forum.xda-developers.com/showthread.php?t=2698267 you probably want to delete the build.prop out of the directory if you want to keep your current build.prop. I don't know if this ever got finished but this would work as well http://forum.xda-developers.com/showpost.php?p=51613184&postcount=54
 
  • Like
Reactions: Delo718

Wolkenstern

Member
Sep 6, 2013
33
1
did you look into what Andr.Exploit.Ratc even is?

it's a root exploit... deemed a virus because it roots android. you do want root right? :p

Sorry, I didn't look futher into it :eek:
But it works, I had this fastboot error because TWRP was gone, even after flashing it again.
Then I did Step 3, like suggested in the comment above and it works.
 

parsifal968

Senior Member
Mar 14, 2011
86
10
i have a problem... after upgrade from stock 4.2.2 to 4.4.2 with LG tool at first execute of ioroot they do a factory format and only after this they do a success at 2nd try.
But i lost all my data. Fortunately i have a nandroid.

how to regain root without data lost?
and if i try to restore \data partition from a 4.2.2 nandroid backup on this rooted 4.4.2 factory resetted?
 
Last edited:

skay

Senior Member
Sep 30, 2004
99
16
Princeton. MA
Works perfectly

I just downloaded KitKat (in the US) using the LG Mobile Support Tool and rooted with ioroot25 last night. Excellent root tool, very easy way to root your G Pad 8.3!
 

kerins

Member
Apr 9, 2012
45
7
Works fine, but erase all your data

Rooting worked fine. Warning about the the possible loss of data would have been nice.

Running the Xposed Framework with Gravitybox. PIE Control gives a better real estate.
Too early to comment on the battery performance. Nova launcher gives a smooth, stutter
experience.
 

Hugo-PT

Senior Member
Jan 1, 2014
612
486
Matosinhos
Done on my Gpad with 4.4.2 :) rooting worked fine, no data loss :)

autoprime, thanks a lot :good:

Sent from my LG-V500 using xda app-developers app
 

joeminati

Senior Member
Dec 23, 2009
391
58
Hey I am trying to root with a Mac. Having troubles going about doing the process. I followed all instructions. And when the tablet goes to stock recovery.... It says no command with a android icon.

Any pointers?

Sent from my Nexus 5 using xda app-developers app

---------- Post added 12th April 2014 at 12:09 AM ---------- Previous post was 11th April 2014 at 11:13 PM ----------

Nevermind..... Rooted it

Sent from my Nexus 5 using xda app-developers app
 

bukmba

Member
Jul 23, 2013
41
4
Tried it and it doesn't work for me. Followed manual precisely.
Once it boots into recovery there is no "apply update from adb" which I could click on. There are only the normal buttons from TWRP 2.7.0.1 like install, backup etc. Anyone can help?

Sent from my LG-V500 using Tapatalk

Edit:
Got it installed via adb but root didn't work. Went into TWRP, Mounted System, went to File Manager and deleted anything related to my previous SuperSU and then reflashed SuperSu and all went well.
 
Last edited:

AjunNg

Senior Member
Sep 24, 2012
324
60
When executing the .bat file, and then entering stock recovery,
at the bottom it reads:

E:missing bitmap stage_empty
(Code -1)
E:missing bitmap stage_fill
(Code -1)

The root is fine, and I have root access.

However does this cause problems in the future?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 101

    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 G Pad - 4.4.2 Only

    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 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]
    
    You should see [URL="http://forum.xda-developers.com/showthread.php?p=51530027"]DAT ROOT[/URL] when finished.
    reboot phone. 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.
    4.4.2 users will see DAT ROOT when finished rooting. Reboot phone. Done.

    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.
    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?
    2
    We have a new LG root method out... designed for LG G3 initially but should work on many more "recent" LG android devices. should support most LG devices on firmware built Q2 2012 up until now.

    New root is called Stump and can be found here - http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906

    New devices will have to be "bruteforced" by one user of each device/firmware... once bruteforced.. all users of that model will be supported once the new info has been added to the app.

    Example: User has a Verizon G3 on 4.4.2 24A... user opens stump.. device is not supported yet... so user accepts the "bruteforce" message and waits an hour or so and is then rooted. in addition to that Verizon G3 on 4.4.2 24A now being rooted... all future attempts at rooting Verizon G3 on 4.4.2 24A will take less than a second to root.

    To clarify.. if "Bob" uses Stump bruteforce on his Verizon G3 on 24A... anyone trying to root the Verizon G3 on 24A after "Bob" will NOT have to bruteforce/wait an hour. Root will then be instant for all future users on that model/firmware. When firmware "26B" comes out in the future.. someone will have to bruteforce that once time before all others get root... and so on and so on..

    The more devices that are "bruteforced" the greater the support list for Stump root is. While it's a tad annoying the first user of each device to wait an hour or so... Stump root has to potential to root more LG devices than any other method available.

    Please provide a logcat if the app is crashing for you. Please report your exact model/firmware if Stump tells you the device is unsupported(and gives you no option to bruteforce).
    1
    I managed to root my 4.4.2 tablet with this method.

    I have had no luck to unlock the bootloader or install a custom recovery.

    Anybody with advice on this when the tablet is running stock 4.4.2.

    dd the old aboot. Look at step 3 here. http://forum.xda-developers.com/showthread.php?t=2698267 you probably want to delete the build.prop out of the directory if you want to keep your current build.prop. I don't know if this ever got finished but this would work as well http://forum.xda-developers.com/showpost.php?p=51613184&postcount=54
    1
    How to make EFS backup without root? I updated my G Pad to 4.4.2 and lost root.

    bump.
    EFS backup is necessary?