Blu R1 HD Unlock bootloader, install TWRP, and root (Non prime) - BLU R1 HD Guides, News, & Discussion

Note: This guide if for the non Prime variant of the Blu R1 HD running android 6.0. It will also factory reset your device
Before you start: make sure usb debugging is enabled by going to settings-about phone scroll down to build number and tap it until it says you are a developer. Then just go into developer settings, find usb debugging, and click enable.
1: go to http://bit.ly/2rYeWVh on your phone and download the zip
2: The first thing you will need to do is install Adb and fastboot on your computer from here: https://forum.xda-developers.com/showthread.php?t=2588979
3: Once you have it installed, find the folder it installed into (usually either in c:/adb or in your downloads), and double click the Runme.bat
4: Once you're in the shell, run
Code:
adb reboot bootloader
this should boot your phone into its bootloader
5: Wait until your phone is in the bootloader (it should say something like "fastboot..."), and then run
Code:
fastboot oem unlock
This will unlock the bootloader and reset the phone. The process may take a few minutes to complete
6: Now that your bootloader is unlocked, you will need to install TWRP custom recovery. Since there isn't an official build for the BLU R1 HD, we will use a custom one. download from bit.ly/2BBJ8rp (original link was long) then place the recovery.img into your adb folder
7: then flash the recovery with
Code:
fastboot flash recovery recovery.img
replace recovery.img with the name of the file if it is something different this should take about a minute to install.
8: once you have TWRP installed you can root. In the TWRP menu click install, then select the SupeSU zip you downloaded previously. Once that has installed you should be rooted
Please post questions below!

lil chickenz said:
Note: This guide if for the non Prime variant of the Blu R1 HD running android 6.0. It will also factory reset your device
Before you start: make sure usb debugging is enabled by going to settings-about phone scroll down to build number and tap it until it says you are a developer. Then just go into developer settings, find usb debugging, and click enable.
Also need to turn on "enable oem unlock" option in developer options
1: go to http://bit.ly/2rYeWVh on your phone and download the zip
A label for random downloads is advised
2: The first thing you will need to do is install Adb and fastboot on your computer from here: https://forum.xda-developers.com/showthread.php?t=2588979
3: Once you have it installed, find the folder it installed into (usually either in c:/adb or in your downloads), and double click the Runme.bat
4: Once you're in the shell, run
Code:
Adb reboot bootloader
this should boot your phone into its bootloader
Needs to be lowercase "adb"
5: Wait until your phone is in the bootloader (it should say something like "fastboot..."), and then run
Code:
fastboot OEM unlock
This will unlock the bootloader and reset the phone. The process may take a few minutes to complete
Needs to be lowercase "oem"
6: Now that your bootloader is unlocked, you will need to install TWRP custom recovery. Since there isn't an official build for the BLU R1 HD, we will use a custom one. download from bit.ly/2BBJ8rp (original link was long) then place the recovery.img into your adb folder
7: then flash the recovery with
Code:
fastboot flash recovery recovery.img
replace recovery.img with the name of the file if it is something different this should take about a minute to install.
8: once you have TWRP installed you can root. In the TWRP menu click install, then select the SupeSU zip you downloaded previously. Once that has installed you should be rooted
Please post questions below!
Click to expand...
Click to collapse
.
.
Your directions are incorrect and incomplete.
And not working for devices updated with OTA , because blue made changes to block the bootloader unlock option
And there are already multiple posts with this topic that are complete.

IDK that's just what I did for mine and none of the other tutorials we're were right for me so I wanted to share it if anyone else had the same problem. I bought my phone like three months ago though so the os should be recent. Any info I should share?
Also I could add the link text cuz I haven't posted enough

lil chickenz said:
IDK that's just what I did for mine and none of the other tutorials we're were right for me so I wanted to share it if anyone else had the same problem. I bought my phone like three months ago though so the os should be recent. Any info I should share?
Also I could add the link text cuz I haven't posted enough
Click to expand...
Click to collapse
I was little harsh with first response. sorry
your steps were incorrect just in the"case" used.
Interested in your custom build number. It is displayed on the "about phone" section of setiings.
And you were able to unlock without changing the "allow oem unlock" setting is curious.
did you get phone refurbished or used?

mrmazak said:
I was little harsh with first response. sorry
your steps were incorrect just in the"case" used.
Interested in your custom build number. It is displayed on the "about phone" section of setiings.
And you were able to unlock without changing the "allow oem unlock" setting is curious.
did you get phone refurbished or used?
Click to expand...
Click to collapse
Its fine
Build number: BLU_R0011UU_V21_GENERIC
build number date: 05-05-2017
Phone purchased at amazon.com/BLU-R1-Cell-Phone-16GB/dp/B01H2E0KVA/ref=sr_1_3?s=wireless&ie=UTF8&qid=1512256238&sr=1-3&keywords=blu+r1+hd
It was new
I might have actually turned on oem unlocking some time in the past because I remember seeing the option, but when I was actually trying to root the phone and unlock it the option wasn't actually there. I had also factory reset the phone recently before the root and unlock so that shouldn't have mattered anyway. But yah, I was like, theres no option to enable that, Ill just try it without and it worked. And it did. The odd thing is though when I go to settings and search oem the option for oem unlocking comes up for developer settings, but when I click it there is nothing there. (Hopefully that makes sense)

lil chickenz said:
Its fine
Build number: BLU_R0011UU_V21_GENERIC
build number date: 05-05-2017
Phone purchased at amazon.com/BLU-R1-Cell-Phone-16GB/dp/B01H2E0KVA/ref=sr_1_3?s=wireless&ie=UTF8&qid=1512256238&sr=1-3&keywords=blu+r1+hd
It was new
I might have actually turned on oem unlocking some time in the past because I remember seeing the option, but when I was actually trying to root the phone and unlock it the option wasn't actually there. I had also factory reset the phone recently before the root and unlock so that shouldn't have mattered anyway. But yah, I was like, theres no option to enable that, Ill just try it without and it worked. And it did. The odd thing is though when I go to settings and search oem the option for oem unlocking comes up for developer settings, but when I click it there is nothing there. (Hopefully that makes sense)
Click to expand...
Click to collapse
To get around this just find the previous version stock rom from the blu dev site and flash it first. I have never seen a OEM unlock menu blanked out if that is what you're trying to say, in this case amazon and blu teamed up and you should be able to restore to original version without the OTA.

Related

[Q][Solved] Where should I begin as a beginner?

Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.
One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.
Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page
ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...
Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.
Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.
So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!

[GUIDE] How to unlock your bootloader, install TWRP and gain root access

There doesn't seem to be a comprehensive guide on this, so I thought I would provide one.
READ THIS FIRST
DO NOT TAKE ANY OTA UPDATES!!!
Please consider the following:
Ask yourself these two questions: "Why do I want to unlock my bootloader? Why do I need root access?" If the answer to either one of those is "I don't know," don't do it. Both of these actions weaken the security of your phone, and there's no reason to do that if you're not sure why.
This guide is for the Droid Turbo, model XT1254. It is not for the Droid Turbo 2, and it is not for any phone that is not named Droid Turbo.
Standard XDA rules apply. I'm not responsible for anything you do, and neither is anyone else other than you.
I'm assuming that you are running a Windows PC. If you have a Mac, I can't help you. If you're running Linux, you shouldn't need help.
This method is not free. It costs $25 (USD). If that's not okay with you, don't do this.
Once your bootloader is unlocked, you CANNOT safely re-lock and unlock it again. See this thread for what happens when you try to do that: http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081#post65095391
Still here? Cool.
Section 0: Installing Firmware Version MCG24.251-5
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you need to take an extra step to unlock your bootloader. I'll explain later. For now, just skip to section 1 of this guide. If it says anything else, keep reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows).
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data.
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
For now, just try to ask someone nicely to help you out with this. I'll try to get this done before the end of the day.
Section 1: Unlocking the Bootloader
1. Download Sunshine from here: http://theroot.ninja/download.html
2. Move the apk file to a convenient location on your phone. If you downloaded it with your phone, it's in your downloads folder already, so leave it there.
3. Use any file browser on your phone to navigate to the folder that contains the Sunshine apk file. Tap on it to install it.
4. If a message comes up and says that you need to enable installation of apps from unknown sources, follow the instructions on that message to enable it.
5. Enable Wi-Fi on your phone if it is disabled. Even if you aren't connected to a Wi-Fi network, it still needs to be on.
6. !!!DO THIS STEP ONLY IF YOU'RE ON MCG24.251-5-5!!! Follow the instructions here to obtain temporary root: https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/. DO NOT perform the uninstall step.
7. Open your app drawer and start Sunshine.
8. Follow the instructions.
9. !!!FOR MCG24.251-5-5 ONLY!!! Sunshine will reboot your phone automatically, and it will go into a bootloop. This is normal. Don't panic. Hold down the volume down button until the phone goes into bootloader mode. Plug your phone into the computer, start Minimal ADB and Fastboot (see Section 0 for link if you didn't have to install it before this point), and enter the command fastboot oem config fsg-id "". This will disable the temporary root exploit. Reboot your phone normally, and everything should be happy again.
10. If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader. If you do not see this message, open Sunshine again and follow the directions again. If you're on MCG24.251-5-5, you'll have to gain and uninstall temproot again at the appropriate times.
Section 2: Installing TWRP
Team Win Recovery Project is arguably the most important tool to have on a bootloader-unlocked phone. This is how you install it:
1. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790. If you already did this in section 0, you don't have to do it again.
2. Download the latest TWRP .img file from here: https://www.androidfilehost.com/?w=files&flid=39562
NOTE: The TWRP file that you download should have a .img extension. Make sure you can see this. If you don't see .img at the end of the filename, Google how to make file extensions visible on your version of Windows and do it. If you do not do this, you may run into trouble later.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. If you already did this in section 0, you don't have to do it again.
3. Rename the file that you downloaded in step 2 to TWRP.img
4. Copy TWRP.img to the directory that you installed Minimal ADB and Fastboot to. The default location on an installation of 64-bit Windows is C:\Program Files (x86)\Minimal ADB and Fastboot.
5. Turn off your phone.
6. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Poor little guy...
7. Plug your phone into your PC.
8. Double click on the Minimal ADB and Fastboot shortcut that's on your desktop. It will open a command prompt.
9. Type "fastboot devices" without quotes and press enter. If it gives you your phone's serial number, you're good to go. If it gives you nothing, your device is not detected. This can happen for several reasons, and I won't discuss them here. However, if you followed these directions and all of your hardware is functioning properly, you should be good to go.
10. Type "fastboot flash recovery TWRP.img" without quotes and press enter. It should tell you that the flash was successful. You might see some "not found" errors. These are normal and can be ignored.
11. Highlight "Recovery mode" on your phone using the volume up and down buttons.
12. Press the power button to boot into TWRP.
13. TWRP will boot, and it will ask you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
14. Select Reboot, followed by System to boot the phone normally.
Section 3: Gaining Root Access
If you intend to install a custom rom, these steps are not necessary. Custom roms almost always come with root access built in. Refer to the thread of your custom rom of choice for installation instructions.
If you do not want a custom rom, and you simply want root access on the stock Droid Turbo rom, continue reading.
1. If you are on the stock marshmallow rom, build MCG24.251-5 or higher, download the latest version of both Magisk and Magisk Manager to your phone: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
NOTE: You need to be on marshmallow to use Magisk to root your phone. The Magisk thread says it supports lollipop and higher, but it only supports lollipop for some stock Samsung roms. This does not apply to you. If you want to root your phone on lollipop, you'll need to use SuperSU. I won't go into that here because I don't think there is a lot of demand for it, but if you need help with that, reach out to someone here. It's not difficult.
2. Install Magisk Manager the same way you installed Sunshine.
3. Turn off your phone.
4. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Andy, what have they done to you?
5. Use the volume up and down buttons to highlight "Recovery mode."
6. Press the power button to select Recovery mode.
7. Select Install from the TWRP main menu.
8. Select the most recent version of Magisk (the .zip file, NOT the Magisk Manager .apk file) that you downloaded.
9. Swipe the bar at the bottom of the screen to flash this zip file.
10. When it finishes, select Wipe Cache/Dalvik and swipe the bar at the bottom of the screen.
11. Select Reboot System
Section 4: Passing Safetynet using Stock, Unrooted Marshmallow
If you are running stock marshmallow with an unlocked bootloader, you will fail safetynet verification (and be unable to use Android Pay). Installing Magisk is the only recommended method, as of this writing, to bypass this limitation. If you completed Section 3, you shouldn't have any trouble. Understand, however, that there is a constant game of cat and mouse going on between Google and Magisk's developer, so sometimes Google will update safetynet to beat Magisk. If that happens, wait for Magisk Manager to tell you that a new version of Magisk is available, and it will install the new version for you. That's your best bet for passing safetynet again.
If you really want to pass safetynet, but you really don't want to be rooted, you can disable root (Superuser access) in the Magisk Manager settings.
Section 5: Miscellaneous
Here are some links to stuff you can flash now that your bootloader is unlocked:
Official LineageOS 12.1 (Android 5.1.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3260253
Official LineageOS 13.0 (Android 6.0.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3353298
AOSPExtended (Android 7.X): https://forum.xda-developers.com/moto-maxx/general/rom-aospextended-rom-v3-1-t3555361
Unofficial LineageOS 14.1 (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-t3494646
crDroid (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-crdroid-android-t3491257
Android Open Kang Project (Android 7.X): http://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Resurrection Remix (a great LineageOS-based rom, Android 5.1.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-5-5-5-t3197643
Resurrection Remix (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232
Resurrection Remix (Android 7.X): https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109
Computerfreek274's optimized stock rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
MoKee Open Source Project (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-mokee-opensource-project-t3188936
Bliss Rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-bliss-rom-6-4-team-bliss-t3422937
Android Open Kang Project (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-android-kang-project-t3422456
Android Open Kang Project (Android 7.X): https://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Change the splash screen (the bootloader unlocked warning message) that you see when you first start your phone: http://forum.xda-developers.com/dro...custom-boot-logos-accepting-requests-t3262873
Xposed framework and installer (make sure to use the sdk22-arm version if you're running a lollipop rom, sdk23-arm if you're running marshmallow. Not available for nougat yet.): http://forum.xda-developers.com/showthread.php?t=3034811
Alternative Material Design Xposed Installer that provides additional features: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Pon-3 Audio Mod (modified and improved Viper4Android. It makes your phone sound better.): http://forum.xda-developers.com/showthread.php?t=2530976
Other modded Viper4Android versions that are better than PON-3: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Theme your TWRP with different colors: http://forum.xda-developers.com/android/themes/theme-twrp-3-0-0-0-dark-stock-colors-t3310235
More TWRP themes: http://forum.xda-developers.com/showpost.php?p=66276401&postcount=2889
Android N Emojis: http://android.wonderhowto.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/
Section 6: Troubleshooting
Issue: When you try to boot TWRP, you see a screen that says "no command." TWRP does not boot.
Solution: The screen you are seeing is the stock Droid Turbo recovery menu (the menu that you're trying to replace with TWRP). If you see this after flashing TWRP, one of two things happened:
-You did not boot into the recovery menu immediately after flashing TWRP, and it was therefore replaced by the stock recovery menu.
-When you flashed TWRP, the process did not complete successfully.
The solution to both of these problems is to repeat section 2 and follow the instructions more carefully.
Issue: When TWRP asked you if you wanted to allow write access to the system partition, you selected no. Now you cannot flash anything.
Solution: At the main TWRP menu, select Mount. Uncheck the box that says "Mount system partition as read-only."
Issue: Fastboot says "cannot load TWRP.img" when you try to flash it.
Solution: This error indicates that Fastboot cannot find TWRP.img. The most common source of this problem is that you did not make your file extensions visible, and so when you renamed the TWRP file to TWRP.img, you actually renamed it to TWRP.img.img (including the hidden .img file extension that you didn't realize was there). Google how to enable file extensions on your version of Windows, follow those instructions, and if this is the issue you will see it.
nice write up - will follow these when I get my phone tomorrow.
worked!
Just tried this. Worked amazingly, and exactly as you described! Thanks!!
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
SpyderPride said:
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Nope, no matter what I do, it stays on that screen. I have to reboot and then it returns to normal. I've followed all of the steps twice now and got the same results each time. I do have the phone still plugged into the computer charging.
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
5.1
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
CatMan8 said:
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
Click to expand...
Click to collapse
if u want an unlocked bootloader then take the OTA
22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
The screen that you're seeing is the stock Droid Turbo recovery menu, which means that TWRP is not getting flashed. What result does it give you after section 2, step 10?
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Yeah, I did the exact same thing. The MDK bootloader is golden. I broke my phone once and almost cried. Luckily, I was able to get another MDK on Swappa. The seller wasn't even charging extra for it! He/she must not have known what they had.
As for Viper4Android, I've added a link to section 4 that you might want to look at.
iceblitz4 said:
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
Click to expand...
Click to collapse
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
s4shield said:
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
Click to expand...
Click to collapse
Such is life. Sometimes if you want the wubz, you gotta take the brony.
TheSt33v said:
Such is life. Sometimes if you want the wubz, you gotta take the brony.
Click to expand...
Click to collapse
Ha ha ha!
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Awesome post. It definitely will come in handy. One question, at what point should I create a backup image via twrp? Is it before section 3 step 7?
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Download the file www.viperforandroid.com install goto menu set as expert ui under ui setting open viper4android check on click box click appropriate sound changer so it sounds right to u I suggest doing on headphones than use thoose settings as base settings for phone bt ect.. The the real good sound comes in under conolover files you must download impulse response files or. Irs files dfx_pro_surround_2.irs, Dolby,, dfx ect. After u download you unzip and using a file manager find unzipped file and goto sd card u will see viper4android folder inside that folder you will see 2 other folders one being kernel place irs files in kernel folder. Now when you click impulse response you will have the audio producing files. Like Dolby digital cinema, stereo, HD. Ect there are hundreds I'll post my walk though install video
can you help me sir
my friend have verizon moto droid ultra xt1254 and he already give it to me
and i got this phone with google account privacy and he forgot last email in this device, so i cant finished setup wizard and go to home screen
this device locked bootloader so i cant do something to
what should i can do?
jco23 said:
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Click to expand...
Click to collapse
Thanks for the help.
After I got stuck, I downloaded and installed KingRoot. It successfully rooted my phone. I downloaded two different root checkers and they confirmed. Everything works correctly within Rom Toolbox Pro now, I can remove apps (stupid NFL mobile, Amazon, etc). My software status says "Modified". I did not need to format or anything like that. Is that normal? My only issues are with XBlast Tools and SuperSU, when I change a setting in XBlast, it does NOT get updated. Even after a reboot. In SuperSU cannot update binaries for some reason.
I cannot post outside links for screen shots yet.

[REF] [ROOT] [RECOVERY] [BOOT LOADER] Metro PCS LG K7 LGMS330 [Guide For Dummies]

I have not been on this site since posting my guide, i do want to let any future people reading this know that, I am not a professional. everything in this guide is using stuff from other peoples threads.... this thread is just step by step directions on how i rooted (and installed TWRP on) MY lg k7 (MetroPCs). Also i had to root before i unlocked the boot loader. Which is not safe, you should probably unlock the boot loader before you root, but i couldn't figure out how to unlock it without root access.
I AM NOT RESPONSIBLE FOR ANY THING THAT HAPPENS TO YOUR DEVICE!
YOU AND ONLY YOU CAN BE HELD RESPONSIBLE​
~BACK UP FILES ON PC, YOUR PHONE WILL BE RESET TO FACTORY SETTINGS DURING THIS TUTORIAL~
Step One: Enable Dev Options
A) open settings>about phone>software info then tap "Build Number" really fast about 10 times
B) open settings>Developer Options, then check the box labeled "Enable OEM Unlock", and the box Labeled "USB Debugging"
Step Two: Install Android SDK/ADB/USB drivers
A) go to http://developer.android.com/sdk/index.html in your browser, and click download...
B) go to https://www.microsoft.com/net/default.aspx in your browser, and click the big blue button that says .NET
Framework 4.6.1 or X.X.X depending on when your reading this...
C) go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html scroll down until you get to the first box, labeled Java SE Development Kit 8u91 or XuXX Depending on when your reading this, then find your OS (ex: Windows x86, Mac OS, Linux, Etc..), then select the download link
Step Three: Installing LG K7's USB Driver's
A) unlock your phone
B) plug your phone into you Computer via USB
C) pull down your notifications, Tap on the USB icon which should be labeled "Media Device (MTP)," "Send Images (PTP)," or "Charge Phone"
D) if a dialogue box pops up asking to install drivers tap install, if not proceed to step E
1) Your PC should ask you if you want to auto run, Either auto run or open the folder and run LG_PC_Programs.exe then proceed to Step Four
E) select "Media Device (PTP)," if not already selected
1) click the three vertical dots next to the magnify glass in the upper right hand corner, select install pc drivers, then tap install
Step Four: Installing Java SE
A) return to the folder where you downloaded the files in step two, install the file which contains the word java in it
Step Five: Installing Microsoft .NET 4 Framework
A) now in the same folder as step four, install the with the name "NDP461-KB3102438-Web," the name might be different then mine depending on when you are reading this
B) if it is already installed it will notify you and you can proceed to the next step
Step Six: Installing Android Studio 2.0 (SDK/ADB Drivers)
A) in the download folder from step four & five, double click the remaining file, the name should contain the words "android", and "studio" in it
B) when the dialogue box opens requesting admin rights, select allow
C) click next
D) click next
E) make sure all boxes are checked and click next
F) read the license agreement, (unless your the 99.9% that doesn't) click i agree
G) you may click next or choose where you'd like to install android studio, and where you'd like to install SDK, for this tutorial i will change make a new folder in my docs named SDK then change the SDK install dir to My Docs
H) click next
I) it will take a moment to install so just wait
(note: the progress bar will fill up, then reset, as it is installing in two separate locations)
J) when finished, click next
K) uncheck the box and click finish
Step Seven: Root your device
(Note: I rooted before i unlocked my boat loader, as i could not get it to boot into boot loader mode until i rooted it)
A) go to http://www.kingroot.net/wap on your android device and download the apk file
B) go to settings>security and check the box labeled "Unknown Sources"
C) install the apk
Video tutorial for king root here: https://www.youtube.com/watch?v=tG_ruuTPVpU
(Not my channel or video)
D) open the king root app
E) make sure you have a charged battery or your phone is plugged in as the rooting process time may vary (better safe then sorry)
F) swipe up until you see a "TRY IT" button click it
G) under "Root Access not available" tap "Get Now
H) do not turn off your phone
I) when it is done you can tap optimize now if you wish, otherwise close the app
Step Eight: Replacing KingRoot with SuperSU ~ W0lfDroid Method
A) go to http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
B) scroll down until you see the word "download:" (should be right above the related posts
C) click on the "new link" next to "Replace_Kingroot_With_SuperSU.zip"
D) extract the .zip so that the "MRW" folder is on your internal storage
(Easiest way is to download it on PC and open up your k7 in "my computer" and select internal storage and drag the MRW folder inside the .zip there)
E) go to google play and search "terminal emulator for android" or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
F) install the first one, or use this link if your reading this on your phone https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
G) open terminal emulator
H) type "su" without the quotations
(everything typed in the terminal is case sensative)
I) type "sh /sdcard/mrw/root.sh" without the quotations
J) you might see a few errors, that is fine
K) wait until it says finished
L) when SU opens, select "update" "install" or what ever pops up
M) when it asks to uninstall, uninstall it, it is not uninstalling SuperSU it is uninstalling Kingroot,
O) if 30 minutes pass and it is still uninstalling then exit the app and then reboot the phone
DO NOT STOP HERE ~ YOU HAVE TO UNLOCK THE BOOTLOADER, and OPTIONALLY FLASH TWRP
Step Nine: Unlocking The Bootloader
A) refer to step one and double check the OEM unlock is enabled and USB debugging is turned on
(If not then please enable them)
B) search quick boot on the google play store download the first app it should be a circle with a lightening bolt
C) open quick boot
D) when asked to "allow root access?" tap allow
E) if an add pops up close it with the ex in one of the corners
F) tap on the word boot loader
G) at the top of your phone you should see " * Welcome To Fast Boot Mode : "
H) now go to your SDK dir, in my case it is C:\Users\USER\Documents\SDK
I) hold shift, then right click on the "platform-tools" folder, then select "open command window here"
J) in the CMD window type "fastboot devices" - without quotations
(everything is case sensative)
K) then type "fastboot oem unlock" - without quotations
L) then type "fastboot getvar unlocked" if that doesn't work try "fastboot getvar" or "fastboot getvar unlock" to confirm if it is unlocked
(if non of the getvar commands work you did something wrong, and i wont be able to help you, but if you followed the tutorial you shouldn't have any issues as these are the exact steps i took)
M) then type "fastboot reboot"
LEAVE THE CMD OPEN OR YOU WILL HAVE TO REPEAT steps H-I
Step Ten: Flashing TWRP
A) go to http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 and click on the latest download for twrp for me it is BETA1
if the links on that page dont work then use the links here http://forum.xda-developers.com/showpost.php?p=66282525&postcount=42
B) extract the download into your SDK folder on your PC
C) in the sdk CMD window from Step nine
D) type "fastboot devices" - without qoutation
E) ~optional, HIGHLY RECOMENDED~
1)type fastboot "boot twrp-image-3.img" - this will boot up twrp WITHOUT flashing it, just so you can make sure everything is working right
in my case it was twrp-image-3.img check your twrp file name and replace fastboot boot twrp-image-3.img with
fastboot boot INSERT YOUR FILE NAME HERE.img
2)in twrp tap reboot>bootloader
F) when bootloader mode opens back up
G) type "fastboot flash twrp-image-3.img" or "fastboot boot INSERT FILE NAME HERE.img" depending on your file name
H) when finished flashing type "fastboot reboot"
Step eleven
A) follow instructions on step one
B) the reason you must do this is because when you flash TWRP it erases your entire phone and resets it
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7
Well done, my friend. Well done indeed.
[QUOTE
Congrats you have Successfully Rooted, Unlocked Your Bootloader, and Flashed TWRP, to your LG K7[/QUOTE]
is this ok with the gapps 5.1 instsall .zip for twrp install or should i use a different? also, do you have a suggested camera app? awesome thread btw. Nevermind simple twrp install fixed everything.
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Today backup important files you need!
Is this a real method BC everybody having problems rooting this device so I ask can u make a video and add screenshots
Sent from my LG-D800 using Tapatalk
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
zgauthier8286 said:
I can confirm this method works. The only different thing i did was purchase Supersume pro from playstore. Worked like it said it would. The Ls675 is rootable. But no bootloader unlock or bootloader at all for that matter. Im running MS330 with TWRP full root and have twrp backups and fastboot flashable backups via flashfire....
---------- Post added at 02:28 AM ---------- Previous post was at 02:20 AM ----------
https://mega.nz/#!CRAVWAyI!QIbo20-0ZnVqlREs7ZXF66aB_Eh3UjCEMVQbLuP1Zec
https://mega.nz/#!zBoxGIQR!buXvorPkA14Vr2Idn7uhNPHanOL6wbvcEav3MhRdjv8
https://mega.nz/#!yQBg1ayC!r3qvWfLjCAKg0e8t91J1IEtae8_EwhvYTXjawv7b_2A
Screen shots of root, flashfire backups, and device info
Click to expand...
Click to collapse
can you please help me i have 2 MS330 that are bricked
callihn said:
While it does work I can find no method using the buttons to get into twrp all the instructions I find for recovery fail so I can only boot back to it after the phone boots, thus it's worthless at this point. Also the command is fastboot flash recovery imgagename.img and you'll need to remove kingroot from administrators to uninstall.
Anyone else been able to boot directly into twrp from the off position?
Click to expand...
Click to collapse
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
zgauthier8286 said:
Try to do the factory hard reset trick but say no at the second screen. I haven't tried it out yet but I've been reading around several sites and that's a possible solution
Click to expand...
Click to collapse
Just reboots. Think we're going to have to change something? Boot image? Kernel?
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
callihn said:
Just reboots. Think we're going to have to change something? Boot image? Kernel?
Click to expand...
Click to collapse
Of other interest 5.1 is very dendent on Google apps and move app updates to the system via TB or Link2SD fails more than it succeeds, shows they moved but app inaccessible afterwards hence brick. Mine went down trying to integrate play services and reinstalling from adb didn't help. FYI if you relock the BL it'll lock the phone with a security error too. Moving play services causes unending error screens so you can't really see if it's done moving, but I waited a good 5 minutes before reboot. Issue on fails could have been the system not being r/w. Needless to say backup, backup, backup as I hadn't because I've never had a serious issue doing that and considered it a trivial task. Anyone had good success with integrating updates and cache? Anyone restored from twrp yet?
JayCouture.com said:
Does anyone know a way to successfully root this phone? Not just recover?
Sent from my LGMS330 using Tapatalk
Click to expand...
Click to collapse
Yes! Just follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=66456635&postcount=1
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
callihn said:
Can you figure out why we can't boot to recovery via hardware buttons? That's critical for tinkering and testing on the go since I always have my phone but not my laptop for booting into recovery with adb. Not sure exactly where to look, probably start with a search for the words "recovery" and "safe mode" for the buttons and "security error" in the boot.img files.
Click to expand...
Click to collapse
If your rooted u can dl a reboot recovery app on the play store I have one that works like a charm. But im gonna take a look through Linux at the kernel options using make menu_config and see if there's anything I can see in there.
zgauthier8286 said:
I'm no developer by any means but I have Linux and windows on my laptop. I'm familiar with kernel building on bunt and have the source code for MS330 on my laptop. I have a backup of my boot img as well. If you can get to fastboot u can probably flash my boot img if you want me to send it. I have recovery img as well which is twrp. Let me know if you have any ideas on what u need or i can do as far as possibly doing a fresh build kernel later tonight and getting a zImage out of it
Click to expand...
Click to collapse
im having a problem w the security 9 error boot loop. only seem to b able to get it into download mode , not bootloader or recovery. would your boot and recovery img's help me at all ya think ? thanks !
goitalone said:
I have tribute 5 and can't access bootloader or install SuperSU.....always fails.
How can I get this to work?
Click to expand...
Click to collapse
Thanks again. For anyone that has a soft bricked LG K7 see this man! He brought my S#!? To life through teamveiwer. Thanks again. From my LG K7.
Maybe just my experience, but regarding step 10. I had to have the twrp image in SDK>platform tools, also when you get to fastboot flash twrp-image-3.img, I couldn't get it to work, until I typed it as fastboot flash recovery twrp-image-3.img. Hope this helps anyone else getting errors during this part. Thanks for the writeup.

R1HD update 6.6 AND 7.4.2 bootloader ROLL-BACK Instructions

This is FINAL working method.
First off you must unlock bootloader, and install twrp.
instructions for unlock bootloader are in this thread
http://forum.xda-developers.com/r1-...mazon-root-t3490882/post69387472#post69387472
I made many cycles between 6.6 and 6.1 and found that this set of files was minimum needed to maintain stable device. I started with only the preloader, and that left the phone able to connect to spft but the preloader was o longer in the "trusted zone" so it would not load the second step of power on (lk). replaceing the lk with spft after that allowed to boot to the boot menu, but would not trust the next step(boot.img). But with the preloader and lk I was able to fastboot, so was able to oem unlock.. this was the first method I was going to suggest. After more trials I decided it better to foll back all the bin files that the update replaced and also the secret bin so no more need to oem unlock after the roll back.
I got so comfortable moving between preloaders and version I got careless. My carelessness allowed me to mix up secure preloader and bin files with custom non secure recovery files and without realizing it I rebooted like that. I was left in a secure environment that was panicking because the recovery was not properly signed. (a terminal soft-brick)
My point is once you roll back DO NOT go back to locked and DO NOT blame me if you forget and restore some backup that does that to you down the road.
I do recomend that you roll back though. Because with the roll back, you are almost certain not able to brick because you can always use spft to to fix things.
THIS WILL ROLL BACK BOOT LOADER AND ALLOWS SPFT .
THIS HAS ONLY BEEN RUN WITH TWRP.
But the fastboot mode can also flash preloader if prefered. Just remember you may also need to oem unlock again after. This has not and will not be tested by me.
ONCE YOU HAVE UNLOCKED BOOTLOADER AND INSTALLED TWRP, return here and download "after_bootloader_roll_back_5.tar" unpack the tar and run the .bat file. It will adb push the recovery image to you phone and then install it.
It will rewrite :
1. preloader
2. lk (little kernel)
3. boot img
4. seccfg.bin
5. frp (to make sure bootloader remains unlockable)
6. trustzone (goes into both TEE1 and TEE2
7. secro.bin
All done.
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
jhonjahegu said:
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
Click to expand...
Click to collapse
Sounds like you need to do oem unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot oem unlock"
6. If need to do oem unlock you will also need to "fastboot format userdata"
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
digihaven said:
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
Click to expand...
Click to collapse
If it is looping into twrp then you must do step 6 from above.
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
clownkitty said:
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
Click to expand...
Click to collapse
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
mrmazak said:
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
Click to expand...
Click to collapse
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
clownkitty said:
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
Click to expand...
Click to collapse
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
mrmazak said:
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
Click to expand...
Click to collapse
I didn't realize you had to load straight into recovery mode after flashing it, I got it to work now, thank you so much!
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
tuespazio said:
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
Click to expand...
Click to collapse
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
mrmazak said:
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
Click to expand...
Click to collapse
Hi, dont worry now is fixed i return to 6.1 and then flash full 6.5 firmware.
Data is now working fine .
Thanks for your Support
sorry, wrong thread
ncy1 said:
Hi guys, sorry to bother you with this
I was on 6.0 rooted and without ads, i just tried to update my phone using the v17 and settings on this thread, when i went to cellphone info on settings it said i was still on 6.0. Did i miss something or this a normal thing? Anyway, i went back to recovery mode, did a wipe and tried to flash the 7.4.2 rom but it sent me an error, now the phone won't boot and gets stuck on the blu loadscreen.
Click to expand...
Click to collapse
Don't get me wrong, I feel bad for you that your phone is in this situation, but that has nothing to do with the thread you are posting in.
This thread is for rolling back the preloader.
And all the oem and Amazon Roms are 6.0
To get help you should post in the thread you got the ROM from.
And include the error you got.
mrmazak said:
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Click to expand...
Click to collapse
I think I just want to try this method, since I want to convert it to OEM and still keep OTA updates anyway. I'm blanking though as to how I need to go about this.
I have adb installed, and I have access. I assume this requires a fastboot command, but I don't know which.
Jessooca said:
Mrmazak... does this work on a new out of the box blu r1 that came with the 6.6 August update already installed?
I'm trying to help a friend, I surprisingly can't get the bootloader unlocked, dirtycow continually failed.
He doesn't care about updates etc... just wanted to flash the no ads firmware onto a prime version blu r1 hd
Click to expand...
Click to collapse
To the best of my knowledge it was.
Last time someone told me they were having trouble, they ran the codes manually one by one instead of using the script, and it worked. Apparently they had trouble pushing the files from the batch file. I had similar trouble when I wrote the script, that is why there are 3 second pauses ,that seemed to fix it for me. I will change them to 10 seconds and see if it helps.
I will update here when I change it then you candownload again and try, or you can make the changes yourself and let the me know
OK i updated the one-click.bat . you can download it again to see if that help. Also you said dirty-cow keeps failing, please let me know the fail message and also the comments displayed during the first part of the script. the part that is pushing files.
Also I have not been able to get feedback on the one-click.sh for linux. I don't normally use linux and did not test the shell. If you are using that one maybe the fail is my poorly written .sh
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
danbcooper said:
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
Click to expand...
Click to collapse
"oem" is not supposed to be capitalized
i went back and edited that original post too.
mrmazak said:
"oem" is not supposed to be capitalized
i went back and edited that original post too.
Click to expand...
Click to collapse
Now I ran "fastboot oem unlock" and it says FAILED (remote: unknown command). Do you know why?
Never mind.. Tried again and worked! Thanks for everything!

How to downgrade from Android 7.1.1 Beta (Build NPF26F)

Hey guys, so I bought a second hand Nexus 6P, and it was running the latest android beta.
Is there anyway for me to rollback or downgrade the version, so that I can unlock boot loader, and root the device?
I'm interested in installing this rom
http://forum.xda-developers.com/nexus-6p/development/rom-weta-v1-0-t3350665
Any help is appreciated
gger123 said:
Hey guys, so I bought a second hand Nexus 6P, and it was running the latest android beta.
Is there anyway for me to rollback or downgrade the version, so that I can unlock boot loader, and root the device?
I'm interested in installing this rom
http://forum.xda-developers.com/nexus-6p/development/rom-weta-v1-0-t3350665
Any help is appreciated
Click to expand...
Click to collapse
I don't run the previews, so forgive me if I'm missing something here, but.. why do you need to downgrade to unlock the bootloader? Do the previews not have the "OEM Unlocking" option in developer settings? All you need to do to is enable that and then plug it in to a PC and use "fastboot flashing unlock" to unlock the bootloader. That will wipe the entire phone, including internal storage. Then just fastboot a custom recovery and install your ROM of choice.
If the previews don't have the OEM unlocking option, then log into your Gmail account on the 6P and then visit Android.com/beta and it should show your device enrolled in the beta, select unenroll. This will also wipe all data including internal storage. From there you'd go back to my first paragraph.
Read this and familiarize yourself with it and you're good to go!
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page513
RoyJ said:
I don't run the previews, so forgive me if I'm missing something here, but.. why do you need to downgrade to unlock the bootloader? Do the previews not have the "OEM Unlocking" option in developer settings? All you need to do to is enable that and then plug it in to a PC and use "fastboot flashing unlock" to unlock the bootloader. That will wipe the entire phone, including internal storage. Then just fastboot a custom recovery and install your ROM of choice.
If the previews don't have the OEM unlocking option, then log into your Gmail account on the 6P and then visit Android.com/beta and it should show your device enrolled in the beta, select unenroll. This will also wipe all data including internal storage. From there you'd go back to my first paragraph.
Read this and familiarize yourself with it and you're good to go!
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page513
Click to expand...
Click to collapse
Hey mate, thanks for guiding me! It does have the OEM unlocking option. I will now look into following your steps, Appreciate the help.
gger123 said:
Hey mate, thanks for guiding me! It does have the OEM unlocking option. I will now look into following your steps, Appreciate the help.
Click to expand...
Click to collapse
Hopefully you were able to figure it out! But like you discovered, it does have an OEM unlocking option. I'm running the dev preview, and rooting is just as easy. If you haven't found any guides here's what you need to do.
Also, make sure you also turn on USB Debugging in your developer settings.
If you've already unlocked your phone, then you already have adb set up. In the case that you don't, install adb on your computer. This tool ( forum.xda-developers.com/showthread.php?t=2588979 ) is very easy to use, although there are other ways to get adb. Run it and select yes to all to install adb. You access adb through your cmd.
1) Download TWRP (custom recovery) from here - dl.twrp.me/angler/
2) Download SuperSU onto your phone from here - download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
3) Put your phone into fastboot. Power down and then hold power and volume down until fastboot pops up. Plug into your pc and then open command prompt.
4) Type " fastboot flash recovery * ". The * should be replaced with the location of the file and then the file name such as C:\Users\Kris\Desktop\twrp-3.0.2-2-angler.img
then hit enter and it should write your recovery.
5) Use your volume down button to scroll to the tab that says recovery. Hit your power button to boot into recovery.
6) You'll get a popup and go ahead and swipe to allow your system to be modified. Tap on the "Install" tab in the top left. Locate the SuperSU zip and select it. Swipe to flash it.
7) Once that's completed hit reboot and you're successfully rooted!

Categories

Resources