I'd like to root my G710TM and run the Lineage OS, but predictably could not obtain an unlock key from LG for the bootloader. I find a bunch of threads from a couple years ago with people trying to root this model. I am wondering if anyone was successful and how they did it.
I'm still trying to root mine too. I want to update to custom android 11
One year later... I guess the G710TM will stay stock forever
Related
Just got the phone a few hours ago and want to root it and install Xposed. But I'm not sure what's the best path.
So far it seems like VS98610B is an old version nobody is using and that if I root it, I won't be able to upgrade in the future without breaking the phone, is that correct?
If I go to "Check for new system update" it asks if I want to update to 11A. From what I understand from this post http://forum.xda-developers.com/showpost.php?p=64116024&postcount=362 is that I want to take the update, then after it installs that update, it should ask to update again to 13B? And that it is this 13B version that I root?
Am I able to unlock the bootloader on any of these versions? Why does it ask me to go to 11A instead of straight to 13B?
All I can say is that you are damn lucky and DO NOT update or flash a non 10B image of you have any desire to unlock the bootloader and use custom ROMs and such
DerekZ10 said:
Just got the phone a few hours ago and want to root it and install Xposed. But I'm not sure what's the best path.
So far it seems like VS98610B is an old version nobody is using and that if I root it, I won't be able to upgrade in the future without breaking the phone, is that correct?
If I got to "Check for new system update" it asks if I want to update to 11A. From what I understand from this post http://forum.xda-developers.com/showpost.php?p=64116024&postcount=362 is that I want to take the update, then after it installs that update, it should ask to update again to 13B? And that it is this 13B version that I root?
Am I able to unlock the bootloader on any of these versions? Why does it ask me to go to 11A instead of straight to 13B?
Click to expand...
Click to collapse
Just my opinion but holding for a bootloader unlock is pointless and no you can't unlock it on any version. I waited for a year for the note 4 to get root or unlocked and never did. As days pass it's less likely we will ever see it unlocked on the g4.
To root take the OTA and get to 13b then follow the root guide in the forums....with root, xposed, and a little debloat this phone is awesome!
Awesome.that's what I was looking for. If it's already been since june and nobody has cracked it, that's not looking too good. My only worry now is why it's not taking me straight to 13b? It will take me to 13b after 11a right?
Also where is a good up-to-date root thread? There's nothing stickied.
If someone is on the verge of cracking the bootloader, how do I root this version so I can holdout, without killing my ability to upgrade in the future?
I'm also really interested in getting the fm radio working.that was one of the deciding factors when getting the phone. I did not know that Verizon crippled it.
EDIT: Also what's the benefit to upgrading? 10B is already android 5.1 so what is gained?
DerekZ10 said:
I'm also really interested in getting the fm radio working.that was one of the deciding factors when getting the phone. I did not know that Verizon crippled it.
EDIT: Also what's the benefit to upgrading? 10B is already android 5.1 so what is gained?
Click to expand...
Click to collapse
I never ran on 10B, so I don't know what benefits there were going to 11, however, 11 to 13b saw major improvements to touch responsiveness for most people (I never had touch issues on my phone, so I don't know on that count, but maybe I just never noticed); I also found that the phone performs a lot better and the battery lasts a bit more.
ericralph said:
All I can say is that you are damn lucky and DO NOT update or flash a non 10B image of you have any desire to unlock the bootloader and use custom ROMs and such
Click to expand...
Click to collapse
The rumored unlocked bootloader is vaporware. There has been no update on the status of it, especially for the Verizon variant. See here: http://forum.xda-developers.com/g4/general/unlock-unofficial-bootloader-unlock-t3222737
I've already considered of foregoing the mythical v0 unlock bootloader (VS98610B firmware, aka 10B) and move up to VS98613B rooted to enjoy all the fixes to the phone. No point of waiting any longer without any updates.
I have now spent several days in trying to root, boot unlock and every time I get that dreadful "permission denied", if you are on any build from 179 (I think) and upwards, no rooting or unlock tool will work here, you will end up going through all kinds of recovery and even xFSTK-Downloader, and simply waste your time.
I just went through the xFSTK-Downloader process in order to get my phone back to life, it was stuck in the Fastboot loop after trying to run the restore.bat to unlock it for M builds, so I thought I would create an entry here to warn people not to attempt any rooting or unlocking until you have downgraded your build.
Good luck
LBN said:
I have now spent several days in trying to root, boot unlock and every time I get that dreadful "permission denied", if you are on any build from 179 (I think) and upwards, no rooting or unlock tool will work here, you will end up going through all kinds of recovery and even xFSTK-Downloader, and simply waste your time.
I just went through the xFSTK-Downloader process in order to get my phone back to life, it was stuck in the Fastboot loop after trying to run the restore.bat to unlock it for M builds, so I thought I would create an entry here to warn people not to attempt any rooting or unlocking until you have downgraded your build.
Good luck
Click to expand...
Click to collapse
I never had any problems with rooting or unlocking LP .184 and now there is even a guide to root and unlock the MM beta (and it works great too). Maybe if you tell us exactly what you are doing we can help you
tabletalker7 said:
I never had any problems with rooting or unlocking LP .184 and now there is even a guide to root and unlock the MM beta (and it works great too). Maybe if you tell us exactly what you are doing we can help you
Click to expand...
Click to collapse
did you perhaps root and unlock your device prior to upgrading to build 184 initially? I have simply followed the threads to root and boot unlock, I actually did manage to root it with one of the 180 builds, but I still got permission denied, boot unlocker never worked for me and gave me lots of problems as I mentioned. If you look at the permission denied threads, I was having the same problem.
I flashed the MM beta before shakalaca ame up with the downgrade method. When you wanted to go back to LP you had to use xFSTK and the Asus Flash Tool then. That locked you down. One click unlock and method 3 for root worked on my phone. My son recently wanted xposed for youtube adaway on his zenfone 2 and his was never rooted or unlocked and the same worked on his .184 LP. You still have not mentioned in this thread what model zenfone 2 you are having trouble with - my home has 3 ze551ml 4GB/64GB phones and all 3 rooted and unlocked with no problems.
Hey guys, i'm having a lot of trouble rooting my LG G3. It is the D855 unlocked variant running Android 5.0, Kernel 3.4.0, Soft Ver V21a-EUR-XX. (If there is any more info needed, let me know.)
I've must have tried 6 or 7 different root methods but they all fail in various ways. I've used IORoot, OneClick, Towelroot, KingRoot, Stump Root and more. Can anyone suggest a viable root method for me or know why all these root methods fail?
EDIT: I upgraded to 6.0 and i'm just gonna stick with that for the time-being instead of installing a custom ROM. I tried to delete the thread but couldn't see where the option was.
Thanks,
Tom
Hmm I think 5.0 was supported, so perhaps you are not doing some of the steps properly? Are you following the steps in one of the tutorials around the forum?
Anyways newer versions cannot be rooted, you need to downgrade to KitKat first, root, install custom recovery and then install a custom ROM which will update your OS.
I highly recommend a good clean AOSP based 7.1.1 ROM for performance -- LineageOS is a great contender.
My LG G3 is very fast and snappy on AOSP 7.1.1 and it's 2 years old. As such I don't feel the need to upgrade my device for at least a few more years (as long as possible really) on the contrary of some people who seem to like spending money on a new phone every year (which I can't afford to do anyway -- both money wise and environmentally wise)
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.
Hey guys, been lurking until my device finally got here. I'm coming from an LG G3 (yes, I hold on to phones for a long time) which I was able to root pretty easily, so I am not unfamiliar with TWRP, backups, recovery, etc.
I got an unlocked US -01 variant that comes preloaded with Nougat 7.1.1. I haven't connected to a service provider yet. I have notification of a system update to NPSS26.118-24-6 which looks like the Sept 2017 security update.
I wanted to know if it was ok to OTA update and then root. I do want Oreo, but I don't know if that is available OTA in the US yet.
Also, do I still need to contact Motorola about unlocking the bootloader with the option to "OEM Unlocking" available in developer options?
Thanks everyone!
You can update normally before rooting but if you root, be aware that you could end up bricking the device if you try to update while being rooted.
I would suggest you read the guides here in XDA if you really need root, but be aware of problems that may appear.
Fixing a LG device is pretty easy compared to a Moto device.
Regarding unlocking the bootloader, you only need to follow the steps in the Moto site, they send you a code to unlock and everything.
victorhbm15 said:
You can update normally before rooting but if you root, be aware that you could end up bricking the device if you try to update while being rooted.
I would suggest you read the guides here in XDA if you really need root, but be aware of problems that may appear.
Fixing a LG device is pretty easy compared to a Moto device.
Regarding unlocking the bootloader, you only need to follow the steps in the Moto site, they send you a code to unlock and everything.
Click to expand...
Click to collapse
Thanks Victor. Like I said, I have been lurker around the forum for a while now. I think I have a pretty good grasp of the steps for the Z2 Play from a few sources. There just isn't quite a thorough and comprehensive guide or development like other phones I have had.
So I can OTA update and then root if I wanted to. I know never to OTA after rooting.
My LG crapped out on me. I think it's overheating. But you are correct, it is very easy to take apart and troubleshoot. I basically cooked the motherboard at 360 degrees F for 10 minutes in the oven and got it working again for about 4 weeks until it crapped out again.