Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,768,557 Members 52,926 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
autoprime
Old
(Last edited by autoprime; 7th June 2014 at 11:56 PM.)
#1  
autoprime's Avatar
Recognized Contributor / Recognized Developer - OP
Thanks Meter 4683
Posts: 1,601
Join Date: Jun 2010

 
DONATE TO ME
Default [ROOT][IOroot] Root your LG G Pro 2 [F350][Woohoo!]


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:
Windows Drivers:
Verizon Drivers - HERE
Drivers for everyone else - HERE

4.4.2 Manual Root:

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.

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

reboot when zip finishes flashing. done.




4.2.2 Manual Root:
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. 
Linux/Mac users may have to enter ./ before adb on each line. 
Example: ./adb push g2_security /sdcard/g2_security

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

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

F350K/L/S (4.4.2): adb push ytiruces_1a_kk /sdcard/ytiruces_1a

********************************************************
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)
********************************************************

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

REBOOT AFTER STEP #13






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?
The Following 20 Users Say Thank You to autoprime For This Useful Post: [ Click to Expand ]
 
magicbbird
Old
#2  
Member
Thanks Meter 0
Posts: 42
Join Date: Apr 2005
Success!! using manual method, though.
Thanks
 
autoprime
Old
#3  
autoprime's Avatar
Recognized Contributor / Recognized Developer - OP
Thanks Meter 4683
Posts: 1,601
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by magicbbird View Post
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
Old
#4  
Member
Thanks Meter 0
Posts: 42
Join Date: Apr 2005
Quote:
Originally Posted by autoprime View Post
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
Old
#5  
autoprime's Avatar
Recognized Contributor / Recognized Developer - OP
Thanks Meter 4683
Posts: 1,601
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by magicbbird View Post
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
Old
#6  
Member
Thanks Meter 0
Posts: 42
Join Date: Apr 2005
Quote:
Originally Posted by autoprime View Post
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
Old
#7  
Senior Member
Thanks Meter 273
Posts: 414
Join Date: Aug 2008
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=s2sKk...ature=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.
Phones: G Pro F240, Galaxy S4, Note 3 N9005, LG G2 F320L, G Pro 2 and now G3 F400L
My IP Address
 
autoprime
Old
#8  
autoprime's Avatar
Recognized Contributor / Recognized Developer - OP
Thanks Meter 4683
Posts: 1,601
Join Date: Jun 2010

 
DONATE TO ME
Quote:
Originally Posted by magicbbird View Post
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
Old
#9  
Senior Member
Thanks Meter 28
Posts: 213
Join Date: Oct 2011
Location: 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
Old
#10  
Account currently disabled
Thanks Meter 1034
Posts: 2,634
Join Date: Sep 2011
Location: 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

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes