Database Develop

[HOW TO][Unlocked Bootloaders]Install Fastboots, CWM, Tips & Ticks, and More

Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Install Stock Fastboots ICS
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc

I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2

miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD

I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2

miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?

Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.

miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me

Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2

miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.

tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.

I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.

probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another

i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx

htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.

skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?

yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?

Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP

htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)

thanx again..
ahahahha...what a beautifullll day....

skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???

For those getting the not enough memory error while flashing the 5.0 Factory Image

THIS WILL FACTORY RESET YOUR DEVICE AND DELETE EVERYTHING
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot
You may need to boot into the bootloader again and wipe cache/factory rese or reset it from the phone settings itself.
Please put this script in the same folder as all the extracted files mentioned in the script above.
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
EDIT:
Edited script to remove the reboot bootloaders and also reboot the phone when it is done.

reinert012 said:
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
Click to expand...
Click to collapse
Is everyone who's getting this error on the 16gb model? Or are there people on the 32 gb model experiencing it as well?

cbowens said:
Is everyone who's getting this error on the 16gb model? Or are there people on the 32 gb model experiencing it as well?
Click to expand...
Click to collapse
I do not know, i'm on 16gb myself.

I was getting this error on my 32GB device
So I went ahead and did the flash commands
Now its showing my 32GB device is a 16GB device
Something bad happened

shoemocker said:
I was getting this error on my 32GB device
So I went ahead and did the flash commands
Now its showing my 32GB device is a 16GB device
Something bad happened
Click to expand...
Click to collapse
Boot recovery and factory reset?

reinert012 said:
I unzipped everything in the factory image and the ZIP file inside the factory image and made this a batch file, and ran it...works great! Be sure to boot into the bootloader:
NOT MY FAULT IF YOU BREAK YOUR DEVICE THIS WILL WIPE IT CLEAN!
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.21.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
You may need to boot into the bootloader again and wipe cache/factory reset.
Please put this script in the same folder as all the extracted files mentioned in the script above.
Script: https://www.dropbox.com/s/tfazy6rqamqpazo/flash-all-modified.bat?dl=0
Original Comment Below
http://forum.xda-developers.com/showpost.php?p=56700113&postcount=63
Click to expand...
Click to collapse
Worked for me on 16gb. Was getting error flashing system.img. Thanks!

reinert012 said:
Boot recovery and factory reset?
Click to expand...
Click to collapse
I just did a factory reset through the settings in the rom itself and that did the trick - thanks for your help

xmishka said:
Worked for me on 16gb. Was getting error flashing system.img. Thanks!
Click to expand...
Click to collapse
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
Click to expand...
Click to collapse
So I just did a fastboot reboot after that. Phone is booting. Fingers crossed.
If it boots successfully, is there anything else that I need to do after that?

theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
Click to expand...
Click to collapse
Just use your volume keys on the phone so it says Start and then hit the power button or fastboot reboot via the cmd prompt.

theretroandroid said:
After flashing cache.img, what's the next step? could you please post the next set of commands for a full reboot of the phone.
Sorry, noob here.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
So I just did a fastboot reboot after that. Phone is booting. Fingers crossed.
If it boots successfully, is there anything else that I need to do after that?
Click to expand...
Click to collapse
Nope, just give it a few min to boot up all the way.

I m getting this error while flashing user data, mine is 32gb one
EDit- just did factory reset from recovery, now it works fine.
Damn you google , you a sec I thought my emmc has got corrupted

reinert012 said:
Nope, just give it a few min to boot up all the way.
Click to expand...
Click to collapse
It booted fine and is working. Setting it all up now. Thanks so much.

This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why

I just did a factory reset using the phones settings menu.
Sent from my Nexus 9 using Tapatalk

anshmiester78900 said:
This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why
Click to expand...
Click to collapse
Boot into bootloader and run the script again, make sure all the files are in the right place. I will run it again with TWRP installed and see what happens.

anshmiester78900 said:
This thing didn't work for me at all it started the twrp then it got into bootloop with the twrp i dont know why
Click to expand...
Click to collapse
I ran my script with TWRP installed and it worked perfect...please make sure ALL of the files in the script are in the same folder as the script.

reinert012 said:
I ran my script with TWRP installed and it worked perfect...please make sure ALL of the files in the script are in the same folder as the script.
Click to expand...
Click to collapse
I just flashed back to kitkat full stock
ALso now can you please be precise with the steps . Please . What files and where do i have to put them . Just confirming it from you as i got a bit confused with the first post

Er, mine also failed because of lack of memory, but it still booted up into lollipop. Should I reflash using your updated script?

anshmiester78900 said:
I just flashed back to kitkat full stock
ALso now can you please be precise with the steps . Please . What files and where do i have to put them . Just confirming it from you as i got a bit confused with the first post
Click to expand...
Click to collapse
1. Download the factory image from Google.
2. Extract those contents into your platform-tools folder wherever that is.
3. Go to the extracted folder, copy ALL the contents back to your platform-tools folder
4. Extract the contents from image-hammerhead-lrx21o.zip (this was in the extracted folder from step 2, which you copied in step 3) and make sure it's in the platform-tools folder again.
5. Make sure script is in the platform-tools folder too, and run it.
I just ran through this on my phone again....works fine.

reinert012 said:
1. Download the factory image from Google.
2. Extract those contents into your platform-tools folder wherever that is.
3. Go to the extracted folder, copy ALL the contents back to your platform-tools folder
4. Extract the contents from image-hammerhead-lrx21o.zip (this was in the extracted folder from step 2, which you copied in step 3) and make sure it's in the platform-tools folder again.
5. Make sure script is in the platform-tools folder too, and run it.
I just ran through this on my phone again....works fine.
Click to expand...
Click to collapse
Alright going to give it a try
---------- Post added at 05:54 AM ---------- Previous post was at 05:45 AM ----------
UPDATE:
Thanks a lot mate it worked . now my phone is booting up, I hope i dont get that problem where storage is reduced to half as i have 32gb model
anyways thanks a lot again
UPDATE 2:
my storage is reduced to 12.6 gb, how to fix this mate ?

Unable to unroll from Nougat

Hey,
I enrolled to the Android Nougat program and rooted my phone (chainfire) a few days ago. Decided to un-root (using superSU), and it said I was unrooted. After doing the un-rooting, the OEM unlock-option was greyed out (and on OFF setting), but the phone recovery says it's unlocked api 3.... I pretty much just wanted to unenroll and go back to MM. Every time I choose unroll from Google, download the MM OTA and it reboots I get an error. Just an image of android with message "ERROR". The only way to get the phone working is to do a hard reset and go back to Nougat.
Not quite sure what is wrong here. Any suggestions?

It's probably because the SuperSU unroot hasn't cleaned up everything that the MM installer checks for. Your best bet is to use the sideload OTA here:
https://developers.google.com/android/nexus/ota
to install MM again. It's quick and easy, and doesn't touch your data.
Since you received the actual uninstall OTA you must have successfully unenrolled, so you should be ok from now on.

dahawthorne said:
It's probably because the SuperSU unroot hasn't cleaned up everything that the MM installer checks for. Your best bet is to use the sideload OTA here:
https://developers.google.com/android/nexus/ota
to install MM again. It's quick and easy, and doesn't touch your data.
Since you received the actual uninstall OTA you must have successfully unenrolled, so you should be ok from now on.
Click to expand...
Click to collapse
I received the OTA but while installing MM it gives me an error, so I have to go back to Nougat every time. I've tried the unenroll option several times and it gives me the same "error" every time. So, I should try manually flashing MM, then?

UPDATE:
I tried the following:
Downloaded and tried to sideload 6.0.1 (MOB30W) to my Nexus 6-device. It got up to 46% and after it gave me and error saying:
WARNING: No file_contexts. This package is for shamu devices; this is a "".
E: Error in /sideload/package.zip
Status 7
Installation aborted.
UPDATE2:
Tried another package. Didn't work. All the OTA updates stop at 46% giving me the same error. Device remains unlocked, but appears not to be rooted. Still stuck on Nougat.

What does "Tried another package" mean?
It may be that your download was corrupt. I always check the SHA with this checksum utility:
http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
though I've read in the instructions that the Android installation itself checks the package - it may be this error that the installation is reporting.

dahawthorne said:
What does "Tried another package" mean?
It may be that your download was corrupt. I always check the SHA with this checksum utility:
http://download.cnet.com/MD5-SHA-Checksum-Utility/3000-2092_4-10911445.html
though I've read in the instructions that the Android installation itself checks the package - it may be this error that the installation is reporting.
Click to expand...
Click to collapse
No, the checksum is fine. The package is fine. I mean I tried several OTA packages for N6 and it always stops at 46%. There's something else going on here. Maybe if I re-root with chainfire and the use another method to unroot it? Which is the correct method, I have no idea?

Factory reset, and try sideloading MOB30W again.

dahawthorne said:
Factory reset, and try sideloading MOB30W again.
Click to expand...
Click to collapse
Done it like 5 times already. Also wiped cache. No help.

Hannes084 said:
Done it like 5 times already. Also wiped cache. No help.
Click to expand...
Click to collapse
My suggestion is to go back to Android N, root with SuperSU and see if your OEM UNLOCK toggle in Developer Options is working again and not greyed out. Then I would fastboot flash back to MM and install TWRP and SuperSu.
Sent from my Nexus 6 using XDA-Developers mobile app

Dude, just flash the system image you want. Forget about the OTA

The OTA is a system image.

fast69mopar said:
My suggestion is to go back to Android N, root with SuperSU and see if your OEM UNLOCK toggle in Developer Options is working again and not greyed out. Then I would fastboot flash back to MM and install TWRP and SuperSu.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Root with SuperSU? I think you mean with chainfire?

dahawthorne said:
The OTA is a system image.
Click to expand...
Click to collapse
You could say the new full otas are, but you can't go flashing them freely over newer images.
The unenroll option resets the phone anyways, so the best and aparently the only option for him is to flash the system image he wants from scratch.

blanco2701 said:
You could say the new full otas are, but you can't go flashing them freely over newer images.
The unenroll option resets the phone anyways, so the best and aparently the only option for him is to flash the system image he wants from scratch.
Click to expand...
Click to collapse
Sorry for asking but how would I even do that? I'm on Ubuntu 12, so it seems mega complicated.

Hannes084 said:
Sorry for asking but how would I even do that? I'm on Ubuntu 12, so it seems mega complicated.
Click to expand...
Click to collapse
Well my friend I have no idea since I'm on Windows. Google how to use adb and fastboot on ubuntu, there should be a solution for you.

This is a script that I used to run before the full OTAs became available. It worked many times for me, but the usual caveat - you follow it at your own risk. You can probably skip the backup step in your situation.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
This is a script that I used to run before the full OTAs became available. It worked many times for me, but the usual caveat - you follow it at your own risk. You can probably skip the backup step in your situation.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
If I download the factory image (OTA) off google's site it has none of those files under the zip-folder.

Hannes084 said:
If I download the factory image (OTA) off google's site it has none of those files under the zip-folder.
Click to expand...
Click to collapse
One thing is the OTA image, and another is the Factory Image.
Download the factory image from here.
https://developers.google.com/android/nexus/images#shamu
Unzip everything and you should get all the files needed. As I said before, you would need to have a computer with adb and fastboot installed.

blanco2701 said:
One thing is the OTA image, and another is the Factory Image.
Download the factory image from here.
https://developers.google.com/android/nexus/images#shamu
Unzip everything and you should get all the files needed. As I said before, you would need to have a computer with adb and fastboot installed.
Click to expand...
Click to collapse
Thanks, doing that now!

Hannes084 said:
Thanks, doing that now!
Click to expand...
Click to collapse
Just be sure to have selected "oem unlocking" in the developer options, make a backup (everything will be wiped), and start flashing!. There are several guides everywhere.

BLU R2 LTE??? unlock/rootable?

I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?

DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813

Thanks. Looks like I have plans for NYE

I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.

somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link

somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!

bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.

Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.

Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.

Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse

Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.

Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx

Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.

8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.

How to flash rom zip with payload.bin inside via twrp?

I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.

stevedat said:
I easily flash any roms via twrp, but recently some rom come with payload.bin inside the zip. I cant manage to flash it via twrp, it ends up with error with zip format?
I saw a thread that mentions to unpack the payload.bin and put all unpacked files into fastboot folder, then fastboot these files separately.
Is there any way to make it as easy as it used to.
Click to expand...
Click to collapse
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.

Identity77 said:
Actually. Its not that hard the using the fastboot version. You will just extract the file then run the batch file. Then wait to finish. Better than ota. Retain my data.
Click to expand...
Click to collapse
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.

stevedat said:
You mean that if I come from other Rom, just wipe all in twro, then flash it by using batch file and just connected the phone to pc as fastboot mode.
Click to expand...
Click to collapse
I Didnt try with other rom. It has the a and b thing. I got problem with ota because im rooted with magisk. Got into bootlloop. This fastboot thing saves me. And i was able to upgrade to latest.