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.
I agreed, I am using v10G, however cant root
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.
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.
I will work on getting a kdz usual you just need to ping their server.
Sent from my LG-F350S using Tapatalk
I will work on getting a kdz usual you just need to ping their server.
Sent from my LG-F350S using Tapatalk
I did a stupid thing today for replacing build.prop wihout changin a proper permission ......
Blank screen after booting the LG logo
I'm able to get into the recovery mode, but fail to get the SU in adb
Cant modify the build.prop permissiom or exchange the backup file....
someboby can make a help ?
Root works like a charm on my F350K
Inviato dal mio LG-F350K utilizzando Tapatalk[/QUOT
What build number?
Sent from my LG-F350S using Tapatalk
Root works like a charm on my F350K
Inviato dal mio LG-F350K utilizzando Tapatalk[/QUOT
What build number?
Sent from my LG-F350S using Tapatalk
https://www.dropbox.com/s/it3akt67taq53a5/Screenshot_2014-03-23-13-37-38.png
Inviato dal mio LG-F350K utilizzando Tapatalk
Hi
I'm using G PRO 2 D838 but cant root now.
Is any possible to root my device ?
most likely no... a new exploit (not ioroot) will need to be made public.
Is this comply to LG D838 International edotion?
Sent from my LG-D838 using XDA Premium 4 mobile app
[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.
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*
Verizon G2 4.4.2 seems to nag about files being modded or a virus being installed... obviously there are more checks in place to detect root. I assume a simple .apk freeze will fix the nag... which apk though.. I do not know. That's for you guys for bother with
it is very lucky that someone uploaded TOT file for the F350K/L just today!!Do you kown any download link of kdz/tot for F350? I want to flash back to v10c/10d but cant get an firmware.
Sent from my LG-F350L using XDA Premium 4 mobile app
[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
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
[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.