I have the LG Power (aka LG Leon) from Tracfone, which has a protected bootloader. KingRoot roots it, but its su binary is not fully compatible with all root apps. Fooling around with KingRoot, I found a way to ultimately root the phone with SuperSU, using KingRoot as a "mule" app to do it.
Warning: As always, you can make your device unusable by attempting to root it. You follow these instructions at your own risk.
Download KingRoot from kingroot.net, install it, and let it do its thing. You may have to try a couple or three times before it gains root.
Install SuperSU from Google Play. Open it and "Cancel" the prompt to update the su binary (it won't work, yet). Configure SuperSU to your preferences, and grant it root permission when KingUser asks.
Install a root browser such as ES File Explorer from Google Play, open it, and enable root access. KingUser should prompt to allow it root.
You will need a copy of the SuperSU su binary. It is not yet in the /system/xbin folder, as KingRoot has control over that. You can get it through ChainFire's site, or from the "root.zip" file attached to this thread: http://forum.xda-developers.com/fir...ne-supersu-t3105546/post60669196#post60669196
Load the mule with the payload. Browse to /data/data/com.kingroot.kinguser using the root browser and REPLACE all instances of "su" with the SuperSU version of the su binary. You will find at least two deeply embedded in the directory tree.
Now wait, possibly for several minutes. KingRoot will eventually check its integrity and find that the installed su binary is different than the one it its data directory. It will reinstall automatically and test its access. If successful, you will see a SuperSU prompt to grant KingRoot superuser access! :victory: Deny it.
Now open SuperSU again and allow it to upgrade the su binary through the "Normal" method. It should succeed.
Restart the device.
Open SuperSU again to test root access. Open a few root apps such as the root explorer. SuperSU should prompt to grant root access.
You can uninstall KingRoot (and Purify, if you want).
Some issues that I ran into that may or may not be of concern to you:
After rooting, my device became unstable and would freeze a few minutes after restarting. I had to take out the battery to restart it. I was messing around a lot with it, so most likely it's something else I did. However, if this happens to you, go into "Safe Mode" by powering it on, waiting for the LG Logo to appear, then holding the "volume down" button until you see the default launcher screen with "Safe Mode" in the lower left corner. Give it many minutes to settle in, then restart normally. This restores a few things to default (such as your widgets, which you will have to re-configure).
SuperSU asked me a second time to update the su binary. I allowed it, and it never asked me again.
If all else fails and you can't get a stable root, install KingRoot again and have it re-root the phone.
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
this not work on H340n with android 6.0
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Corbow6 said:
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Click to expand...
Click to collapse
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
voluptuary said:
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
Click to expand...
Click to collapse
Thank you! I'll try it out. What do I have to lose, recovery?
gsearle5 said:
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
Click to expand...
Click to collapse
I just updated to version 86 without a hitch.
Looks like I celebrated too soon, while you can enter recovery with the IMG I posted above it won't actually do anything... except make you have to pull the battery out. Least you don't get an error in the top left corner anymore so there's that.
Just installed the new Xposed Framework self-installer for Lollipop on this device (LG Power). It worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=3034811
Related
I was just been going through different forum threads and found that most people find it difficult to root there device,
So I decided to write a easy tutorial to do that(not ment for Android 5.0 Lolipop, yet)
things you should know before following this:
a. it MIGHT(not necessarily)trigger KNOX(on samsung some devices)
b. you need unlocked bootloader in case you have a sony device.
Click to expand...
Click to collapse
these are the steps you need to follow to root your device, it is a general method and SHOULD work on almost all devices(might not work for few):
1. First of all you are supposed to know what device you are using, and if you know what device you are using, you are ready to proceed
2. Next thing you would need to find is the process needed to flash image/md5 to the device you want to root(might trigger KNOX)(unlocked bootloader needed)
3. So if you don't know how to flash image/md5 to your device, just search here, on XDA for how to install cwm recovery(for example) on *your device*(might trigger KNOX, google it to know if your device have it or not, will void your warranty)(unlocked bootloader needed)
4. Cwm recovery is a custom recovery(few more are there too) for almost every device (you can make one if its not available yet, just search XDA)(if not, this is probably not a process you can follow, find some other)
5. When you have successfully installed the cwm recovery to your device, then you would need to know how to enter recovery mode on your device, generally, holding power+volume up keys for few seconds when the device is off will get you to recovery mode, and on Samsung devices, it's power+home+volume up keys that are supposed to be kept pressed to get to recovery mode, and if any of these don't works, just google "how to enter recovery mode on *your device*"
6. Now you need to download a supersu update zip from: HERE.
7. Place it anywhere on your phone and now turn off your device and boot to recovery mode (by process explained above)
8(a). When you enter recovery (any custom recovery you can find), there's an option to install zip from SD card (external or internal)
8(b). Select it and find out the supersu zip you downloaded above and then select it and confirm to install it
When it's done(installing that zip), you are done, you had rooted your device successfully and now you can enjoy the root access!
Just reboot your device normally and you can find SuperSU icon in the app drawer(if you don't, just install it from play store), open it and it will simply open with an option to follow them
If for some reason, supersu says super user binary is not installed and supersu can't install it, then it's not rooted, and you can retry the process of installing supersu update zip by booting to recovery and installing it from there (explained above)
It is not supposed to happen (the problem stated above) as you are not doing any wrong thing during the process (if you followed my steps)
So, that's it if you have any problem during doing this, just reply and I will try to solve it for you
tell me if it didnt worked for you, i will make a list of devices that are not able to be rooted by this( i guess there wont be any.)
Hit thanks of I helped you
Sent from my SM-T211 using XDA Free mobile app
Ok I did this and it triggered KNOX... I let SU try and Disable it, but it's been trying for over 30min.
Edit: Re-booted and let SU try again. It disabled KNOX it said.
Many devices are not able to root via this method, especially those with locked bootloaders. There is no generic root all method as there are too many variations on software, hardware, and everything in between.
run2jeepn said:
Ok I did this and it triggered KNOX... I let SU try and Disable it, but it's been trying for over 30min.
Edit: Re-booted and let SU try again. It disabled KNOX it said.
Click to expand...
Click to collapse
well, you should know that flashing anything will trigger knox, its not stated in this post because when i created it, i didnt knew about KNOX, i will add it now.
es0tericcha0s said:
Many devices are not able to root via this method, especially those with locked bootloaders. There is no generic root all method as there are too many variations on software, hardware, and everything in between.
Click to expand...
Click to collapse
ok thanks
i changed the post and stated that this process need unlocked bootloader thanks again
No clockworkmod recovery needed. And this won't break root on system updates you will just have to update su binary after each system update.
(1) Download developer ROM from here http://en.miui.com/download-101.html#164
(2) Copy file to root folder on phone storage and rename the file to update.zip.
(3) Power off the phone then hold volume up and power key till mi logo pops to boot into recovery mod.
(4) Select language, click volume down to navigate to 'Install update,zip to System One' and hit power button to select.
(5) Wait for Install to complete (usually progress stops at 98% for while but do not panic and wait for it to complete).
(6) Now hit Reboot then Reboot to System One after update and reboot go to security enable root permission install Super SU from playstore, open the app and update Su binary.
(7) Now phone is rooted, Super Su is installed, Su binary is updated so you can go and disable root permission from security app and let Super Su manage root permissions instead.
Note- when ever you install an update from phone it will install update to system two
and when you update from recovery it will install update to system one
I am not a DEV, just sharing what I know.
Which method is recommended? Rooting with package through recovery or through system settings menu within MiUi?
i download the developer rom when i went to flash it, it says its for pieces your device is cancro . so whats the problem /
mandarpalshikar said:
Which method is recommended? Rooting with package through recovery or through system settings menu within MiUi?
Click to expand...
Click to collapse
You can use any method, just use same method every time so one of the two system stays stock.
Babu-Ji said:
i download the developer rom when i went to flash it, it says its for pieces your device is cancro . so whats the problem /
Click to expand...
Click to collapse
Try flashing it from recovery. And make sure you downloaded developer ROM for 'WCDMA/CDMA China' and not 'TD'.
vikie said:
No clockworkmod recovery needed. And this won't break root on system updates you will just have to update su binary after each system update. Also from what I know this method does not void your warranty.
(1) Download developer ROM from here http://en.miui.com/download-101.html#164
(2) Copy file to root folder on phone storage and rename the file to update.zip.
(3) Power off the phone then hold volume up and power key till mi logo pops to boot into recovery mod.
(4) Select language, click volume down to navigate to 'Install update,zip to System One' and hit power button to select.
(5) Wait for Install to complete (usually progress stops at 98% for while but do not panic and wait for it to complete).
(6) Now hit Reboot then Reboot to System One after update and reboot go to security enable root permission install Super SU from playstore, open the app and update Su binary.
(7) Now phone is rooted, Super Su is installed, Su binary is updated so you can go and disable root permission from security app and let Super Su manage root permissions instead.
Note- when ever you install an update from phone it will install update to system two
and when you update from recovery it will install update to system one
I am not a DEV, just sharing what I know.
Click to expand...
Click to collapse
Its not available for any snapdragon 800 variant. Its just for TD and CHINESE version of MI3. And even if somehow works on other MI3. If you flash this you will still void warranty as it's not officially given by xiaomi.
Now you will say how will they know. Its the same phone. They will known when you will go to claim the warranty in your country. I don't think you will go to china to claim the warranty of your phone and even if you do go to china for that
a. Your phone should have international warranty.
b. And that person giving you warranty should be stupid enough to ignore the country mentioned in your bill and also ignore the fact that no developer version is available for your country.
Lots if if's and buts and travelling just to claim warranty.
Okay, I was not sure about warranty thing any way. Will edit that. Also you could have just replied, didn't had to quote the whole thing. I am pretty sure buying new phone would be cheaper than going to china for warranty. Also I am sure people who use xda and flash custom roms would not cry for warranty. And this is no twitter so won't argue on this further.
I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
Magisk comes with a ton of benefits, including a powerful systemless interface, as well as keeping device certification and SafetyNet intact, allowing you to use apps like Snapchat, Pokemon Go, Super Mario Run, and so forth.
Credit to @mcopeland1003` for the heads up on Magisk.
PREREQUISITES
A PC
Odin
Galaxy Core Prime not rooted by any other method, and has the stock kernel intact. (If you want to OTA update your phone be sure to do that before you root your Core Prime with this method!)
Unofficial TWRP SM-G360T1
Installing TWRP Recovery
Enable OEM Unlocking in developer options if you haven't already.
Then, put your device in download mode by pressing Power+Volume Down+Home Key.
Launch Odin on your PC, then connect your device to your PC.
Click on the AP Button and browse for your downloaded TWRP file.
Hit Start.
In my experience, my Core Prime for some reason did not let TWRP install on my phone; when I decided to boot into recovery it booted into Samsung's stock recovery. To get around this: before flashing TWRP, go into the options tab of Odin and uncheck Auto-Restart. Then flash TWRP and then remove the battery of your phone and unplug your device. This will not damage your device.
Now, boot your phone into recovery by pressing Power+Volume Up+Home to make sure TWRP's there. You can now boot back into android.
Installing Magisk
Sideload the Magisk Manager APK from this link onto your device.
Now we need to download the latest Magisk zip file to flash through TWRP. Open up Magisk Manager. Press the giant Install button, then Install, and finally Download Zip Only. The latest Magisk flashable zip will start downloading.
Once the file has finished downloading, boot into TWRP by powering off your phone then pressing the Power+Volume Up+Home keys simultaneously. Head into Install, and browse to /sdcard/MagiskManager. You should find a .zip file with a name like "Magisk-v16.0(1600).zip". Flash that, then reboot into system.
By the way, don't let TWRP install SuperSU. It'll pretty much defeat Magisk.
And there you have it, Magisk giving you root in a systemless fashion, without breaking Wi-Fi, device certification, and SafetyNet. Hope this guide helped you guys out.
Be still my heart
Glad you found it useful. I use it so my 7 year old can play his pokemon games and stuff like that, but use root for the extra storage.
twrp has official release for this phone i seen and used its app to add to recovery once rooted .. wish i didnt use first root method i seen as phone no wifi and cant get reconition from pc
It worked for a while then went belly up !
FazPhantom said:
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
.
Click to expand...
Click to collapse
Hello,
Using your method which worked for me initially on an SM-G360T1 then on bootup I got the dreaded Wrong Binary FRP enabled message. Since then I have flashed back to the stock ROM but the minute I install TWRP it won't boot past the Metro PCS screen. It just sits there and won't go any further. I have done this multiple times in hopes that it will somehow 'fix' itself...(yeah right) but that never happens.
One of the membes in the Androidcentral group sent me here to ask about the problem. I can't undestand if the frp was tripped by something, why did the phone work OK for 2 weeks and then quit? It would seem to me it would have done it right away but yet it worked fine with TWRP and magisk. I did NOT install any more apps or ROM's to the device that's what puzzles me.
Can you help me with some ideas? You guys are the decided experts and I am a newbie to all this but trying hard to learn as I go.
Many thanks in advance,
W T
My Padfone S screen is broken, fully black and out of function. I can't follow the some of the root guide to install TWRP and load the SuperSU zip to it because the screen is broken. I can just use my Padfone with the padfone station, so is there any way to root it? Thanks.
I did my Padfone X about an hour ago! I realize its not the same, but I'll give you a run-down of what I did and maybe it will help!
So I rooted it the dirty way first with KingoRoot, because I just really wanted to debloat. Downloaded the app, nothing complicated about it, I just don't like it and personally I don't trust this root provider for a daily driver. Prefer SuperUser or SuperSU.
Next, I spent a long while poring over threads full of dead links trying to find a CWM or TWRP recovery, and finally stumbled across one, which also contained the flashable bootloader unlocker. So I put the phone in fastboot mode (power the phone off, hold power + vol up) and ran "fastboot boot recovery.img", which is what I renamed the TWRP recovery file to. To my surprise, it booted and mounted the internal storage! So I copied the bootloader unlocker zip, flashed it, rebooted. Entered fastboot again, "fastboot flash recovery recovery.img" and boom! TWRP installed and working.
My next step will be to replace KingoRoot with SuperSU. I tried it via the normal flashable zip, but it failed somehow. The flash completed but when I rebooted, the SU binaries were missing or something. I lost root access. Good thing that the backup and restore works in TWRP
I'll post a full "how I did it" guide when I'm done. Until then, hopefully something I learned will help you!
yes, it can be root
Hi, I use TWRP 3.0.0 from quarkx
http://quarx2k.ru/asus_padfone_s/
and install magisk
https://forum.xda-developers.com/app...mless-t3473445
it's really work for MM rom