H810 Root/Unlock 20n? - G4 Q&A, Help & Troubleshooting

So I got an ATT LG G4 the other day. I've been looking around on the web and the news doesn't seem good for root and/or bootloader unlock. I've looked everywhere but seem to only find guides for 5.X.X. Currently, it's on the 20n build which is Marshmallow. How would I go about getting root or custom ROMs? If I'm on 20n, is it still possible to flash the rooted image for 10G/O (?? I can't remember which one I saw that was a rooted img).
Mainly, I would like to adjust DPI and change my emojis to stock and boost volume, so I would be content with just root. I just need some clear answers. It seems that Marshmallow just came out recently and there's not a lot of info.
If any can share, that'd be great! Thanks

Don't do it
there is a security feature that detects a partition rollback and disables the phone if you try that method. I'm looking for a way to do it myself. We are waiting for an unlocked bootloader for now.

Related

Can you root the latest update and use xposed? Pros and Cons?

Cant make much sense of all these threads. Always used a highly customized and unlocked international Nexus. But this US Verizon phone seems to be difficult to customize.
usern ameisval idandnot said:
Cant make much sense of all these threads. Always used a highly customized and unlocked international Nexus. But this US Verizon phone seems to be difficult to customize.
Click to expand...
Click to collapse
You definitely can root this phone and install exposed. The biggest issue is that the bootloader is locked and doesn't look like it's going to be unlocked anytime soon. So for the most part, no custom roms. Another downside if that of something goes wrong on root, your options to get your phone back up and running are limited to using a KDZ file if one is available for the specific version your trying to root, or push a stock system image if you made a back up. Sf today the latest 13b software has a KDZ thanks to autoprime. I haven't done much customization, so I can't shall to that.
Where can find a step by step guide how to flash a rooted image? What precautions are necessary to get back to stock in case something goes wrong? I need to costumize my phone.
usern ameisval idandnot said:
Where can find a step by step guide how to flash a rooted image? What precautions are necessary to get back to stock in case something goes wrong? I need to costumize my phone.
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
Following this guide will allow you to make a backup of your stock system image and root your own image. It's easy and straightforward.
Google lg g4 root xda
From there, you'll see a link to a low effort root, that teaches you how to flash system image.
I tried KDZ method but the KDZ image I loaded wasn't rooted...
It is super easy to do. I will say the low effort root page should be updated with a * or something to say hey, the latest version for the verizon lg g4 is 13b. Also the flashfire method to install xposed takes 15 minutes. I also like using g4 tweaksbox.
This is my first few days with the g4. I have had the g3 since release. Much faster. Familiar. Liking it so far. Battery life seems great. But I am delaying greenify, amplify, etc, to see if I even need it.
Kinda shocked there isnt more activity around here tho!
I have successfully rooted my G4 and Xposed is up and running. I do have a kinda dumb question. Can i move my rooted.img & system.img to my external SDcard to save some space? Just want to make sure. Thank you in advance.
NVM found my answer.

TWN downgrade and root. -- Success!

Hi guys,
I've recently picked up a grey import G4 on ebay and opened it up, tried to unlock the bootloader and found out that it's a TWN model (Taiwan), so no unlock for me.
I'm wondering if, first of all, it can be downgraded from 6.0 MM to 5.1.1 LP and from there, injected with root?
I intend to eventually copy over various items via Titanium Backup, but require root first.
I've had a little look around but I'm not sure if this specifically is possible.
Help from seasoned veterans is appreciate.
EDIT:
title change, downgrade success, root success!
Found this thread: http://forum.xda-developers.com/g4/general/815-taiwan-v10f-t3298685 which provided the current/latest (to my knowledge) kdz and root system image.
Followed this thread: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803 to downgrade from MM to LP. (TIP: LGUP looks for .tot files, but feed it the .kdz anyway)
Followed this thread: http://forum.xda-developers.com/showpost.php?p=62028523&postcount=2 to then flash the rooted system image once downgraded.
Bonus:
Followed this thread: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593 and installed Xposed too. (I'm using xposed-v80-sdk22-arm64.zip)
Currently running 5.1 LP just fine. Hopefully it stays stable. It's exactly what I'm looking for right now.
Cheers everyone who looked at this thread and the authors of these linked threads.
XDA is a pretty awesome place.
It seems downgrade and root is possible on most models. I would assume its on yours. Worked fine on my Canadian H812. I used LGUP to downgrade then used the original method to root, root injection may possibly work too.
milan187 said:
It seems downgrade and root is possible on most models. I would assume its on yours. Worked fine on my Canadian H812. I used LGUP to downgrade then used the original method to root, root injection may possibly work too.
Click to expand...
Click to collapse
To clarify: I say downgrade because apparently there's little hope for the moment of ROOT on MM.
Is there any extra risk downgrading stock LG MM to a pre-rooted image of LP?
I would assume I could flash the international/europe h815 version with root over mine -- H815 10D EUR or H815 10c EUR, assuming you can get a hold of either -- but wondering it this is the best or right choice. I don't want to end up with a broken phone, bootloop, or whatever seeing it is brand new.
I want to make sure what I would be doing is the best way to do so, and am willing to wait a little extra to make sure I do it correctly.
I've looked but haven't found a TWN rooted image, but it doesnt mean it doesnt exist.
Cheers, and thanks for the input

Help with best root method out of the following:

Hi, been away a while and have spent the last 3 hours reading but still a little confused and don't want to brick my wifes 'new' lg g4 (13b). I would like to root but am getting confused w/ all the possible options:
-lgup: https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
-low effort root: https://forum.xda-developers.com/g4...t-tmo-vzw-intl-variants-soon-root-lg-t3164765
-New Root Method for LG devices: https://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
-"13b rooted system image & KDZ" : https://forum.xda-developers.com/verizon-g4/general/vs986-rooteddebloated-t3256814
-VS98613b saved image and rooted: https://forum.xda-developers.com/verizon-g4/general/vs98613b-saved-image-rooted-t3258794/page8
I simply want the safest / easiest method to root and install twrp. I'll likely flash the multi-window mod and hotspot mod and thats about it. Also, if there is a debloated stable rom i ought to flash on this please advise as well. Thanks for any tips!!! I'm really in a frozen state and don't know what the latest best options are available since i rooted my G4 nearly two years ago!!!
No TWRP available for VS986 due to locked bootloader.
Easiest way would be to use a saved rooted image.
I used the method in second link to learn how to root the image myself.

Need Help - New to this

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.

New Z2 Play User Questions

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.

Categories

Resources