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?
Success!! using manual method, though.
Thanks
magicbbird said:
Success!! using manual method, though.
Thanks
Click to expand...
Click to collapse
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
autoprime said:
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
Click to expand...
Click to collapse
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?
magicbbird said:
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?
Click to expand...
Click to collapse
it will determine if the bootloader can be exploited so custom roms can be flashed on G Pro 2
autoprime said:
it will determine if the bootloader can be exploited so custom roms can be flashed on G Pro 2
Click to expand...
Click to collapse
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.
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.
magicbbird said:
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.
Click to expand...
Click to collapse
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.
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?
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
Epix4G said:
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
Click to expand...
Click to collapse
loki is patched/blocked on F350.
autoprime said:
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://forum.xda-developers.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?
Click to expand...
Click to collapse
No brainer! Many thanks! Used automatic. G Pro 2.
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.
haared said:
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.
Click to expand...
Click to collapse
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.
Thanks, Waiting for KDZ or TOT..............
autoprime said:
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.
Click to expand...
Click to collapse
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
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?
autoprime said:
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://forum.xda-developers.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?
Click to expand...
Click to collapse
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
[email protected]:/ $ 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>
Click to expand...
Click to collapse
is there any more information i can provide？
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.
hkfriends said:
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.
Click to expand...
Click to collapse
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.
Related
Okay, this was my first time trying to root my phone and it would figure that non of the automated methods worked for me. Still, I was able to get root on my US Cellular Samsung Galaxy S Mesmerize (SCH-i500 for the kids keeping track at home) and these are the steps that I took. I hope this helps others who may be scratching their head wondering what to do when the developers haven't gotten around to (read: forsaken) us.
The nice thing about this method is that it doesn't require Windows (though you still do download SuperOneClick).
NOTE: This is only for an officially updated Mesmerize. Rooting is unnecessary for the leaked version.
APOLOGY: I can't post any links to anything outside the forum as I am a newer member, so, sorry for not being able to post URLs.
1. Download the Android SDK from the Android developer website and install/unzip it. You may need to add the path to the adb tool (found under platform-tools for me) to your PATH variable.
2. Download the SuperOneClick tool and unzip it
3a. If you are using Windows, then make sure to install the drivers for your phone. I don't have Windows, so don't ask me which file to download. Sorry.
3b. Enable USB Debugging on your phone (Settings->Applications->Development->Check "USB Debugging").
4. Connect your phone to your computer using the USB cable
5. Open a shell (or command prompt on Windows) and change directories to where you unzipped SuperOneClick
6. Run the following commands to copy files to your device
A. adb push psneuter /data/local/tmp/psneuter
B. adb push busybox /sdcard/busybox
C. adb push su-v2 /sdcard/su
NOTE: A quick note of each of these files.
A. psneuter - an exploit to gain root access temporarily on your phone
B. busybox - a compilation of common unix commands to help you along the CLI world
C. su - the super-user command used to gain elevated privileges
7. Run the following command to get a command line interface to your device
adb shell
At this point, you should see a $ prompt indicating that you are on your phone.
From here, you will change directories to where you put the exploit, change the permissions so you can run it, copy over the files that we need to sustain root access, and finally, install the Superuser.apk app so that you can manage root access from the UI.
Execute the following commands:
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
Here, you will be disconnected from your device. This is normal. Just run "adb shell" again to get back in, though now, you will notice that the prompt has changed to a #. The following commands will reflect that.
# mount -t rfs -o remount,rw /dev/block/st19 /system
# cd /system/xbin
# cat /sdcard/busybox > busybox
# cat /sdcard/su > su
# chmod 4755 busybox
# chmod 4755 su
# exit
Now, you will be back on your computer. Type the following to install the Superuser.apk app.
adb install Superuser.apk
That should do it! You now have root access. Go ahead and try to install Titanium Backup (requires root). You can also install a terminal app or anything else.
I hope this helps. Report your successes/failures in the comments.
Build Properties of Auxus Core X2 3G contains the ro.build.user=root by default firmware update and also Default Properties contains ro.secure=0, ro.debuggable=1. So rooting the devices made very easy.
The following are the things to do to get root access in the front end
Update the binary of the Superuser
Setting the chown & chmod to the Superuser binary
Install the Superuser.apk
Optional:Installing the Root Checker & Root Unistaller
The following are the files required to do the above
ADB Driver for the Rockchip board (Auxus Core X2 Shipped with RK3066)
ADB file & ADB library files
Latest Superuser binary & apk files
Optional:Rootchecker & Root Uninstaller files
Source:
ADB Driver : XDA Post (http://78.140.134.121/d/6ea124157e9cda25ab1707cbcba7/usb_driver.zip)
ADB Files : http://forum.xda-developers.com/showthread.php?t=1987280
SU Files : http://downloads.androidsu.com/superuser/
Optional:RootCheck: http://joeykrim.com/
Optional: RootUnistaller:http://www.apkmania.co/2012/12/root-uninstaller-pro-v32-apk.html
Customizing the folder for the Auxus
Create folder e.g., C:\Auxus\
Extract the ADB files and Copy the adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll to Auxus
Extract the Superuser files and Copy the \system\app\Superuser.apk and \System\bin\su to Auxus
Optional:Also place the RootCheck & RootUnistaller apk
Creating batch file named ROOT.bat
Creating batch file : ROOT.bat
The following code to be added to batch file
Code:
echo off
echo Check list of devices connected
adb devices
pause
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
echo Rebooting 1/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
echo Setting Kernel Properties
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
echo Rebooting 2/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
adb shell id
pause
echo ADB Mounting root drive
adb remount
echo Pushing Superuser files
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
echo Installing application
adb push superuser.apk /system/app/superuser.apk
echo Rebooting 3/3
adb reboot
echo ROOTED
pause
Also append below code if optionals downloaded
Code:
echo ADB Mounting root drive
adb remount
echo Installing Root Check & Root Uninstall
adb push Root_Uninstaller_Pro.apk /system/app/Root_Uninstaller_Pro.apk
adb push RootCheckPro.apk /system/app/RootCheckPro.apk
echo Done
pause
echo Rebooting
adb reboot
echo After Reboot to home screen unlock and press any key
pause
Steps to root
Install the ADB driver by double clicking the DPInst-32bit.exe
Now windows will prompt for the Driver security - Click Install anyway to proceed
Now connect the Auxus Core X2 3G in USB Debugging mode, the driver will be identified by windows (if not restart)
Now run the ROOT.bat (Run as Administrator)
The tablet will be reboot 3 times (if optional files used reboot 4 times)
Now run the ROOT.bat file and Auxus Core X2 3G rooted successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer :
Though tested many times with my tablet and the post drafted carefully. Kindly Backup data before proceed; All the files download from various link from internet and the attachment (Auxus.rar) contains the combination of them. Screenshots generated by author.
ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
combined attachment included
Update: Auxus.rar is combination made from the above said link and with root batch files. ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Thanks a bunch!!
I will try this method on my corex2 this weekend and let you know the result. Thanks a lot!:good:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Rear camera- laggy- known issue
guyton100 said:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Click to expand...
Click to collapse
Yes, this is a known issue with the CoreX2. Lets hope that they will fix this issue with future firmware updates.
Please tell me how to unroot the same
Kudremukh said:
Please tell me how to unroot the same
Click to expand...
Click to collapse
muruggan_a has reported a post.
Reason:
Hi Friends,
I have done a pre-booking of X2 3G, i have faced the following issues
1) I was unable to send any 2010 MS office documents from win 7 laptop to auxus x2 3g
2)Even after i paired my tablet with my laptop, i cannot connect the media service from my tablet to laptop using bluetooth
3)Nokia BT head set doesnt get paired
And my last query is if i can root the device whether i can use 3G dongle instead of using SIM slot?
Please help me,
I have handedover to iberry service center and asked for replacement because of the bluetooth issue which i mentioned above. I got the replacement device but that also have the same problem. The new device had some scratches behind so given them back and asked for replacement.
Device Not found
When I oopen ROOT.bat In,
Win 8 it says error:device not found
Win 7 it says path not recognized or something like that
plz help me how to fix it and the
ADB unknown USB driver you gave when i open it win rar says that the file is corrupted or what i dont know
plz help me here:crying:
Will this work for Auxe CoreX4?
skv_vlr_mech said:
Build Properties of Auxus Core X2 3G contains the ro.build.user=root by default firmware update and also Default Properties contains ro.secure=0, ro.debuggable=1. So rooting the devices made very easy.
The following are the things to do to get root access in the front end
Update the binary of the Superuser
Setting the chown & chmod to the Superuser binary
Install the Superuser.apk
Optional:Installing the Root Checker & Root Unistaller
The following are the files required to do the above
ADB Driver for the Rockchip board (Auxus Core X2 Shipped with RK3066)
ADB file & ADB library files
Latest Superuser binary & apk files
Optional:Rootchecker & Root Uninstaller files
Source:
ADB Driver : Unknown (http://78.140.134.121/d/6ea124157e9cda25ab1707cbcba7/usb_driver.zip)
ADB Files : http://forum.xda-developers.com/showthread.php?t=1987280
SU Files : http://downloads.androidsu.com/superuser/
Optional:RootCheck: http://joeykrim.com/
Optional: RootUnistaller:http://www.apkmania.co/2012/12/root-uninstaller-pro-v32-apk.html
Customizing the folder for the Auxus
Create folder e.g., C:\Auxus\
Extract the ADB files and Copy the adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll to Auxus
Extract the Superuser files and Copy the \system\app\Superuser.apk and \System\bin\su to Auxus
Optional:Also place the RootCheck & RootUnistaller apk
Creating batch file named ROOT.bat
Creating batch file : ROOT.bat
The following code to be added to batch file
echo off
echo Check list of devices connected
adb devices
pause
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
echo Rebooting 1/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
echo Setting Kernel Properties
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
echo Rebooting 2/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
adb shell id
pause
echo ADB Mounting root drive
adb remount
echo Pushing Superuser files
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
echo Installing application
adb push superuser.apk /system/app/superuser.apk
echo Rebooting 3/3
adb reboot
echo ROOTED
pause
Also append below code if optionals downloaded
echo ADB Mounting root drive
adb remount
echo Installing Root Check & Root Uninstall
adb push Root_Uninstaller_Pro.apk /system/app/Root_Uninstaller_Pro.apk
adb push RootCheckPro.apk /system/app/RootCheckPro.apk
echo Done
pause
echo Rebooting
adb reboot
echo After Reboot to home screen unlock and press any key
pause
Steps to root
Install the ADB driver by double clicking the DPInst-32bit.exe
Now windows will prompt for the Driver security - Click Install anyway to proceed
Now connect the Auxus Core X2 3G in USB Debugging mode, the driver will be identified by windows (if not restart)
Now run the ROOT.bat (Run as Administrator)
The tablet will be reboot 3 times (if optional files used reboot 4 times)
Now run the ROOT.bat file and Auxus Core X2 3G rooted successfully.
Disclaimer :
Though tested many times with my tablet and the post drafted carefully. Kindly Backup data before proceed; All the files download from various link from internet and the attachment (Auxus.rar) contains the combination of them. Screenshots generated by author.
ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Click to expand...
Click to collapse
Will the above procedure work for the Corex4 as well?
guyton100 said:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Click to expand...
Click to collapse
yes, it is there, but front camera is good. I posted support query in manf webpage and searching the firm update to make custom rom
cdwarak said:
Will the above procedure work for the Corex4 as well?
Click to expand...
Click to collapse
try root methods of Samsung Exynos 4412 for CoreX4 3g
iNOXIA2012 said:
When I oopen ROOT.bat In,
Win 8 it says error:device not found
Win 7 it says path not recognized or something like that
plz help me how to fix it and the
ADB unknown USB driver you gave when i open it win rar says that the file is corrupted or what i dont know
plz help me here:crying:
Click to expand...
Click to collapse
If Root.bat not worked manual use the code as mentioned in the thread.
I'm using windows 7 only and also verified with the XP.
Try downloading the files from source links. If device not recognized then it is the issue of the USB driver installation; Also refer the Screenshots and steps in the post
Kudremukh said:
Please tell me how to unroot the same
Click to expand...
Click to collapse
in command prompt, path to the adb folder
adb remount
adb shell rm /system/app/superuser.apk
adb shell rm /system/bin/su
adb reboot
and so on...
!!!Rooted!!! This method works like a charm. Thanks man!! Trying to figure out if we have cwm recovery for corex2. I tired a couple of them meant for other rockchip 3066 devices but no dice.
clockworkmod-recovery-for-auxus-core-x2
s.rahus said:
!!!Rooted!!! This method works like a charm. Thanks man!! Trying to figure out if we have cwm recovery for corex2. I tired a couple of them meant for other rockchip 3066 devices but no dice.
Click to expand...
Click to collapse
Check out for CWM
http://forum.xda-developers.com/showthread.php?p=37584364#post37584364
Link Error
ADB Driver URL that you gave wont work gives me Error
iNOXIA2012 said:
ADB Driver URL that you gave wont work gives me Error
Click to expand...
Click to collapse
Please find attachment file that i downloaded from the link what i mentioned in first post
skv_vlr_mech said:
please find attachment file that i downloaded from the link what i mentioned in first post
Click to expand...
Click to collapse
thank you so much
Great It worked flawlessly. I wasn't able to root using moborobo or Zhuo. But this method worked. Thanks
Has it got GPS or not???
Hi,
Can anyone please tell whether Auxus core X2 3G has got inbuild GPS or not.
About the device:
http://www.xolo.in/Q2000L
http://www.gsmarena.com/xolo_q2000l-6495.php
Stock Firmware:
Latest : S017_01-07-2014 (KitKat 4.4.2)
https://drive.google.com/uc?id=0B6xlBPoXgsR3U0JBWm5oT0J5bUU (Source)
Code:
File: Xolo Q2000L S017 01-07-2014-(by_xdafirmware.com).zip
CRC-32: eb227244
MD4: c8d1739be1fe45d43d8fd2a1615d680d
MD5: 07a484331431e523e5067186f07f0ac3
SHA-1: e808227b928fd03f0696ef6e37015432c06fade5
Flashing Instructions:
Prerequisites:
1. Broadcom MultiDownloader
(Latest one I can find is V2.0.1; Source)
2. Broadcom USB Download Device driver
(Latest one I can find is v1.0.5, mirror by @moulnisky. Broadcom uses two interfaces for flashing - one is serial/COM & another is USB but now they encourage to use the later one. Remember that the driver's digital signature isn't valid for 8.1/10 so you need to turn off driver signature enforcement to install the driver. To install the driver manually, open BRCM_WinUSB_ADB_Jungo_MTP_RNDIS_Driver_1.05.exe using 7-Zip, extract the contents & install the using bcmusbdl.inf)
Follow this tutorial, but we need some enhancements:
1. At step 8, I've chosen Download Mode as "Flash All Image" i.e the first one.
2. Skip step 9 & 10, come to step 11 i.e press 'Flash' button.
3. After that, connect the device in flashmode i.e as described in step 9. If Broadcom USB Download Device driver is properly installed, then flashing will begin. FYI, the hardware ID of the flashing interface is USB\VID_0A5C&PID_E720.
USB Debugging:
Broadcom bundles signed drivers for ADB/MTP/RNDIS interfaces along with the device itself (in the emulated CD drive). I've also mirrored it here. As an alternative, you can also use Android USB UnifL driver.
Remember that current ADB binary requires vendor ID whitelisting to detect Broadcom SoC. So execute Broadcom_SoC_Drivers.rar\AndroidPCUSBdrivers\andro id adb\brcm_adb_vendor_id.bat to do it. Otherwise ADB can't see the device, even if drivers are properly installed.
Rooting:
After you are able to communicate with the device through ADB, use iRoot to root it. Make sure to uninstall two Chinese bloatwares that came with Kinguser. I personally prefer to use SuperSU by @Chainfire, so we need to tinker with it again.
1. Install BusyBox.
2. Thanks to @idler1984, we've an easy way to switch from Kinguser to SuperSU. See here, search for "Q: I'd like switching to SuperSU, what shall I do?". I'm also providing the modified steps here which fits our needs:
2.1. Download SuperSU (I prefer the latest beta though). Open the zip, go to armv7 folder & extract the file named "su".
2.2. Use ADB to push su to /data/local/tmp:
Code:
adb push su /data/local/tmp
2.3. Start a su session and run the following commands:
Code:
adb shell
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
2.4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. It may crash but its harmless. Your su session should be still running.
2.5. Uninstall Kinguser app.
2.6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
2.7. Install SuperSU; get it from SuperSU zip => common\Superuser.apk.
2.8. Open SuperSU to update files & reboot.
2.9. (Optionally) make SuperSU a system app.
Other Notes:
1. This device has fastboot interface too; you can access it by running
Code:
adb reboot bootloader
2. To force install applications in SD card, use this:
Code:
adb install -s NAME.apk
Reserved for future use.
This post is kinda hard to find. But the instructions are good. They all work on my Xolo Q2000L.
Thank u @Titokhan for great help. Please help me over internal app storage issue. This phone is lacking good internal storage even it is having 8gb (5.29 gb on board). Please help.
########################################################################
EDIT ::: First Non-Alpha Release.
#>>Download LINK <<#
http://www.mediafire.com/file/rhmimk5dojt492b/DirtyCow + Double SuperSu Injection.zip
########################################################################
######Screenshot's######
PROOF.SH <<--- Click-able --- <<<
Kernel + SEpolicy Informations <<--- Click-able --- <<<
Succesfully Granted Termux Root <<--- Click-able --- <<<
SuperSu is at Lastest V2.82 <<--- Click-able --- <<<
######PROOFS######
But Technicly this works on ANY Android , Tested on 5.1.1, 6.0.1, 7.0,
SM-G920V
My Bootloader is Locked/ Doesnt Exist?
I use FLashFire, which will be installed using this method, but i also used Official TWRP to understand how the S6 Bootloader IS Picky I will only Accept STOCK.
I SUCCESFULLY Booted in TWRP with FISHY... I was working on TEMP Recovery and i thought...(Useless because you cant MODIFY THE OS -_- else Bootloader trigger)
But how about Booting a ROM instead of TWRP?! So i am working on this right now, Currently have a WORKING METHOD For Lg G4 h812 and succefully Booted Custom ROM)
This(Dirty-Cow Exploit) also Worked for my LG G4 But with Different Security Disabling Methods(OEM UNLOCK), Bluestack, Ubuntu 16, My raspberry PIE.... Pretty much... ARM32/64... but there is one for EVERY arch anyway.
I wish you guys a GOOD root.... Not to Exploit the exploit.
Scan.rar :Note: IF This is INFECTED"... well i had no clue, i want to Declare that i have NOT inject any Virus, i just Found the files on a XDA and Slighty modified a Root-Tool and Merged it with another, Writed .bat to make it Function at least with VERIZON and ROGERS.
::::::::::::::::::::::::::::::::::::::::::::::I want also to Declare that IF IT IS INFECTED , PLEASE REPORT BECAUSE... i am RUNNING THIS on my phone.*facepalm*::::::::::::::::::::::::
https://www.virustotal.com/fr/file/...19598dfec975f6511e20ed70/analysis/1519884568/
6 / 58
Antivirus Résultat Mise à jour
Antiy-AVL Trojan/Linux.TSGeneric 20180301
Avast ELF:CVE-2016-5195-T [Expl] 20180301
AVG ELF:CVE-2016-5195-T [Expl] 20180301
CAT-QuickHeal Exploit.dirtycow.A18c7 20180228
ESET-NOD32 a variant of Android/Exploit.CVE-2016-5195.A 20180301
Ikarus Trojan.AndroidOS.Exploit 20180228
Download Link ::
http://www.mediafire.com/file/n2r3obszwkxf31n/Arm32-DirtyCow-MixSploit.rar
What's going on here? No input is being accepted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wasted time, no root....
Anyway of making linux version? and maybe another option for dirtycow app_process32
EDIT --
YOU MUST disabled KNOX - Find My Device - Reactivation LOCK.
You must run DIsable Samsung Securities.. it might bug on Lockscreen or Knox. But CTRL + X/C ; would you like to terminate bat (y/n?) = N , just skips the stuck steps(most of the time)
But i really recommend doing all commands 1 by 1.
i figured much about android since using DIrtyCow and other Rootkits
Think about your / (root path) as an Standart UBUNTU/Linux, whitout YET the SUDO(which is added using BUSYBOX to your System/bin)
I also want to add that With ANY ANDROID.. or almost, in this case my Sm-g920V 5.1.1:: I succefully Flashed NETHunter for Arm64, still trying to compile it for ANdroid 7.0... Might as well just install CyanogenMod if i can Get Root and TWRP Working again.
FISH script is USING DIrtyCow. so should GET YOU ROOT. if you dont have it already.
Try running the .bat commands 1 by 1
the Run_for_arm.bat is to get a shell, then if you copy dirtycow.sh to the /system/usr/tmp (something like that) you can do with the SHell that run_for_arm.bat has open something similar to this :
--This Runs a Shell with Dirtycow(modified sh Function to allow Root) + My-run-as(which Elevates to Root)
*****************Run a Dirtycow(elevated) Shell ADB ************************
adb shell
/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/my-run-as
#OR#
adb shell "/data/local/tmp/dirtycow /system/bin/run-as /data/local/tmp/my-run-as"
-- You can after that Operate Root Commands from this shell. EXEMPLE :::
Code:
*******Remove Old DirtyCow**********
files\adb shell rm /data/local/tmp/dirtycow
files\adb shell rm /data/local/tmp/my-run-as
files\adb shell rm /data/local/tmp/init
files\adb shell rm /data/local/tmp/init_patched
files\adb shell rm /data/local/tmp/sh
files\adb shell rm /data/local/tmp/a.out
files\adb shell rm /data/local/tmp/sepolicy
*******PUsh DIrty Cow Via ADB **********
files\adb push files/armeabi-v7a/dirtycow /data/local/tmp/dirtycow
files\adb push files/armeabi-v7a/my-run-as /data/local/tmp/my-run-as
files\adb push init_patched /data/local/tmp/init
files\adb push a.out /data/local/tmp/a.out
files\adb push sh /data/local/tmp/sh
files\adb push sepolicy /data/local/tmp/sepolicy
*******Change the Permission of the FIles inside /tmp/ and attemp to unrestrict the tmp folder itself **********
files\adb shell chmod 0777 /data/local/tmp/
files\adb shell chmod 0777 /data/local/tmp/*
files\adb shell chmod 0777 /data/local/tmp/dirtycow
files\adb shell chmod 0777 /data/local/tmp/my-run-as
files\adb shell chmod 0777 /data/local/tmp/init
files\adb shell chmod 0777 /data/local/tmp/init_patched
files\adb shell chmod 0777 /data/local/tmp/a.out
files\adb shell chmod 0755 /data/local/tmp/sh
files\adb shell chmod 0777 /data/local/tmp/sepolicy
*****************Remount /system as Read/write ************************
adb shell "/data/local/tmp/dirtycow /data/local/tmp/my-run-as mount -o rw,remount /system"
adb shell mount -o rw,remount /system
adb push push_system /system
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
**************Install SuperSU APK and FlashFIRE********************
adb install -r SuperSU-v2.82.apk
adb install -r FlashFire.apk
**********Push The SuperSu Binary(Flashed .zip to an Empty Android Partition Format)**********************
adb push SuperSU-v2.82.img /data/su.img
adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
adb push init.sec.boot.sh /system/etc/init.sec.boot.sh
adb shell < supersu.cmds
adb shell < supersu1.cmds
-- The Trick is to try and open a Terminal emulator with My-run-as
Like so
I'l try to make it simpler... sorry I'm a noob as well. BUT I CAN TELL YOU
THAT I Succefully ROOTED once... now i reflashed stock, I'l try to do it again and make a Working, .bat script. sorry for inconviniente..
I Was so drunk.
########################################################################
EDIT ::: First Non-Alpha Release.
http://www.mediafire.com/file/rhmimk5dojt492b/DirtyCow + Double SuperSu Injection.zip
########################################################################
after Running Security Disabler AND Disabling Reactivation LOCK:::
Samsung/Security Disabler.Bat
1) Here it is, Copy and paste this new Run_for_arm(complete).bat
Just run that root.bat in this .zip file
And then Run This one.
Warrior1988 said:
Anyway of making linux version? and maybe another option for dirtycow app_process32
Click to expand...
Click to collapse
Took me an week to Find DirtyCow.Exploit
Took me an 3 Days to Figure out how it works(still not quite shure)
Took me a Whole day to install Kali-Linux, but EVERYTIME i finish install. Password changes?
I have now Ubuntu 17.01 , and it is My First time.
You can Probably rename <root.bat >---> root.sh>
Since Most Commands are "echo"(Unix-Basic) and "adb"(Downloadable Library) which can be performed on both environement almost natively.
In Fact , If you have an: ROOTED-Arm64-Android-Device(Exemple : "LG G4 H812" ) ++ OTG CABLE
(((NOTE :: If you Have an ROOTED-Arm32-Android-Device INSTEAD:;
1) :: EITHER ::
---Modifie the STEP 2 script (Which is SUPOSED to work for EITHER ARM32 or ARM64)
((( TO instead use the "/Step 2/push_system/lib" :: INSTEAD OF :: "/Step 2/Push_system/lib64" )))
2) :: EITHER ::
---Copy the "/Step 2/push_system/lib" Folder FILES to "/Step 2/Push_system/lib64"
0); you can EASILY ROOT your NON Rooted Arm64-device :
(1) Plug your UNIX USB_Debugable_-_arm64.-device : to : OTG_Cable-Usb3_ >> _-_Rooted Android Device;
(2) install ADB from terminal or Github to your Rooted Android Device;
(3) Extract DirtyCow + Double SuperSu Injection.zip >> /storage/emulated/0/WORKFOLDER
(4) Extract /Step 0 / Step 1 / Step 1.5 / Step 2.0 / (No worryes They have Folders Named Accordingly in Every .zip)
(5) For Every "Step X" folder, Find and rename Root.bat >> Root.sh
(6) Execute the RENAMED root.bat >-> Root.sh ; FROM Android Terminal Emulator(Requires Root, or does it?)
#OR#
run the ADB's Manually, which links to supersu.cmds, WHICH runs .sh Scripts.....
Anyone actually get this to work other than the OP? I have a 920v sitting here rotting i would rather use since my note5 will never have root
Icetech3 said:
Anyone actually get this to work other than the OP? I have a 920v sitting here rotting i would rather use since my note5 will never have root
Click to expand...
Click to collapse
op is a noob
there is no root on devices with dm-verity enabled
you can't make any changes to /system making this useless
What i thought. no idea why i have any hope on these things thanks.
Legitsu said:
op is a noob
there is no root on devices with dm-verity enabled
you can't make any changes to /system making this useless
Click to expand...
Click to collapse
its not workble j3119 ,but device have RL, i already disable all knox pakgs,
is thery any method which can give us temporally root access for all androids ,samsung lg etc
I have been trying to figure out how to make the github source code to work.
Hello. Did this end up not working? I have a Samsung galaxy s6 att SMG920A. It's been impossible to root it seems. It has a locked bootloader from what I've been told but it's not locked to The service provider . That being said I've rooted successfully s5, j7, LG k7, LG 330, and a few others I can't recall . I'm as new as it gets but I'm learning fast. I rooted the s5 by flashing old versions of the s5 stock rom, bricking it and reflashing. I was told back then that it was impossible especially since it was from T-Mobile. I have been told the s6 7.0 att is impossible but I think impossible means lazy sometimes. It's still up and running and not bricked and I have flashed with Odin every stock rom I came across and a few twrp that claimed they would work. I thrown noencryptnoencrptverity files and every super su u app on play store, modded play store and the free store at it. I've tried using lucky patcher, Apk editor and every flasher app i could. I recently decrypted one of the recorded recovery and found that dirty cow is being used on this phone and because I'm a noobe and don't know what I'm looking at; I think this phone is or was possibly rooted; but I doubt it root checker says it's not. Then again I rooted and flashed my wife's j7 with custom note 8 rom and root checker also says it's stock and not rooted. How does that work? I have three Alcatel 5041c and they have custom builds from the factory? Anyways I'm head strong to figure out how to make this dirty cow work and hopefully be universal because I have a bunch of cheap phones id like to see the full potential on and all the Obama phones everyone is selling for dirty cheap. I would also like to add I tried kingroot, kingoroot, drfone toolkit, drfone root, superoneclick every adb command I could find and even the sites offering paid roots can't touch it. Recovery mode has an option to boot to bootloader but it only just starts the phone. I'm confused on that. Fastboot commands don't work on Samsung so what would booting to the bootloader be used for with a Samsung? I'm honestly surprised this phone doesn't have more info on it or people working on it together. It's an octacore with 64 gigs of space. It walks faster than my rooted LG runs AND would take both the rooted jay7 and LG combined in a speed test and has and it's stock I've also used a usb hub and and otg cable and was able to add 184 gigs of external with no problems. Last I would like to add I have the internal parts of another s6 that was damaged and is running an older version I had a backup that I can't seem to find anywhere.
does it work running G920VVRU4DRE1 ? I know that was the major concern and problem with all the other methods. I just was to verify so I dont brick my phone.
so glad i posted this couples years ago. btw i was 16 years old.
it still work tho for my sw900w8:armv7
idk why but the boot image in step 1.5 gives me root (in ADB, not SuperSU). DirtyCOW seems to be patched (I wrote my own exploit and it didn't work either). Where'd you get the boot image?????
Superseani2 said:
########################################################################
EDIT ::: First Non-Alpha Release.
#>>Download LINK <<#
http://www.mediafire.com/file/rhmimk5dojt492b/DirtyCow + Double SuperSu Injection.zip
########################################################################
######Screenshot's######
PROOF.SH <<--- Click-able --- <<<
Kernel + SEpolicy Informations <<--- Click-able --- <<<
Succesfully Granted Termux Root <<--- Click-able --- <<<
SuperSu is at Lastest V2.82 <<--- Click-able --- <<<
######PROOFS######
But Technicly this works on ANY Android , Tested on 5.1.1, 6.0.1, 7.0,
SM-G920V
My Bootloader is Locked/ Doesnt Exist?
I use FLashFire, which will be installed using this method, but i also used Official TWRP to understand how the S6 Bootloader IS Picky I will only Accept STOCK.
I SUCCESFULLY Booted in TWRP with FISHY... I was working on TEMP Recovery and i thought...(Useless because you cant MODIFY THE OS -_- else Bootloader trigger)
But how about Booting a ROM instead of TWRP?! So i am working on this right now, Currently have a WORKING METHOD For Lg G4 h812 and succefully Booted Custom ROM)
This(Dirty-Cow Exploit) also Worked for my LG G4 But with Different Security Disabling Methods(OEM UNLOCK), Bluestack, Ubuntu 16, My raspberry PIE.... Pretty much... ARM32/64... but there is one for EVERY arch anyway.
I wish you guys a GOOD root.... Not to Exploit the exploit.
Scan.rar :Note: IF This is INFECTED"... well i had no clue, i want to Declare that i have NOT inject any Virus, i just Found the files on a XDA and Slighty modified a Root-Tool and Merged it with another, Writed .bat to make it Function at least with VERIZON and ROGERS.
::::::::::::::::::::::::::::::::::::::::::::::I want also to Declare that IF IT IS INFECTED , PLEASE REPORT BECAUSE... i am RUNNING THIS on my phone.*facepalm*::::::::::::::::::::::::
https://www.virustotal.com/fr/file/...19598dfec975f6511e20ed70/analysis/1519884568/
6 / 58
Antivirus Résultat Mise à jour
Antiy-AVL Trojan/Linux.TSGeneric 20180301
Avast ELF:CVE-2016-5195-T [Expl] 20180301
AVG ELF:CVE-2016-5195-T [Expl] 20180301
CAT-QuickHeal Exploit.dirtycow.A18c7 20180228
ESET-NOD32 a variant of Android/Exploit.CVE-2016-5195.A 20180301
Ikarus Trojan.AndroidOS.Exploit 20180228
Download Link ::
http://www.mediafire.com/file/n2r3obszwkxf31n/Arm32-DirtyCow-MixSploit.rar
Click to expand...
Click to collapse
Modifying recovery to boot ROM go anywhere?
Hi, I'm having trouble choosing the right section, anyway..
After more than a year i managed to correctly install ADB drivers, because before i installed Google driver, when i noticed i must install Motorola driver , the removing of previous one did not successful done, so the Motorola one did not installed well, by manually removing files it succeed.
But now another annoying not previewed issue, i need to exchange a file in /system/etc both in my tablet and my Motorola moto C tel. , it needs to remount system part. in r/w but to do this need to restart adb as root but with 'adb root' this is the answer:
adbd cannot run as root in production builds
my system is 7.0, what can i do?
You can install a temporary root to run shell-commmands what require root-rights like mount in ADB:
Code:
adb devices
adb push <FULL-PATH-TO-SU-BINARY-ON-PC> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'mount -o rw,remount,rw /system'"
I have two questions, i don't find any su command available in the net.
I don't understand how it is possible to have to do all these hard maneuvers with a debug tool, i think it might be simpler.. why there's a command remount or root if it doesn't work?