Database Users

✮ [GUIDE] ✮ Unlock + Root + Backup + Restore + Downgrade (Updated 01/08/17)

ALL IN ONE GUIDE
Unlock + Root + Backup + Restore + Downgrade
For Moto G 2014 (2nd Generation)
titan (3G) : XT1063, XT1064, XT1068, XT1069
thea (4G/LTE): XT1072, XT1077, XT1078, XT1079
(Updated 1st August, 2017)​
Requirements:
1. Moto G 2014 2nd Generation (titan/thea)
2. Unmodified Stock ROM
3. Windows PC & Stable Internet Connection
4. Good Quality USB Cable & Functioning USB Port
5. Lots Of Patience & Common Sense
This guide is divided into 4 parts, read the below post & the comments before asking any question. Dont quote the entire post in the comments & ask what is only necessary.
PART I : UNLOCKING
This part is compulsory before proceeding to PART II. Your warranty will be voided after sending a request for an unlock key to Motorola used for unlocking process.
PART II : ROOTING
This part consists of 2 steps, flashing TWRP & flashing SuperSU Zip. After PART II is done, you can now flash custom ROMs, mods, scripts on your Moto G 2014.
PART III : RESTORING
This part is for those who wish to go back to the same stock firmware i.e. 6.0 to 6.0, 5.0.2 to 5.0.2 in case of boot loop, stuck at Motorola logo/boot-animation, BOOTLOADER UNLOCKED screen, OTA Update. You dont need an unlocked bootloader to flash the same stock firmware.
PART IV : DOWNGRADING
This part is for those who wish to revert back to previous Android version. i.e. 6.0 to .0.2 or 5.0.2 to 4.4.4. Please be very careful in this part as it can lead to dead devices if you dont follow the instructions correctly.
Code:
#include
/*
* Your warranty is now VOID !
*
* I am not responsible for bricked devices, dead SD cards,
* accidental data wipe or a thermonuclear war.
* If you have any concerns about steps included in this
* guide please do some research before trying it!
* YOU are choosing to make these modifications & if you
* point the finger at me for messing up , I will laugh at you.
*
* GOOD LUCK !
*/
PART I : UNLOCKING​
NOTE:
The warranty of all Non-European phones is lost permanently after UNLOCKING bootloader. LOCKING the bootloader again after UNLOCKING won't give your warranty back.
The warranty of all European phones is not lost after UNLOCKING bootloader. To claim warranty of an UNLOCKED European phone you will need to live in the European Union.
Requirements:
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
Unlock Bootloader Tutorial
Unlock Bootloader YouTube Video
Bootloader LOCKED, Status Code 0 : Bootloader was not UNLOCKED before by the user & is factory LOCKED, UNDER Warranty.
Bootloader UNLOCKED, Status Code 3 : Bootloader is UNLOCKED by the user, Warranty VOID.
Bootloader RELOCKED, Status Code 2 : Bootloader was UNLOCKED by the user & is LOCKED again by the user, Warranty VOID.
1. Users with LOCKED bootloaders will have to first UNLOCK their bootloader before proceeding, this will VOID your WARRANTY.
2. Users with UNLOCKED bootloader need not worry as this process will not wipe anything from the internal storage.
3. Users with RELOCKED bootloader will have to UNLOCK their bootloader again before proceeding, phone will be erased again after UNLOCKING.
4. After UNLOCKING the bootloader your phone's internal storage will be erased. Your installed apps, contacts, SMS, call logs, data like photos, music, videos in internal storage will be WIPED completely.
5. Use 'SuperBackup' App from Playstore & set the location of backup files to external sdcard.
6. Before proceeding make sure you backup everything & move your data from internal storage to external sdcard or PC.
PART II : ROOTING​
Requirements
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
TWRP v3.1.1-0 for titan
TWRP v3.1.1-0 for thea
SuperSU v2.82 Stable
A) Flashing TWRP
1. You need to unlock the bootloader before proceeding/
2. Install Motorola & Fastboot Drivers & restart your PC. Copy the SuperSU Zip inside your phone storage.
3. Go inside the installed adb fastboot folder. Hold "Shift" key & right click inside the folder & click on "Open CMD Window Here".
4. Copy the TWRP image file inside installed adb fastboot folder.
5. Switch off the phone, press & hold "Volume Down" & "Power" & release after 4-5 seconds.
6. Connect phone to PC . You will see "USB Connected" on the phone screen.
7. Type and press enter after each command
For titan (3G) : XT1063, XT1064, XT1068, XT1069
Code:
fastboot flash recovery twrp-3.1.1-0-titan.img
fastboot boot recovery twrp-3.1.1-0-titan.img
For thea (4G/LTE): XT1072, XT1077, XT1078, XT1079
Code:
fastboot flash recovery twrp-3.1.1-0-thea.img
fastboot boot recovery twrp-3.1.1-0-thea.img
7. Your phone will now boot into TWRP.
B) Backup Stock ROM (Optional)
1. Inside TWRP, select 'Backup', select 'System', 'Boot' & 'PDS' partitions & swipe to backup your Stock ROM.
C) Flashing SuperSU Zip
1. Select "Install" option, Select the location of SuperSU Zip & flash it, go back & select "Reboot", select "System".
2. Open the App Drawer & check for SuperSU app & then download 'Root Checker' app from Play store to check for root access.
PART III : RESTORING​
Requirements
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
Softbrick : Stock 5.0.2 Factory Firmware Image Installer
Hardbrick : Unbrick Moto G 2014 (2nd Gen)
1. You won't need to UNLOCK the bootloader to flash the firmware of your variant for your region. i.e. You can flash firmware on a LOCKED bootloader. However to flash a firmware for different region, your bootloader needs to be UNLOCKED. Check your Moto G 2nd Gen Model No & Regional Variant from here before proceeding. You will need it for downloading factory images for your corresponding phone.
2. If your device gets stuck in following situations it has soft bricked.
- Stuck on Motorola logo or "Unlocked Bootloader" screen.
- Stuck on boot animation or device restarts automatically (boot loop)
- Cannot boot into recovery mode.
- Can boot into fastboot mode only.
3. If your device gets stuck in following situations it has hard bricked.
- Cannot boot into fastboot mode.
- Cannot power on or cannot charge.
- Cannot boot into recovery mode.
Step By Step Troubleshooting Of Your Device
1. Check if it switches on or boots into fastboot menu, if it doesnt maybe the battery is depleted. Use a minimum 1A output charger & keep it plugged in overnight for atleast 10-12 hours. Repeat for 2-3 days. If it still doesnt power on, this means your phone is hardbricked & recovery may or may not be possible. Motherboard replacement might be needed. You will loose all your data & your IMEI number will be changed after your motherboard is replaced.
2. If it switches on & is stuck on Motorola logo/bootanimation or "Unlocked Bootloader" screen, hold power button till phone screen turns off. Your phone will restart, let it continue the booting process. If it still stuck, hold power button till phone screen turns off. After it turns off immediately press volume down while holding power button. Release both after 2-3 seconds. You will now boot into fastboot menu. This means your phone is softbricked & can be recovered by flashing correct factory image for your device. Flashing incorrect image or downgrading from a higher Android version to lower (Eg Marshmallow to Lollipop) may render your device permanently hard-bricked/dead.
PART IV : DOWNGRADING​
Requirements
Unlock Bootloader Here
Unlock Bootloader YouTube Video
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
5.0.2 Factory Firmware Image Installer
1. Boot into fastboot mode. Check your bootloader version from top 2nd line. It should say something like "48.86 (sha-5497-c9). 4886 is your bootloader version.
2. Marshmallow 6.0 to Lollipop 5.0.2 : If your bootloader version is 4886 (Marshmallow Bootloader), you need to make some changes in the easyinstaller.bat file inside the Stock Factory Firmware Image that you download or while flashing the ROM manually.
- Download Lollipop 5.0.2 Factory Firmware image zip from PART III RESTORING Section
- Unzip the contents & open easyinstaller.bat with notepad.
- Find the 2 lines "mfastboot.exe flash motoboot motoboot.img" & delete both of them.
- Delete the motoboot.img file inside the extracted contents.
- Run the easyinstaller.bat
- Do not type "mfastboot.exe flash motoboot motoboot.img" while flashing the Lollipop ROM manually
3. Lollipop 5.0.2 to Kitkat 4.4.4 : If your bootloader version is 4882/4883(Lollipop Bootloader), you need to make some changes while flashing the ROM manually.
- Download Kitkat 4.4.4 Factory Firmware image zip.
- Unzip the contents.
- Delete the motoboot.img file inside the extracted contents..
- Do not type "mfastboot.exe flash motoboot motoboot.img" while flashing the Kitkat 4.4.4 firmware image manually.
4. If you downgrade your bootloader version i.e flash a 4883 Lollipop bootloader on your existing 4886 Marshmallow bootloader, your phone will be hard-bricked / permanently dead. Therefore follow the instructions above carefully. I am not responsible for dead phones.
CREDITS
@Lucas Eugene for his thread 'Unlock Bootloader - Moto G (2nd Gen) [UPDATED]'
@Tomsgt for his YouTube video 'How to unlock the boot loader on your Motorola phone Moto X, G, & E all versions'.
@Chainfire for creating CF Auto Root & SuperSU.
@luca020400 for maintaining TWRP.
@reefuge for his thread '[STAGE FRIGHT][XT106x][5.0.2][LXB] Stock 5.0.2 Easy Installer via FastBoot Tool'​

Do I have to change anything if I have the bootloader already unlocked (especially to avoid the factory reset)?

Nagass said:
Do I have to change anything if I have the bootloader already unlocked (especially to avoid the factory reset)?
Click to expand...
Click to collapse
Just flash the latest SuperSU http://download.chainfire.eu/supersu with twrp. That's it.

Nagass said:
Do I have to change anything if I have the bootloader already unlocked (especially to avoid the factory reset)?
Click to expand...
Click to collapse
Please read the OP
Unlocked bootloader wont wipe anything after rooting.

Just remove install_recovory.sh from /system/etc/. when you bootep into twrp the first time
After flash supersu and reboot

It displays failure remote failure when I run bat.exe

Thank you so much, this tutorial is perfect. :good::good::good:
Now my girlfriend can enjoy her 5.0.2 rooted with twrp 2.4.8.0 installed.
Great

iamanubhav said:
It displays failure remote failure when I run bat.exe
Click to expand...
Click to collapse
https://forums.motorola.com/posts/132580d3df

thaaaaaaaaaaanks @luca020400
and I can delete the application motorola?

If I understood correctly, this method does not require unlock key from motorola to unlock bootloader. So, if I unlock the bootloader and restore the lock again later, then there won't be any way that motorola can get to know if it was unlocked ever (for warranty purpose )??

Thanks for this!
However, it results in the same issue I've found ANY time I've tried to install ANY version of SuperSU with ANY android version on this phone (1063). That is: after flashing supersu, I get a boot loop. The first few times this happened, I cursed and reformatted the entire phone. For anyone else who has encountered this, I just figured out a way around it! It looks like this problem *only* affects the recovery partition, which is easily re-flashed.
Here's what worked for me:
While boot looping, press and hold vol down + power until screen stays black for 5-10 seconds, then release. You'll get to fastboot mode here. Then, connect with a usb cable and in a cmd prompt, from within your adb directory, type fastboot flash recovery <recovery image name.img> and hit enter. Once it flashes sucessfully, you'll be able to start back up with "normal startup" from the device's fastboot menu and all should be well. And if you've done this to correct a boot loop brought on by this autoroot, you'll actually still have root once you start up. Hooray!
The recovery image that you flash can be TWRP (link above) or the stock android recovery (which I found on this forum somewhere, but will upload with a link as soon as Mega is nice to me again).
Hope this helps someone else.

himsin said:
If I understood correctly, this method does not require unlock key from motorola to unlock bootloader. So, if I unlock the bootloader and restore the lock again later, then there won't be any way that motorola can get to know if it was unlocked ever (for warranty purpose )??
Click to expand...
Click to collapse
You need to unlock it
These are the step after the unlock on lollipop roms

imp .questions
Hey thanks for this thread I have successfully rooted my phone
Q. And if Motorola pushes the 5.1 ota can I update my is to 5.1?I have just rooted and the recovery is also stock

luca020400 said:
You need to unlock it
These are the step after the unlock on lollipop roms
Click to expand...
Click to collapse
So, this method won't unlock the bootloader?? The very first warning in OP gave me the impression that it will also unlock the bootloader :silly:

himsin said:
So, this method won't unlock the bootloader?? The very first warning in OP gave me the impression that it will also unlock the bootloader :silly:
Click to expand...
Click to collapse
Yes , the tool unlock your bootloader
But anyway you need the motorola code and unlock process

luca020400 said:
Yes , the tool unlock your bootloader
But anyway you need the motorola code and unlock process
Click to expand...
Click to collapse
Now I am more confused.... If the tool unlocks the bootloader then shall I assume that it asks for the unlock code during process?

himsin said:
Now I am more confused.... If the tool unlocks the bootloader then shall I assume that it asks for the unlock code during process?
Click to expand...
Click to collapse
Yes it ask for unlock code

Didn't work for me on Linux
fastboot-linux binary included with auto-root seems to be not working.
I tried to use fastboot from ubuntu repositories, which works, but couldn't correctly boot auto-root image.
I used openrecovery-twrp-2.8.4.0-titan.img with "normal" procedure described here , and everything worked perfectly.
Thanks anyway!

luca020400 said:
Yes it ask for unlock code
Click to expand...
Click to collapse
Thanks for clearing the doubts

himsin said:
If I understood correctly, this method does not require unlock key from motorola to unlock bootloader. So, if I unlock the bootloader and restore the lock again later, then there won't be any way that motorola can get to know if it was unlocked ever (for warranty purpose )??
Click to expand...
Click to collapse
Yes they understand, since your STATUS number changes from 0 to 3.
When you relock it changes from 3 to 2.
So your warranty is lost forever. Be careful.
You can find this number on the display when you're on fastboot mode (turn off the device and then press power + volume down for aboout 5 sec and release)

[GUIDE] All-In-One noob friendly guide for xperia X (Root/Bootloader/Rom)

[UPDATE]: USE THIS ONLY FOR NOUGAT 7 OR 7.1! THERE IS A DIFFERENT GUIDE FOR ANDROID OREO!
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502 (Written by YasuHamed, not me!)
If you are not interested in android Oreo, or you want to go back to Nougat, this guide is still valid! [End of Update]
This is a guide for newbies or for people that are simply confused. If you have any questions, you can always ask me, and I will reply. but please make sure you haven't made mistakes and do not ask about things that are already stated here. Let's go!
BEFORE DOING ANYTHING, NOTES
-make sure you have installed ADB : https://forum.xda-developers.com/showthread.php?t=2588979
-make sure ADB can read your phone with the correct drivers installed. If you have trouble with that, read "DRIVERS" section
!It is absolutely necessary to install the drivers correctly!
-Backup your stuff if you have any, you will need to delete everything from the phone
-Enable USB debugging
-Note: some of these instructions apply to Windows OS only!
-Note: links to downloads have been shortcutted as much possible to make it easier for you!
-Find some stock roms here! https://forum.xda-developers.com/xperia-x/how-to/sonyx-f5121-downgrade-8-0-0-to-7-1-1-to-t3754986
(Credit: HEKER510)
-Warning: you will lose your warranty!
-I am not responsible for any damage done to your device.
BACKUP DRM KEYS (OR WORKAROUND)
You may want to unlock your bootloader. If you unlock it without backing up the DRM keys, you will lose them. I did that mistake and I regret it. If you already did, there is an alternative solution, skip to step 8.
1) If you are running android 7 nougat, you will need to downgrade to MM. If you are running MM, skip to step 7.
2) You will need to wipe everything before rolling back, so if you have any data back it up
3) Download any stock MM 6.0.1 firmware for the xperia X. You can find one here : https://mega.nz/#!1xRj2CYS Decryption key: !qBVi7yky8AL84eUF3bpTTGQ2YmN0ePCjc-eSDZGIZCI
Watch out: if you have the dual SIM model, F5122, you need to download accordingly!
For more firmwares, check "BEFORE DOING ANYTHING"
4) Download the latest flashtool: http://www.flashtool.net/downloads.php
Upon installation, tick on fastboot, flashmode drivers! If it didn't ask you, go to the installation folder and run Flashtool-drivers.exe. Please read "DRIVERS" section!
5) Flash the .tft file
How to flash?
0. Go to "C:\Users\[Your PC Name]\.flashTool\firmwares" , and put your firmware .ftf file in there!
1. Open Flashtool and click on the lightning bolt icon (first one from the left)
2. In the prompt, choose flashmode.
3. Under firmware, click on the version you put (It should probably only be one option)
4. Under wipe , tick everything. Under the others, do not make any changes.
5. Click "Flash"
6. When the popup appears, connect your device. It needs to be powered off, and connected while you are holding the
"volume down" button.
7. Wait for it to finish.
8. Done. Boot up the device, it might take some time to open so don't worry.
Click to expand...
Click to collapse
6)If your phone bootloops, try flashing again or a different firmware and make sure you followed the steps correctly.
7) Once your phone successfully boots android MM, use Dirtycow to get your DRM keys out: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
8) If you unlocked the bootloader before backing up your keys, you can use DRM kernel fix. You can get it here: https://forum.xda-developers.com/xperia-x/development/kernel-drm-fix-nougat-t3530849 Before using it check out the custom rom that includes this fix and other things.
UNLOCK BOOTLOADER
This is relatively easy and you can follow official sony instructions to do it.
1) Go to your phone settings, developer options, and enable OEM unlock
"But there is no developer options!" -Go to the bottom of your settings, system, about phone, and tap multile times on "Build Number", also at the bottom.
Click to expand...
Click to collapse
2) If you haven't already , install ADB fastboot and configure drivers (Link on top )
3) Follow the steps on the Sony website to get your unlock code: https://developer.sonymobile.com/unlockbootloader/email-verification/
4) After unlocking, a warning message on boot is normal!
INSTALL RECOVERY
Installing TWRP on your xperia X is very important, since you can flash zips and img files so easily, plus wipe, backup and other features.
1) Download the TWRP .img file: https://androidfilehost.com/?w=files&flid=197369 (Credit: eagleeyetom )
2) Make sure you have USB debugging enabled
3) Open your downloaded twrp folder
4) Run CMD in that folder (shift + right click inside the folder, Open CMD here )
5) Connect your Xperia X to your PC
6) Type these lines:
adb reboot bootloader
fastboot flash recovery recovery.img [where recovery.img is your twrp file name]
fastboot reboot
7) If no errors, twrp is now installed. Once your phone boots , turn it off,. To access TWRP recovery hold power button and volume down button until the TWRP menu appears.
STOCK ROM, ROOT
If you just want to root and not interested in additional features and tweaks, you can simply flash SU through TWRP to get your phone rooted.
Note: Current best stock ROM available: 7.1.1 (252) - better features than older ver, and good battery life.
0) Install your desired stock firmware using the exact same previous instructions, (under DRM section) with flashtool.
1) Download SuperSu
Or magisk, using YasuHamed guide mentioned on top, but I have not tested with anything other than Oreo 8.0
Use magisk if you want more stability / root features (like hide root from apps, modules )
2) copy it anywhere on your phone
3) Run TWRP
4) Tap on install
4) Flash the file
5) Reboot, you are now rooted
6) Insert your DRM keys if you have them
Custom ROMS
After unlocking the bootloader and installing TWRP this is the best way to go in order to get full root, tweaks.
https://forum.xda-developers.com/xperia-x/development/rom-xperia-x-pexorom-v1-0-0-f5122-f5121-t3590552
^ This is a very good custom ROM made by prmk74. You can see its features in his thread.
1) Download the rom and copy it to your phone
2) Run TWRP
note: It is recommended to wipe dalvik, cache, data ( your storage partition doesn't need to be wiped)
3) Tap install, find your downloaded file and execute
note: It is recommended to wipe dalvik, cache, data ( your storage partition doesn't need to be wiped)
4) Follow on-screen instructions, do not stop the booting after finishing the installation, it will take some time
5) Insert your DRM keys if you have them
6) For those who lost their keys: Now the functions like vivid image mode are working properly.
DRIVERS
For Windows 8/8.1/10 users, how to solve driver problems:
1) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers. Go to the flashtool install location and run the drivers.exe again, check fastboot and flashmode
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine
TO CONCLUDE:
This is what you may want to do to get the most out of your new xperia x:
1) Backup DRM
2) Unlock BL
3) Install TWRP
4) Flash Persian (or a different rom) through TWRP (And subscribe to the thread so you receive updates)
5) Restore DRM
Notes:
None of the links, tools are of my work, I'm just writing a guide for my fellow XX owners

^^ this guide is so really good :3. I post flash script for someone dont know how to find it ^^
unzip it in this position.
C:\Users\[user-name]\.flashTool\mydevices

max26292 said:
^^ this guide is so really good :3. I post flash script for someone dont know how to find it ^^
unzip it in this position.
C:\Users[user-name]\.flashTool\mydevices
Click to expand...
Click to collapse
Thanks!

Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.

brianx87 said:
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
Click to expand...
Click to collapse
These USB drivers are very annoying to work with. I got mine to finally work using a program called ADB driver installer. http://adbdriver.com/downloads/ Choose automated installation and try what I said. I believe it should fix your problem, after installing the drivers reboot and flash again.
Other than that, I have to ask are you 1000% sure you used the exact commands?
I saw another thread someone mistook
"flash recovery recovery.img" for "flash recovery.img"
"recovery" should be included before the recovery file name

brianx87 said:
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
Click to expand...
Click to collapse
Why didn't the sony guide work? It worked for me. Just so you know, the "device cant be trusted" message is appearing on everyones' phones after unlocking the bootloader, it's not a problem or something

the part of restoring DRM is skipped,
please xplain

YasuHamed said:
the part of restoring DRM is skipped,
please xplain
Click to expand...
Click to collapse
I know, as I said there is room for improvement. The reason I did not include it is because I never did it myself, so I don't want to write something wrong or something that could lead to problems. I write something only if I am 100% sure. If anyone of you is kind to offer that piece so the guide is complete I will be glad

FoxTheLegend said:
Why didn't the sony guide work? It worked for me. Just so you know, the "device cant be trusted" message is appearing on everyones' phones after unlocking the bootloader, it's not a problem or something
Click to expand...
Click to collapse
Ok I figured out what I did wrong and was able to amend another issue I edited out of this post.

brianx87 said:
Ok I figured outwhat I did wrong (able to boot into the os and warning message no longer an issue ) and the issue I am now facing is that twrp is hanging on the boot screen. Is this version of twrp built to a specific version of android?
Click to expand...
Click to collapse
What do you mean hanging? the twrp logo frozen?

FoxTheLegend said:
What do you mean hanging? the twrp logo frozen?
Click to expand...
Click to collapse
Working now, used a previous version of twrp by mistake. Using latest build works fine now, have to wait to get home from work to proceed with the rest, annoying procedures this stuff but your guide is great.

brianx87 said:
Working now, used a previous version of twrp by mistake. Using latest build works fine now, have to wait to get home from work to proceed with the rest, annoying procedures this stuff but your guide is great.
Click to expand...
Click to collapse
Thanks, Im glad to it works now

FoxTheLegend said:
I know, as I said there is room for improvement. The reason I did not include it is because I never did it myself, so I don't want to write something wrong or something that could lead to problems. I write something only if I am 100% sure. If anyone of you is kind to offer that piece so the guide is complete I will be glad
Click to expand...
Click to collapse
thank you for the answer sir
i am unable to find any twrp that work for my F5122, it always bricks and i have to reset.
is there any twrp recovery image that works correctly with f5122?

YasuHamed said:
thank you for the answer sir
i am unable to find any twrp that work for my F5122, it always bricks and i have to reset.
is there any twrp recovery image that works correctly with f5122?
Click to expand...
Click to collapse
Hmm.. Did you try the one from the poison thread? I myself have still the old version installed (not 3 or 3.1) if I find it on my pc I will share it with you

FoxTheLegend said:
Hmm.. Did you try the one from the poison thread? I myself have still the old version installed (not 3 or 3.1) if I find it on my pc I will share it with you
Click to expand...
Click to collapse
I have to modified kernel
all i want is to boot it via fastboot command
for example i have the rooted kernel SU installed (but battery drain is high) so i what wana do is flashing kernel with all securities OFF and then with twrp image i will do
Code:
fastboot boot twrp.img
i will boot the X in to twrp and i will flash SUPERSU via twrp.
thanks all

YasuHamed said:
I have to modified kernel
all i want is to boot it via fastboot command
for example i have the rooted kernel SU installed (but battery drain is high) so i what wana do is flashing kernel with all securities OFF and then with twrp image i will do
i will boot the X in to twrp and i will flash SUPERSU via twrp.
thanks all
Click to expand...
Click to collapse
I see, but don't you want to figure out why it's not working normally? Noone has reported a similar problem

FoxTheLegend said:
I see, but don't you want to figure out why it's not working normally? Noone has reported a similar problem
Click to expand...
Click to collapse
since there is no offcial twrp for X out yes and only DORA (XA) is available) even XA don't work for X
so either twrp 2.8, 3.0 or 3.1 any should just boot in order to let us flash superSU.

YasuHamed said:
since there is no offcial twrp for X out yes and only DORA (XA) is available) even XA don't work for X
so either twrp 2.8, 3.0 or 3.1 any should just boot in order to let us flash superSU.
Click to expand...
Click to collapse
=-= try to use this command fastboot flash recovery [your_recovery_name].img
I use f5122 and flash successfull twrp 3.0.2 and 3.1. with this, i flash some kernel and rom without any problem.

Everything is working good for me now, the only issue now is restoring the DRM keys, has anyone found a credible source for doing this on this device?
How can I be sure I have a full root? I can't seem to be able to uninstall some of the bloatware only disable it!

brianx87 said:
Everything is working good for me now, the only issue now is restoring the DRM keys, has anyone found a credible source for doing this on this device?
How can I be sure I have a full root? I can't seem to be able to uninstall some of the bloatware only disable it!
Click to expand...
Click to collapse
Well titanium backup can assure you but I don't see why you wouldn't have full root... You need an app uninstaller to uninstall bloatware, it can't be done through the settings you know that right

LG K20 plus, how to flash original rom

I have a LG K20 plus with t mobile as the carrier. I believe the model should be TP260. I mistakenly restored a twrp backup from a metro pcs phone that I got from this site coincidentally. Now my phone drops calls and data frequently and shows metro pcs on bootup vs tmobile. I have a kdz file but it won't flash because it now also thinks the model is MP260...not TP260 and says it's a mismatch. Any ideas on how I can get a restore for tmobile to try to reset the phone?

Just bumping

i could use a restore too. I installed super SU root and lost access to android pay. I wasnt to try that magisk root

I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay

colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
You were able to install TWRP after this process with the TP26010k_00_0316.kdz?
I am on TP26010E and don't want to upgrade to TP26010k if TWRP cannot be flashed as it has been stated here.

Yeah, you have to perform OEM unlock again, but I have been able to flash TWRP after flashing the previously attached .kdz with the LGUP tool

colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
Can I install this kdz from twrp and install supersu?

no, you have to use LGUP tool. This is a LG image that will flash everything including your recovery partition, and not a flashable ROM image.

You flash root through TWRP, you use LGUP for kdz as the user above said rom flashing and kdz flashing are two different things

See this post which reflects the new kdz available https://forum.xda-developers.com/showpost.php?p=73690098&postcount=3
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse

I flashed the modded ROM for MetroPCS, and couldn't flash kdz file because my phone was identified as MP260, instead of TP260.
I wiped the phone and re-locked the bootloader, and the phone would only boot into download mode, It gave a message about it being corrupted.
I took it back to TMO, and the sales people thought it was a virus, and replaced the device.
I've made a TWRP backup for anyone who runs into the same problem. This will fix your problem, so you can use the flash tools available for this device.
NOTE: I also provided Root tools and instructions for those Rooting for the first time.
1. Power off device, plug into computer, then hold volume up for download mode and let COM drivers install, you may need to change COM port to 41, through device manager.
2. In LGUP, choose upgrade or FOTA upgrade.
2. Once you flash firmware, you'll have to hit reset once or twice to get rid of the encryption failure notification.
3. Enjoy rooting your device again if you so choose.
ROOTING:
NOTE: Must have ADB & Fastboot setup already.
First you must unlock your bootloader.
1. In about phone settings, tap build number 6x to get developer settings, enable adb debugging and OEM unlock. Now plug into your computer.
2. Boot into Fastboot mode.
A. Open command prompt and type: adb reboot-bootloader.
B. Next type: fastboot oem unlock.
WARNING: You'll be prompted to factory reset device to protect your data. Your chance to turn back, if your brave then continue. Your device will factory reset, and you'll have to perform the first step again and you'll be ready to root.
1. To flash TWRP, plug into computer, then in command line navigate to where you have your recovery.img
A. adb reboot-bootloader
B. fastboot flash recovery recovery.img
2. Pull battery and manually boot into recovery,
A. volume+down as soon as you see LG, release then press again quickly and hold, follow the steps provided.
3. Hit cancel for the encryption notice, and swipe to modify system.
4. You must format device to get rid of encryption message, so choose format and it will ask you to type, yes.
5. Stay in recovery and flash the no-encryption.zip, and Magisk, if you choose to use it for your SU manager. Stay in recovery.
6. Reboot into recovery, and then set up your TWRP environment.
7. Enjoy Root:laugh:
NOTE: If you decide to root again, try using Magisk for SU management. Magisk's mods are excellent, and can run along side Xposed. If you choose Magisk, do not flash SuperUser.zip
TWRP STOCK BACKUP
https://mega.nz/#F!a59RBICD!kOisA-eOxviWK07Dn182FA
LG tools w/ Latest kdz
https://mega.nz/#F!b9sWDBwR!LjhrhZgYXB-BNHUWE11tJw
Sent from my K20 Plus using XDA Labs

Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks

Rican39 said:
Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks
Click to expand...
Click to collapse
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.

blas4me said:
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.
Click to expand...
Click to collapse
Thanks for reply.And info

does anyone have an mp 260 zip rom for twrp before boot?

5(/!p7 kiddie said:
does anyone have an mp 260 zip rom for twrp before boot?
Click to expand...
Click to collapse
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?

Pm me if this is what you need and I'll send you a link

I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.

lg k20 plus tmobil
lgup recognizes my model correctly as lg-tp260 on [com41] but it just sits there initializing for eternity. With my model highlighted I select it and I keep getting the error "LGUP cant load the model [C:\Program Files(x86)\LG Electronics\LGUP\model\com. I have installed lg air drive, lg bridge, lgup8994.dll, lgup for store. I desperately need to get this thing back to stock, I have the AICP rom installed but I dont like it. it was a mistake, if anyone can help I would appreciate it.

stovo06 said:
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?
Click to expand...
Click to collapse
Could you PM me this link to the Metro PCS stock backup, if you still have it?

Android 7.1.1 Doogee X5PRO

I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?

I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.

Do the camera and fingerprint work?

Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.

Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?

****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!

The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.

I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.

installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?

xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )

Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug​#b. Enable OEM unlock​
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:​type: adb reboot-bootloader ___ (Wait 1-3 second)​type: fastboot devices ___ (verify device is detected)​#b. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: yes​= unlocked: no​#c. unlock bootloader​type: fastboot oem unlock ___ and you get​-> start unlock flow​---> on screen appear:​vol UP=Yes; void warranty, clear ALL data​vol DWN=no; no unlock​Press Vol UP​#d. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: no​= unlocked: yes​#e. May be phone restart​
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt​as per normal way (You know this , after some trying...)​
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)​
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons​#b. choose recovery with Vol Up and confirm with Vol Down​
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.

Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo

xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.

when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file

I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file

xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?

The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.

I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...

As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?

[GUIDE] How to root, install TWRP, ROMs and mods on a G3s/G3 beat d722 in 2020?

*After I wrote this whole thing as a DM i figured it might be helpful for a couple of people that are struggeling to root and install a custom recovery on their d722.*
Before we start you will need a PC with internet connection and a USB cable.
If you get stuck or need something about the device you can find it here. It's an XDA thread about the d722, it's mods, roms... : https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
First you will need to flash your phone back to 4.4 kitkat firmware to ensure maximum compatibility (this is the only way my device would root) ( find it here: https://lg-firmwares.com/ (type in your model and download a 4.4 firmware closet to your region, language...)). We will do that with the lg flash tool (find it here: https://lgflash.com/download/) + also install lg drivers if you don't have them already (https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560).
1. First enable developer options in phone settings by tapping the build number 7 times. Go to the developer options and there tick usb debugging. Than you want to turn you device off. Hold volume up and plug it into you computer. You will get into download mode. On your PC extract and open the lg flash tool. There you will chose your kdz firmware file you downloaded previously and click normal fash. Choose other instead of korean and your preferred language. When you flash it the tool might report an error but just ignore it and wait for the phone to reach 100% download. It will reboot itself when finished. After that you can close the flash tool and continue to the next step.
2. Now you will root your phone. You will do that with lg one click root (found here: https://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951). Download the latest GUI version, install it onto your PC and open it. When your redy plug your phone into the computer (turned on no apps open) and click start. Wait for it to be done. It's normal for it to restart a few times.
3. Now we will instal the custom recovery to be able to flash ROMs. To do that you will need to dowbload this zip file from here and extract it with 7zip (https://forum.xda-developers.com/showpost.php?p=61220755&postcount=100) and install ADB (remeber install folder) (from here: https://forum.xda-developers.com/showthread.php?t=2588979). Paste aboot file into /sdcard folder (or folder of choice with adjusted path in command) ob your phone uding file manager. Than open CMD and type in
cd *path of your folder*
adb shell
su
dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you get an error that says there is no aboot file or something similar than you nees to change this command : dd if= *your phones path*/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot For me it was : dd if=/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4. This should have installed a basic version of TWRP on your phone ane booted into twrp recovery but we will be updating it.
To get into recovery from off state hold volume down + power button until you see the LG logo. Relese both for a split second and hold both down again (volume down + power) until you see an option to factory reset (wont actualy reset anything if you did all steps correctly). Click yes and yes again by using volume and power buttons and you will be booted to TWRP.
Alternative is to go to playstore and download root app that boots you to recovery if you do it often.
This version is quite old and not capable of flashing newer ROMs so we will be flashing an updated version (download it here: https://vasy.ru/TWRP/jagnm/ and rename it to .img if it isnt named like that alredy). Easiest way is to download it to your PC and transfer it via USB if your PC detects the phone while in TWRP. If not boot it up transfer the files and boot back to recovery. Now just flash the .img file and reboot.
5. At this point you have root privilages (super SU) and a custom recovery. Now all theres left to do is to flash ROMs and mods.
You boot to TWRP recovery, connect your phone to the PC and transfer the .zip files you want to flash. Tha you click flash in twrp chose your ROM files and click add more, your GAPPS click add more and the mod (if you want to try it of course). Than you flash them, wair for it to finish and click reboot.
If it takes longer than 15 min+ than you probaboy have a bootloop. To fix it take out the battery put it back in and boot into recovery (volume down + power until LG logo pops up, release for half a second hold again, yes and yes). Try factory reseting (type yes). And than just flash the ROM and boot. If it boots go back to recovery and flash GAPPS and mod and it should normaly boot into android.
If nothing fixes your issue you can alway use the firmware and lgflashtool to go back to default unrooted kitkat or lolipop.
My recomendations:
I personaly use this liniage (14.1) 7.1 ROM as it's still getting updates (I also tried 8.1 but it's buggy, laggy and gapps don't work):
https://forum.xda-developers.com/lg-g3/development/cyanogenmod-14-1-lg-g3s-t3508224
And of course you want google apps to go along with it:
https://opengapps.org/ (pick ARM, android version of ROM (7.1 in this case) and how many preinstalled apps (I use nano))
I also have this mod installed which makes colours of your display a bit better:
http://www.mediafire.com/download/6z9yg1d3gooyz37/Sony_Bravia_3.zip
From here you can also get Exposed framework, root apps like LSpeed to speed up your phone even more, greenfy and amplify to improve battery life. Again every mod for this phone along with overclocking and other mods is or was discussed here at one point so dont be afraid to join the conversation in this thread:
https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
And ofcourse google is your friend if you get into any issues. Hope this helps, typed it on my G3s .

Thanks
---------- Post added at 12:28 PM ---------- Previous post was at 11:44 AM ----------
It would be better for our phone to release an android 9 custom, it would be great. Here is the same phone as our processor and video accelerator. Android 9 would work great on our phone https://4pda.ru/forum/index.php?showtopic=633150&view=findpost&p=36961339

Thanks for the guide!
I bought a G3s D722 cheap off ebay to experiment with. I tried to flash four different kitkat roms many times on 2 computers and each time the phone went into boot loop (start tune and logo over and over) so I flashed the first UK Lollipop on the list and all went fine, there are not UK kitkat roms in the link.
The UK kitkat roms must be different is all I can determine anyone know where I can get one?
The preflash OS was V20e-EUR-XX and now its V20d
Any thoughts or suggestions anyone?
Thanks!

I couldn't get this to work so tried the very easy no PC method in the link and it works great!
LG G3/G3s/G3 Beat telekom,orange or any other operator
Hi everyone, I want to show u how to upgade your LG G3s/beat to adroid 7.1.1 lineage OS. It has taken me some time to find and to gather all needed files but i was succesfull :D So I had my lg running on android 5.1 Lollipop but I had problem...
forum.xda-developers.com