[Root & Bootloader Unlock] Docomo Optimus G
Original source: http://www.androidpolice.com/2013/01...-lg-optimus-g/
adb backdoor: giantpune
Duct tape guru: jcase
bootloader: Team Codefire http://forum.xda-developers.com/show....php?t=2001655
Testers: Shados and germes81m
For giantpune : Paypal to email@example.com
For jcase : http://forum.xda-developers.com/dona....php?u=2376614
Files: (Verify the MD5s before proceeding)
MD5 (boot.img) = 175c1bdaabbbbcbd7a4b69a315057e5b
MD5 (hotplug) = 9fbef20822281a2dd546b3e43d8c30dd
MD5 (lk.img) = bc54a6a730658550713a0779b30bf6b7
MD5 (unlock.sh) = 3871c2dde3d6b1d99d27ffa4021c81d3
Fastboot Drivers (needed for windows):
This is an at your own risk kind of thing, if your phone becomes damaged or data lost, your
fault not mine. This does install a unsecured (ro.secure=0) boot image in the process, this
does potentially open your device to security risks (as do most customized firmwares.)
The Docomo Optimus G ships with a mandatory access control system, that prevents
remounting system, reading boot, executing some things as root, etc general pain in the butt.
We are using a backdoor found by giantpune (and later by Juggie). The backdoor is partially
broken on this device due to the MAC, so it does not yield a root shell for us. However we
can still use it with a couple extra steps to unlock the bootloader\s. We are also going to
install a modified boot img, that removes some of the phone's security features, and allows
us to actually have root access.
Graphic glitches will occur while in the bootloader, you will have to use the bootloader 'blind'
Follow directions exactly.
adb push lk.img /data/local/tmp/lk.img
adb push unlock.sh /data/local/tmp/unlock.sh
adb shell chmod 755 /data/local/tmp/unlock.sh
adb shell touch /sdcard/g_security
Disable USB Debugging, then enable usb debugging
Should recieve an error about not executing /system/bin/sh, this is what we want. If you
don't have the error, start over.
adb push hotplug /proc/sys/kernel/hotplug
Now toggle bluetooth once, and wait for your phone to display a garbaled screen (the bootloader).
If it displays a blank screen instead of a garbled screen, pull battery, reboot and run 'adb reboot bootloader'
If you see your device listed, continue. If not then find the proper drivers, and then
fastboot flash boot boot.img
adb shell /sbin/rootme.sh
If your phone does not reconnect to your mobile network, try rebooting it serveral times.
If it does not still, then reflash stock firmware.
We are using supersu, and the app https://play.google.com/store/apps/d...infire.supersu
Please don't send sensitive communications via PM or plain text email, -> my PGP key http://cunninglogic.com/jcase_cunninglogic.asc
Like Android security topics? Join our G+ community -> https://plus.google.com/communities/...07618051049043
My Bitcoin address : 1Newifz6yETTmbziCsZZstmHHPH6ejNr75