Database Users

Stuck on boot animation screen? [SOLVED]

I tried to root my NSTV and got as far as flashing the .zip file in TWRP but after I rebooted, it's now stuck in the boot animation screen with the dancing colored circles?
Any ideas please?
SOLUTION
First download Recovery OS Image from here: https://developer.nvidia.com/gameworksdownload
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
 These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD, connect your SHIELD
 via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
Fastboot menu navigation:
- Single tap on touch button for navigations between different menu.
- Hold down touch button for 4 second and release for selecting any menu
To flash this recovery image to your SHIELD, run the following commands from
 the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
 DTB file name to use for flashing for your product(see below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- It will take you to '!!! READ THE FOLLOWING !!!' page.
- Two selectable options are available. 'Confirm' and 'Back to menu'.
- Select 'Confirm' to unlock the bootloader.
Unlock may take upto 2 hours for pro device.
Get <DTB file name>
- For base sku use dtb file "tegra210-foster-e-p2530-0930-e02-00.dtb"
- For pro sku use dtb file "tegra210-foster-e-hdd-p2530-0932-e02-00.dtb"

old thread i know, but still very helpful!
after updating to 3.2 yesterday and then trying to root it again (lost after the update), i was stuck at the boot animation screen for-ev-ver!!
used this guide to fix and was successful, however there was one change that i had to make: after extracting the 3.1 recovery image....there was no "userdata.img" file. so in place of that file, i flashed the "vendor.img", which was in the extracted folder along with the other files i needed to flash.
in the end what worked for me was the following:
downloaded the 3.1 recovery OS image from the link provided in OP. extracted/unzipped the image file to a folder, then from that folder i flashed the following files in this order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash staging blob
fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
worked like a charm for me, booted up fine, ran updates and when it was done it asked if i wanted to update to version 3.2 ....i said yes and when that finished, i tried to root it once again. all went smoothly this time. not sure what went wrong the first time, but i am now on version 3.2, rooted, and did not even lose any data along the way!!
hardest part for me was getting into the bootloader (using HW method posted above). took me quite a few tries before i nailed it, lol
thanks for posting @Neo3D

Just tried to do it, but failed:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (22712 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.014s

I;m stuck,it won't except the tegra darcy or tegra foster. Help please i am sitting her stuck!

[GUIDE]Oneplus X MAC Root Guide

This guide will help mac users with rooting their Oneplus X
BEFORE STARTING!
This could void the warranty of your device.
I won’t be held responsible for anything that happens from doing this tutorial so please proceed at your own risk.
All your data will be erased, so please make a back-up!
Please enable usb debugging in developer options(tap 7 times on build number).
Connect your phone to your mac and you will see Oneplus Drivers in your finder.
Double click on AndroidFileTransfer(OSX).dmg
Drag Android File transfer to the programs folder.
Step 1: Setting up ADB and FASBOOT and unlocking the bootloader
- Power off your phone and hold power button+volume up
- The phone should enter fastboot mode
- Go to https://drive.google.com/drive/u/0/folders/0B-baud5R8XkwLWYxcHNmbGZTY1U
and download the 3 files.
- Go ahead and unzip fastboot.zip then copy over the recovery.img file into fastboot folder.
- Open Terminal
- In Terminal type the following with hitting enter at the end of each line:
cd downloads
cd fastboot
chmod 755 *
./fastboot-mac oem unlock
- Your phone will reboot and you will be asked to unlock the bootloader. Just hit the Power button and unplug
your phone
- Phone will reboot
- Setup your phone
- Copy the UPDATE-SuperSU-2.78.zip to the internal storage of your OnePlus X using Android File Transfer.
- Power off your phone and hold power button+volume up, you should enter fastboot.
- Re-connect the USB cable once in fastboot mode.
Step 2: Flashing custom recovery and rooting
- Open terminal
- In Terminal type the following with hitting enter at the end of each line:
./fastboot-mac flash recovery recovery.img
./fastboot-mac erase cache
- Wait for it to finish and unplug your phone
- Hold down power and volume down for 20 seconds.
- The phone should boot into recovery.
- Once in TWRP recovery, choose “Install”
- Choose the Super SU zip file you copied over to your phone earlier.
- Swipe to flash.
- Choose “Reboot System”.
- If twrp asks your to disable stock recovery, swipe to disable.
YOUR OPX WILL REBOOT AND IS NOW ROOTED!
To check, open to superSU app and check for errors, no errors=rooted!
Thanks to https://theunlockr.com/ for the windows tutorial.
Need help ? Post a comment and I will help. :good:
Noticed spelling mistakes? Please let me know

ᕕ( ಠ‿ಠ)ᕗ
Just hijacking this post here to say, way to go buddy !
jk, reserved

Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?

Hey, I've been trying the same thing. Didn't have your specific issue but I think it may be related to the fact that it's already unlocked.
That said, I to make everything work I basically used this guide + the commands from the official TWRP guide at the page "TWRP for OnePlus X" + the command from a guide in the official OnePlus guide called "[GUIDE] ONYX: How to Unlock Bootloader, Install Custom Recovery, Root, Take EFS Backup & More !!" --- sorry but I can't post links.
All in all the commands I've used where:
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot oem device-info
fastboot flash recovery twrp.img
fastboot boot twrp.img
brunolimaam said:
Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?
Click to expand...
Click to collapse

Asus zenfone 2(ZE551ml/ZE550ml)UNLOCK, UNBRICK, CUSTOM RECOVERY, FIX IMEI....and more

This document ALSO provides knowledge about android system work flow
The following Steps will help and resolve issues related with Zenfone 2 Series,
Do remember that most of the steps which are provided here are not automated, So have patience.
This guide will help you Recover Completely bricked mobiles - You are responsible for you own actions
We will try to do
1. adb and fastboot installtion
2. Unlock Bootloader
3. Custom Recovery Installation
4. Root Device
5. Unbrick (Asus Zenfone 2 ze551ml/ze550ml ONLY)
6. Recover lost IMEI's and Device Serial number( Of course the valid one Which is mentioned for your device ) (Asus Zenfone 2 ze551ml/ze550ml ONLY)
7. Recover serial number, mac, bluetooth address (Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________
*************************** 1. adb and fastboot installtion ********************************
____________________________________________________________________________________________​
used for Basic troubleshooting and updating android system
In windows just copy these four files into windows(c:/windows) folder or install it in windows folder
AdbWinApi.dll AdbWinUsbApi.dll adb.exe fastboot.exe
Download Link https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
For Linux refer distribution guide
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
********************************** 2. Unlock Bootloader ************************************
____________________________________________________________________________________________​If you are on Android L(5.x) Asus provide boot loader unlock tool you can download it from asus.com
Doing so will make your device warranty void. or you can use custom bootloader unlock
if you are on Android M(6.x) Asus doesn't provide any tool to unlock for Android MM
You should use custom bootloader unlock you can follow the procedure provided by the unlock tool
FAQ
Can we relock device ?
YES
Why we need to unlock bootloader ?
Bootloader is a program which will allow your device to load Android OS
Why Bootloader is locked ?
To protect the devices from unauthorized access to third party. More of Business tactics
How to
Download the file from https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!Ux9HlCzA zip file which corresponds to your Device
follow the instructions provided in the zip file
The successful of that unlocking process conclude that your device bootloader is unlocked, but its not ROOTed
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************************** 3. Custom Recovery Installation *******************************
____________________________________________________________________________________________​
There are majorly two custom recoveries used
* CWM - clock work MOD
* TWRP - Most flexible recovery mode ( more than just recovery)
you can download cwm from link (search google)
and TWRP from https://twrp.me/Devices/
once you downloaded the binary file from respected link provided
boot the device into fastboot mode
Follow Steps (only Asus Devices)
--------------------
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* fastboot devices - (in Computer prompt) wait till your device listed
* fastboot flash recovery filename(cwm.img or twrp.img) - it will take 20-50 Sec to complete
* press vol+ or Vol- until you see recovery mode on the screen and press power button
Once all the steps completed successfully you should be able to see the custom recovery screen
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
************************************ 4. Root Device ****************************************
____________________________________________________________________________________________​
Everyone who started using android device they all come across the word "ROOT" soon or later.
No wonder, whoever have root access to device can do wonders on android device. Root is nothing but having administrator privilege to make system wide changes, changes applied using root will applied without any question. no more, no less. whatever happens to device(system) you are your own, "SU" is nothing but "super user" and root is a super user which is from UNIX and Linux.
After unlocking android device bootloader, you need to patch su(binary file) command into android system which will allow you to run commands from adb shell prompt as root user.
There is no universal procedure to ROOT device, everything depends on the android device company, so based on manufacturing company you can google and get your device ROOTed
To root your Ze551ml/Ze550ml
Tools Required
---------------
Unlocked Bootloader Asus Zenfone 2(Ze551ml/Ze550ml)
SuperSU-2.78SR1-zf2_6.0.1.zip (Google search SuperSU-2.78SR1-zf2_6.0.1) download the zip file which has zf2 in filename or try https://www.yadi.sk/d/vVk0Qd-Ow7fdK
Custom Recovery (TWRP or CWM)
Steps to Root Device
---------------------
# copy SuperSU-2.78SR1-zf2_6.0.1.zip file into sdcard
# adb reboot recovery
OR
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* press vol+ or Vol- until you see recovery mode on the screen and press power button
# From TWRP main screen select install
# Browse and select SuperSU-2.78SR1-zf2_6.0.1.zip from sdcard
# select reboot
# adb shell
# su ( allow the permission from superSU app on mobile)
That concludes you are at root prompt (Device Rooted successfully)
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
*************************************** 5. UNBRICK *****************************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________​
Cause
----------------
Custom or Wrongly flashed ROMS
Most of the time unlock bootloader and ROOTing device leads to bricked mobile
Symptoms of bicked Device
------------------------------
1. Black Screen - You can sense vibrations only, from the device when you press power button but nothing on the screen(Unless screen hardware faulty)
2. Vibrations - Device keeps on vibrating at same interval of time (usually every 5-10 mins loop)
Tools required
-------------------
- Xfstk windows application (google search "xfstk-downloader_v1.7.0")
- Intel Soc windows driver (google search "iSocUSB-Driver_v1.2.0")
- xFSTK_ZE551ML-sal358-amtech.vn.zip do (google serach "xFSTK_ZE551ML-sal358-amtech.vn" download the zip file which contains 3 bin files)
- Asus user UL-Z00A-xx-x.xx.xx.xxx-user.zip you can download this zip file from asus website (https://www.asus.com/in/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/)
- partition.tbl (https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB)
some files are located at https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Remember the windows operating system will block some of the drivers from loading on windows 7, 8 or 10 just override that, install the driver first, Intel Soc windows driver after that install Xfstk windows application
How to Steps
--------------
* Open XFSTK Downloader, Click MRD tab A0 / B0 + A0 + CRC Tab, scanning shows Moorfield in device list.
* Click Options--> modify settings check Enable Override and change GP Flag overide value 0x800000807. Click OK.
* Change value of Device detection timeout to 120
* FW DNX should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* IFWI should point to ifwi.bin (browse and locate)
* OS DnX dont make any change to this field
* OS Image should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* Click Begin Download (Remember Once you see Scanning ....... device detected:1 which will be changing 0 to 1, couple of times wait till you see download sucessful before that mobile screen goes on and off let it continue for couple of minutes usually (2-5 mins) later you see 4 color strip on mobile screen and it enter into fastboot mode if you see that, your device is unbricked. if you dont see fastboot mode just turn off your mobile and try to enter into fastboot mode using volume up (press and hold) and power button(Press and hold release only power button when device vibrates)
* extract UL-Z00A-xx-x.xx.xx.xx-user.zip into a folder and copy partition.tbl into same folder open command prompt in that folder
* Run these commands one after another on every sucessful completion of command
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
* select Recovery mode using volume up or down key and press power button
* When you see android logo on the screen press and hold power button, press and release volume up key then release power button
* select sideload using voulme key and press power button
* on computer enter adb devices, should show connect device
* Run command adb sideload UL-Z00A-xx-x.xx.xx.xx-user.zip and enter, this command will take minimum 20-30mins to complete
if everything goes well your device is back to life, Congrats
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
******************** 6. Recover lost IMEI's and Device Serial number **************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
IT's ILLEGAL TO TAMPER IMEI RELATED INFORMATION AND IT IS PUNISHABLE OFFENCE
THIS IS JUST AN OVERVIEW AND
FOR KNOWLEDGE PURPOSE ONLY​____________________________________________________________________________________________​Its mobile user's NIGHTMARE when they see Wrong IMEI and serial number
Cause
---------------------------
Custom or Wrongly flashed ROMS
Symptoms of Wrong IMEI and Serial Number
-------------------------------------------
Unable to connect to network even though mobile boots properly and works normally
How to Check
---------------
When you run adb devices from your pc its shows device serial number
IMEI can be checked in Settings --> About --> Status --> IMEI information OR
Call Dialer enter *#*#4636#*#* and select Device Information
Tools required
-----------------
Digma_SoFia_IMEI_recovery.rar (Google search "Digma_SoFia_IMEI_recovery file contains contains Digma software and windows driver)
IntelAndroidDrvSetup1.10.0.exe (Google search "IntelAndroidDrvSetup1.10.0") IntelAndroidDrvSetup1.10.0.exe
Rooted Device
links
Digma - https://yadi.sk/d/30q9w4KJjvgHd
IntelAndroidDrvsetup - https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Steps :
* To identify the com port turn on your device and run command adb shell(from computer command prompt)
* Run su
* your device should be rooted so it will give su prompt(#)
* Run setenforce 0
* Run setprop system.at-proxy.mode 1
* Install IntelAndroidDrvsetup and intel mobil family imc1 driver which is included in Digma software ( This is the hard part to setup as windows driver installation restrictions and identifying com ports on usb interface make sure these software and driver installed properly)
* after successful installation of driver and Phonetool run Phonetool
* settings --> Phonetool check RTS and DTR on select your phone com port listed in port list click ok
* click on update info (Should say success connecting to port)
* Click modes --> security click on show advanced options
* Click unlock
* Click on personalization programming tab
* scroll down and click add button
* add your mobile phone imei number (only first 14 digits) again add one time if you mobile is dual sim phone
* Click Execute (will take upto 60 sec)
* if above all steps completed without any error, just reboot your phone and check your imei number should show your real imei numbers
Note some times you needs to flash imei number after setting setprop system.at-proxy.mode 3 to flash 2 imei number just try until both imei show correctly on you mobile check your imei number by dialing *#*#4636#*#*
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************** 7. Recover serial number, mac, Bluetooth address **************************
____________________________________________________________________________________________​
Refer https://forum.xda-developers.com/showpost.php?p=66877096&postcount=28 Thanks to BORETS24

Thanks, helped a lot.

Unsure of what happened to my phone
Hey, I was trying to root my zenfone 2 ZE551ml by following a youtube video. It asked me to first put superSu.zip inside the SD Card which I did. Next - unlock the bootloader of my phone by downloading an zip which has an unlocker.bat file. Then it asked me to flash TWRP recovery using fastboot which I also did and then to boot into twrp and install the supersu.zip. I did everything but the last step, as when i tried to boot into the recovery to use twrp, the phone restarted, came to the white asus screen, stayed there for a very long time and then went back into the bootloader.
At this point I got frustrated and thought of reinstalling everything. So I downloaded the zip file for the latest firmware, flashed recover, boot and droid boot and then when I restarted the phone to go into the recovery, the white asus screen just keeps on repeating itself. The device keeps on shutting down and then restarting but never goes past the white asus logo screen where it says "powered by android", doesn't even let me get into fastboot.
I am new to all this and any help from anyone is highly appreciated. Thanks

error loading partition.tbl? edit: now im stuck on "cannot load fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin "

after doing these steps
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
when i reboot and select recovery i cant load recovery , it opens bootloader
how to install recovery

Hi, good day.
I am having 0 response when I hit this command. setprop system.at-proxy.mode (number) Do you know why ?
Device is rooted, since I've unlocked the bootloader using the ASUS app.

Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)

I'm on step, Run setenforce 0, but it returns an error message, "Couldn't set enforcing status to '0': Permission denied". Please advise. Thank you in advance!

[GUIDE] [ROOT] LG K7 MS330 - Concise tutorial on rooting with: ADB, TWRP and SuperSU

***MOD EDIT: BE WARNED THAT WHEN PERFORMING THESE INSTRUCTIONS, THAT ALL DATA WILL BE WIPED (FACTORY RESET) FROM THE DEVICE - THIS INCLUDES THE INTERNAL DEVICE STORAGE (INTERNAL SDCARD). YOUR EXTERNAL SD FILES, HOWEVER, ARE SAFE AND WILL NOT BE MODIFIED.***​
Hello.
I will attempt to keep this tutorial as concise as humanly possible, without the expenditure of costly applicably valid information. There are many other persons (whom I do not know) to thank for the majority of this information (from XDA Developers and other sites around the world wide web). Without further adieu: Let's begin!
The base operating system that this tutorial references is a Windows distro (I am operating on: Windows 10 Home OEM).
Target phone specs (http://www.lg.com/us/cell-phones/lg-MS330-White-k7):
Carrier: MetroPCS®[*]
[*]Make: LG K7 ("HW" or "White")
[*]Model: LG MS330
[*]Build number: LMY47V
[*]Software version: MS33010m
[*]Android version: 5.1.1
[*]Android security patch level: 2017-04-01
[*]Kernel version: 3.10.49​
Prerequisites:
A USB cable (able to transfer data)
A functional copy of Windows
An internet connection (to download the software tools)
If you opt to not download and install the stock firmware ROM (*.kdz) and LG UP (used for many things):
You are taking a great risk in the event something catastrophic occurs (no backup; Corrupted partition(s); Broken hard-key reset; etc).
The LG UP tool combined with the ROM file enables you to fully slate the drive on the phone (effectively restoring it to a manufacturers state; No partitions, no data, nothing!).
It also acts as a major fail-safe as previously iterated.
You can also (if you take the time of day) use it to create your own customized 'factory style' bloatware free, customized filled state *.KDZ ROM! Although TWRP backups should be capable of emulating this type of behavior.
The ROM is ~1GB in file size from the server (capped at ~10MB/s download rate at the time of the writing of this post). Translation: It takes a while (~30min) to download. Fortunately for me: I had it and had to use it earlier today (TWRP backup failed).
Software tools (ADB, TWRP, SuperSU, LG UP, ROM):
ADB (Android Debug Bridge): https://developer.android.com/studio/releases/platform-tools.html
TWRP (Team Win Recovery Project) v3.2.1.0: https://twrp.me/lg/lgk7.html
SuperSU (SuperUser) v2.82: http://www.supersu.com/download
LG UP Lab v1.10: https://www.mylgphones.com/download-lg-up-software
Stock ROM (MS33010i -- *.kdz): https://mega.nz/#F!sdwRDLbZ!yPOiRPv5QJS_9I4hzL4ptQ!ddJHSBhR
This will be a step-by-step process; If you skip a step: Make sure you have a good reason!
I will be assuming you have followed the links above and both downloaded and installed the appropriate software (ADB, LG UP). Keeping everything organized is key.
For instance: Create a folder on your main drive ("C" drive is common traditionally). Name this folder "Rooty." Create a short-cut of "adb.exe" and place it there. Place the SuperSU *.zip and *.kdz ROM data files in the same directory as well.
Overview of procedures:
Enable "OEM unlock"
Enable "USB debugging"
Unlock OEM bootloader
Install ("flash") TWRP
Using LG UP (after TWRP is either installed or live loaded)
Install SuperSU
Step 1) Enable developer options
Enabling developer options -- Navigate to "Settings," then to "About phone," then to "Software info," then tap on "Build number" until the dialog states: "No need, you are already a developer."
Step 1.1) Enable OEM unlock option
Traverse two levels up; Tick off "Enable OEM unlock"; Scroll down 2 options and tick off "USB debugging."
Step 2) Unlocking the OEM bootloader
Insert your USB cable to connect your desktop/laptop to your cellphone; When the dialog comes up asking for permission to debug: Accept it (OPTIONAL: Tick off the 'always allow this device'). Ensure "Media device (MTP)" option is selected (it will automatically install the drivers from your phone to your computer if enabled).
Step 2.1) Unlocking the OEM bootloader (for the not-so-technically-inclined)
Create a textfile and name it whatever you'd like (I prefer the filename: "OEM_Unlock.bat").
Copy and paste this script and simply place it in the same directory ('folder') as ADB.
Code:
REM This will reboot the phone into "bootloader" mode
adb reboot bootloader
REM This will unlock the OEM bootloader (a message will display on the starting logo afterwards)
fastboot oem unlock
REM This is just to verify that it was successfully unlocked ("unlocked: yes")
fastboot getvar unlocked
Alternatively: You can manually input the commands one at a time by typing them yourself or copying and pasting.
Step 3) Installing TWRP
You can just use ADB to directly flash the recovery partition of the ROM on the phone:
Code:
fastboot erase recovery
fastboot flash recovery C:/Android/recovery.img
You can also simply 'live boot' into TWRP (less risk of a faulty TWRP):
Code:
fastboot boot C:/Android/recovery.img
Now TWRP is installed (unless you simply loaded the image file into the phone's RAM).
Using LG UP to flash the ROM ("WIPE" every partition of the phone with TWRP; EVERYTHING will be lost:
To use LG UP: You only need to power down the phone fully (ensure it is not yet connected to the computer).
Hold the "VOLUME UP" key (do not release); Insert the USB cable. The phone should (within moments) place itself into "DOWNLOAD MODE." At which point LG UP will recognize the phone. There will be two options: "Refurbished" and "Upgrade"; Tick off 'upgrade' every time! Below that is "3 dots" which enables you to navigate (GUI) to the directory of your desired *.tot or *.kdz file. Simply hit "start" and it'll flash the phone (it usually takes ~300s or ~5m).
Step 4) Installing SuperSU
Through TWRP: Click on "Advanced"; Then click on "ADB Sideload"; Tick both the "Wipe Dalvik cache" and "Wipe cache" (these will force all APKs to be reinstalled via root level). Then slide the bar across. Return your attention to Windows.
You can just use ADB to directly sideload SuperSu onto the phone.
Code:
adb sideload C:/Android/SuperSU.zip
The final page asks if you would like to install the "official TWRP app" and also if you'd like to install it under "system" privileges (one less than root).
The end! You now have root accessible privileges through the "SuperSu" application (which contains root privilege at this point).
Alternatively to manually inputing everything by hand into ADB: I've whipped up this simple batch script for Windows:
Code:
ECHO OFF
CD\
CLS
ECHO Waiting for the device to communicate (ensure you are not in 'recovery,' 'sideload,' or 'bootloader' state)
adb wait-for-device
REM Reboots to the bootloader
adb reboot bootloader
REM Unlocks the OEM bootloader
fastboot oem unlock
REM Quick check to see if it successfully unlocked
fastboot getvar unlocked
REM Flashes (deleting the stock ROM recovery program)
fastboot erase recovery
REM Flashes (copies the TWRP custom recovery program)
fastboot flash recovery C:/Android/recovery.img
REM Loads the TWRP custom recovery program into memory (a "live boot")
fastboot boot C:/Android/recovery.img
REM Pauses execution until the phone boots into "recovery" state
ECHO Wait until the phone enters a "recovery" state...
adb wait-for-recovery
CLS
ECHO Traverse to "Advanced" then to "ADB Sideload"
ECHO Check off clearing both the Dalvik cache and cache
ECHO Press any key *after* you swipe the bar across
ECHO(
PAUSE
REM Copies over the APK to the ROM (security exploit to gain root permissions)
adb sideload C:/Android/SuperSU.zip
adb reboot
How to use the batch script file to root your phone with ADB, TWRP and SuperSU:
Place: SuperSU.zip and TWRP.img in the same directory as the ABD/fastboot executables
Modify the absolute paths and file names to your system (EG: "C:/Android/" and "recovery.img")
I hate to post this, but I feel it to be utterly important to express my deepest gratitude to all those who have posted this information that was scattered about the internet. This is my first Android or PHONE for that matter to root! It was quite the under-taking (nearly a 48 hour scourge of research). I've learned quite a bit how the Android OS works internally as a result; as well as the tool-kits that are commonly used in conjunction with modding the Android (out of the scope of this thread).
I hope this very recently updated and compiled information will help ease the suffering of another's entrance into the world of rooting Android phones. I also hope it really deepens the understanding of what they're doing (EG: The commands being utilized with abd and fastboot).
Here is a helpful link in regards to adb/fastboot:
- Quick reference to abd commands (syntax and meaning): https://developer.android.com/studio/command-line/adb.html
- Alternatively: You can use "adb help" to see a print-out of the commands and arguments (same applies to fastboot).
Happy rooting, y'all!

Thanks for the write-up!
The attached SuperSU.zip worked perfect to gain root on my K7 m1 using the adb sideload in Twrp and PC.
My bootloader I had already unlocked. Twrp, I flashed before I accomplished that feat!
Was rooted with Kingroot but wasn't satisfied with that.
Factory reset, and followed your adb sideload instructions to gain root with SuperSU.zip ..
Thanks again my friend.
Custom Roms for the K7 seem to be scarce, unless I am looking in all the wrong places.
Would be much appreciated if anyone could help me on that front?? ... Please let me know.

Good Day
With very insignificant changes to syntax used above I found this works perfectly on OSX as well.
Thanks

hi, i cant seem to unlock the bootloader. i have already enabled oem unlock and usb debuggin from settings but it always fails
Code:
PS C:\adb> adb devices
List of devices attached
ZSTSS8DUSWZD9LCE unauthorized
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
ZSTSS8DUSWZD9LCE fastboot
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.294s
I should note that kingrot also failed to root
i dont know whats wrong, imma gonna try factory reset and try again
UPDATE
It seems the allow oem unlock option got disabled by itself somehow, i re enabled, tried again and unlocked succesfully
UPDATE 2
Aaaaand Bootloop, dunno what went wrong, iv'e reached step 4, flashed twrp, then tried to reboot into twrp and now im stuck in bootloop
Code:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 8.981s]
finished. total time: 8.983s
PS C:\adb> fastboot getvar unlocked
unlocked: yes
finished. total time: 0.003s
PS C:\adb> fastbot erase recovery
fastbot : The term 'fastbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastbot erase recovery
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastbot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\adb> fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.004s
PS C:\adb> fastboot flash recovery c:/adb/lg.img
target reported max download size of 134217728 bytes
sending 'recovery' (12010 KB)...
OKAY [ 0.394s]
writing 'recovery'...
OKAY [ 0.706s]
finished. total time: 1.103s
PS C:\adb> adb reboot recovery
error: device '(null)' not found

return from lineage os to oxygen. problem with twrp installation

hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!

sun-k said:
hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!
Click to expand...
Click to collapse
Hello,
let me see if i can help,
but i need some info....
Which the LineageOS version
your device currently running ?
Is your 6T a global or T-Mobile version ?

hi, thanks for the reply. it is a secondary phone and has an old lineage version. yesterday with a different PC than usual I managed to install the latest version of twrp from cmd after solving a partition problem. i installed twrp only theoretically since after reboot the lineage prompt doesn't start and the boot stops at the screen with fastboot written... by forcibly turning it off I can access the bootloader. this is the current situation. 6t golobal...

developments ... from what I wrote above I could not get any progress. the device goes into bootloader mode manually but from the windows prompt it is not detected by the adb device command or by fastboot device .. so I can't advance ...

Going back to stock version does not necessarily
imply the use of a custom recovery,
you just need to use the MSM/rollback tool.
You can download it from THIS thread.
Use the earlier version of the tool as
you don't know wich exactly the
version of android installed in your device,
9.0.16 suggested.
When you will have a running device,
manually download and install OOS 9.0.17 firmware,
which will let your device to upgrade to android 10 and so on...
READ carefully @iaTa THREAD to follow exact MSM procedure.
Use a Windows pc and be sure
you have installed Oneplus driver.
Feel free to ask.