Root Root exploit = easier rooting without having to flash the whole firmware

[livsantos]

Ok, I had some time today with windoze7 and managed to get this to work. It involves replacing(gasp) the official LG drivers. Anyways, here's a quick rundown of how I did it. If somebody can confirm that this is working for them, then I'll add it to the first post.

First, setup the drivers. You need WinUSB drivers installed for 3 of the interfaces provided by the phone - numbers 0, 2, and 3. Install the newest version of Zadig.exe (libwdi - Browse /zadig at SourceForge.net). Click options->List all devices. It should populate the dropdown list. To install a driver, you need to select it in the dropdown, then click the big "reinstall driver" button. Do this 3 times; CDC Serial (Interface 0), LG Android USB Device (Interface 2), and LG Android USB Device (Interface 3).

When you're done, you can verify it was done correctly by looking for these 3 Universal Serial Bus Devices at the bottom of the device manager.

Download the lgoeExploit program for windoze. Download lgoeExploit.exe from Sendspace.com - send big files the easy way
md5sum - 274ad4fb92ba3a2a8d8d180cebf840c9

Run the program.

After a successful install of exploit, is the phone suppose to reboot automatically? Mine didn't. I'm wondering if I'm doing something wrong.

 

[giantpune]

No. Look at the end of step 6. When you type that last "adb reboot" is when it reboots and starts up normally with root.

You have to start at the first step in the first post and continue through all of them unless it tells you otherwise. That post you quoted was just 1 little section where I was trying to get a program to work correctly under windows. That section alone won't do anything cool. It needs the stuff that comes before and after it.

 

[jwiMT]

Hi,thanks for the guide.I am using Linux Mint Debian.I have a problem.I have the VM OE NOT activated and when i use ./adb devices i get ?????? no permissions..Do i have to activate phone for your guide to work?Also i use MAC OSX and do ./adb devices and it will detect it and give me a device number.On MAC OSX i go to install the Ministro part and it says could not find ministro to install.Any ideas?Thanks

 

[giantpune]

On kubuntu at least, i had to setup udev rules for adb to be able to access the phone without running as root. Google "adb udev" for help in that department.

As far as the ministro goes, yes, you probably need to activate the phone, or at least connect it to wifi. The ministro program goes out onto the internet and downloads some libraries. I have used it without issues on an android emulator and it is able to get the required libraries, but have not ever tried it on a real device which was not activated. If it comes down to it, you can setup an android emulator with the SDK, then install ministro there, let it download the files, and then use adb to pull them from there and copy them to your real phone ("/data/local/qt").

 

[livsantos]

I seem to be stuck at step 2.
Step 2A gives me this screen, which I believe is normal.

Then step 2B gives me this:

Sorry for the problem guys. I don't know where I'm going wrong.
Any help would greatly be appreciated.

 

[giantpune]

Do you have the setting in your phone turned on to allow installing applications from untrusted sources? That needs to be turned on to allow "adb install ..." to work. Also, make sure you give the correct path for the .apks to install. "adb install -r <insert/the/correct/path/here/to/the/app.apk>". Note that if that path contains any spaces at all, you need to wrap it with quotation marks.

 

[Deleted User]

Where is the LG_OE_DiagMode-debug-unaligned.apk located? I can't seem to find it in the thread. I found the Ministro II.apk on source forge.

Thanks.

Edit: Never mind...I obvisiously did not read ALL the links...lol

 

[Deleted User]

Well done!! I put my phone back to stock and non rooted and put these instructsion through its pace and was successful.

One note:

I noticed after step 5, I didn't get the boot loop however, when I went on to step 6, I notices I had root right after entering the adb shell. After step 6 and the final reboot, when I went in to the adb shell this time, I had to type "su" before gaining the root "#" designation.

Thoughts on this? Job well done!!!

 

[livsantos]

./adb shell am start -n org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity

Is this the actual code to enter?
I gave the correct paths of the .apks to install, but I'm still getting an error when running the code above.

Yes, "Unknown Sources" is checked. Also, "USB debugging," "Stay awake," and "Allow mock locations" are also checked under Applications/Development.

 

[Deleted User]

./adb shell am start -n org.kde.necessitas.example.LG_OE_DiagMode/org.kde.necessitas.origo.QtActivity

Is this the actual code to enter?.

If you are in windows, do not put a "./" in front of adb. this is linux syntax

 

[livsantos]

No, I'm not using "./" in front of the adb.


Here's the path to adb.exe...

With the three .apks in this directory...

I ran steps 1A, 1B and 2A successfully (I think)...

But when I enter the command for step 2B, I get this error...

I'm running Windows 7 Ultimate x64. I have restarted both PC and phone. Enabled Applications/Development...USB debugging and Stay awake. As well as ticked "Unknown Sources"

Any more ideas what I'm doing wrong. Thanks guys.

 

[Hashtag]

No, I'm not using "./" in front of the adb.


Here's the path to adb.exe...

With the three .apks in this directory...

I ran steps 1A, 1B and 2A successfully (I think)...

But when I enter the command for step 2B, I get this error...

I'm running Windows 7 Ultimate x64. I have restarted both PC and phone. Enabled Applications/Development...USB debugging and Stay awake. As well as ticked "Unknown Sources"

Any more ideas what I'm doing wrong. Thanks guys.

I don't know if this is it, but whenever I did it, I put the three files in the SAME directory as the adb.exe. Try that out and see if it works.

 

[Deleted User]

I'm running Windows 7 Ultimate x64. I have restarted both PC and phone. Enabled Applications/Development...USB debugging and Stay awake. As well as ticked "Unknown Sources"

Any more ideas what I'm doing wrong. Thanks guys.

Check you phones app manager to make sure those apks installed. From the picture, it looks like you were still in the adb shell.

The "adb push..." installs should be back at the c:\... prompt

Should look like this:

 

[livsantos]

Check you phones app manager to make sure those apks installed. From the picture, it looks like you were still in the adb shell.

The "adb push..." installs should be back at the c:\... prompt

Should look like this:

Thank you! I feel like such a buffoon! :stupido3:

Thank you everyone! Phone is now rooted!

 

[Deleted User]

However, when I ran the program "Root Check," it says that it doesn't have "proper root access." I restarted the phone and checked again, it seems I still do not have root.

No problem. For applications to have root access, you need to install the super user app from Google Play:

https://play.google.com/store/apps/...wsMSwxLDMsImNvbS5ub3NodWZvdS5hbmRyb2lkLnN1Il0.

 

[giantpune]

I noticed after step 5, I didn't get the boot loop however, when I went on to step 6, I notices I had root right after entering the adb shell. After step 6 and the final reboot, when I went in to the adb shell this time, I had to type "su" before gaining the root "#" designation.

Thoughts on this? Job well done!!!

When you write the /data/local.rc file, and restart the phone, you are setting a property that says the phone is an emulator. When that happens, one of the cool things is that the adb shell is run as root. One of the side effects, at least in some cases, is that the phone is stuck in a boot loop. I've seen some other phones where the sound doesn't work and odd issues like this when running with the emulator flag.

So what you are doing here is using that emulator flag to get a root adb shell, using the root adb shell to copy the su binary into place, and then deleting the /data/local.prop file. That way, when you reboot the phone again, it is not running with that emulator flag, and you don't get the benefits and possible side effects from it. But you will now have the su program there for when you need it.

 

[Deleted User]

So what you are doing here is using that emulator flag to get a root adb shell, using the root adb shell to copy the su binary into place, and then deleting the /data/local.prop file. That way, when you reboot the phone again, it is not running with that emulator flag, and you don't get the benefits and possible side effects from it. But you will now have the su program there for when you need it.

Learn something new everyday!!! Thanks a bunch!

 

[rob11223]

Thank you for all the help, and awesome way of rooting. I'm wondering however, did I mess something up, or miss a step? Root Check says I have root, I can grat super user permissions, but in no file managers am I able to explore root, as no files come up, and android commander says I'm not rooted as well.

 

[Spiify]

Thank you for all the help, and awesome way of rooting. I'm wondering however, did I mess something up, or miss a step? Root Check says I have root, I can grat super user permissions, but in no file managers am I able to explore root, as no files come up, and android commander says I'm not rooted as well.

Download a terminal emulator from the market and type su in it. It should ask for su permission and a # should pop up. Aslo if you want to check through adb type adb shell then $ should pop up. After that type su the and # should pop up. Also are you using a file manager that has root access?

 

[rob11223]

Download a terminal emulator from the market and type su in it. It should ask for su permission and a # should pop up. Aslo if you want to check through adb type adb shell then $ should pop up. After that type su the and # should pop up. Aslo are you using a file manager that has root access?

Yes n yes I tried su it works.... But can't access root it comes up empty, or crashes

 

[Hashtag]

Yes n yes I tried su it works.... But can't access root it comes up empty, or crashes

What explorer are you useing? Because in some of them, you have to go into the app settings and check a box that says "root access" kind of thing.

 

[Spiify]

Yes n yes I tried su it works.... But can't access root it comes up empty, or crashes

Do you mean the folder named root is empty?

Edit: See the last post from Hashtag.

 

[rob11223]

What explorer are you useing? Because in some of them, you have to go into the app settings and check a box that says "root access" kind of thing.

I'll check int that a bit more,one i was able to view files, but only view. Android commander is a computer based program so I'd guess it could say no root if it wanted. Only one app bought up root access though, and clicking on files said I was denied. I havent tried again, since previous post, but I've rooted about 7 phones before, with the g1 seemingly being the hardest , before this.

 

[jwiMT]

Hi giantpune.Thanks for the udev solution,finally had time to get it setup and working.

Now it dawned on me why i couldn't download.I have no idea how to enter DIAG mode.Do i need the MSL everyone talks about or is there a code somewhere i can get?Thanks for all help..

 

[Hashtag]

Hi giantpune.Thanks for the udev solution,finally had time to get it setup and working.

Now it dawned on me why i couldn't download.I have no idea how to enter DIAG mode.Do i need the MSL everyone talks about or is there a code somewhere i can get?Thanks for all help..

For giantpunes method, you don't need your MSL. There is an app that you put onto the phone(Mirnova II), that will allow you to get into diag mode without your MSL. Just double check the instructions and run it again. Watch your phone screen. There will be a window that pops up with a big "Push Me", that will take you to the Diag menu.