• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Optimus Elite root with an apk

giantpune

Android Enthusiast
Jun 13, 2012
452
476
It seems that people are having some trouble with rooting this phone. So here's an apk that will hopefully work right from the phone. So that means to fiddling with drivers, adb, compiling software, or any of that fun stuff. So far this has only been used on about 3 phones. Of those 3, all of them made it out alive and are probably still working. So now it is time for more of an open beta type deal.

Why are there 2 apks provided? Do I need to install both?
Poot-debug.apk is the miracle worker here. In order for it to work, it needs some libraries provided by Ministro.apk. If ministro is already installed, you can skip installing it again. If you don't have access to the googleplay app store, there is an apk for ministro attached to this post.

What does Poot do?
So, you got the Poot-debug.apk installed and ministro installed from somewhere. Start up Poot. After it gets some libraries using ministro, you should see a screen with a button at the top that says "Press here to poot" and a big white log window. Press that button and cross your fingers. It will try to do some haxxory and gain root access. Then it will try to remount the filesystem, write the su binary, and clean up after itself a little bit. in the log window, lines starting with "[+]" show good things that are happening. Lines that start with "[-]" show something that didn't work as expected. Assuming everything worked as it should, Poot will have written an su binary in /system/xbin. This binary goes with the Superuser app (not the SuperSU one). You'll want to install Superuser from the play store to finish the process and allow apps to use the su binary. There will be 2 more buttons pop up at the top of the screen that are links to the google play store for the free versions of a couple useful programs. You probably want to install the superuser one first, and then the rootcheck so you can verify that stuff is working.

What devices does this work on?
So far, it is only tested on a few versions of the Optimus Elite and the VM Venture. The bug it exploits has been around since 2009, and I found it in the source code for several other models. But I don't have access to any phones except the OE. At any rate, it shouldn't do anything bad. There is some error checking in place and in the event that something doesn't go right, it should fail at least somewhat gracefully without setting anything on fire.

For now, you can consider this an open beta test. I assume it will work. But it comes with no guarantees or warranties, expressed or implied.



20120906023004.jpg
20120907064632.jpg




Extra downloads:

Poot.apk with support for PCD Venture / ARM5 http://www.sendspace.com/file/dgid06

Poot.apk with support for One Touch 910 /ARM5 http://www.sendspace.com/file/6golr5

Poot.apk with support for Cherry w100 http://www.sendspace.com/file/oq37ui
*The cherry w100 version isn't 100% done and working, but it does work well enough to get the su binary installed. You have to reboot your phone each time you try the exploit.

Poot.apk vith support for h866c (get ministro from the play store, not from this post). http://www.sendspace.com/file/k9b3ks
 

Attachments

  • Ministro II.apk
    478.6 KB · Views: 33,323
  • Poot-debug.apk
    304.7 KB · Views: 40,581
If you do want it to work on yours, you're going to have to be more detailed than that.

Understandable. Downloaded both ministro and root-debug on the root of my sd card. Installed ministro first and then installed root-debug. It loaded up the libraries then went forward to the root option. Selected and showed everything went through just like your screenshot. Went on to add SuperUsers and then it hung up at the point to verify if it would work. Attempted again and it just showed the root screenshot, but selected to install rootcheker instead. It told me root not achieved. Root not completed. :(
 
Upvote 0
Selected and showed everything went through just like your screenshot.

If you get to the point where your screen looks like the screenshot in the first post, and there are no lines that start with a "[-]", then it most definitely worked. You may have an issue similar to what hashtag had.

The su binary was getting correctly written in as "/system/xbin/su", but he had run some other failscript previously that placed a different "su" somewhere in $PATH. So when apps try to use that su binary, they get the one installed by the failscript and not the proper one. I had him fix it by removing the broken "su" from every folder in $PATH.
 
Upvote 0
I added in another button that will check for situations like the one hashtag had. It looks at all the directories in $PATH to see if there is something called "su" in it. Then it does "ls -l ..." for that file so you can see the properties like the date it was created and the owner and all that crap. If it says anything besides "/system/xbin/ is the first su found" like in the screenshot above, then you may have problems. This app writes it only to /system/xbin. Any other one ended up where it is from something else you did.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones