Database Develop

[SOLVED] Flashing back Stock Recovery (from recovery)

[SOLVED] See below
Hello,
I need to return my phone to repair service and would like to flash a zip from recovery to go back to stock recovery.
(I can't flash thru odin : stuck at "Nand write start").
I just flashed Philz recovery to backup my internal SD data, but want to make it look cleaner... (I'm clean on download screen).
I found this thread but it's a flashable zip for sgh-t879 t-mobile galaxy note :
http://forum.xda-developers.com/showthread.php?t=2072255
Do you think I can try to flash it ? (phone is almost dead already but I don't want to have it says T-mobile at boot or in the recovery ! and be stuck like this :cyclops:!)
Thanks in advance !
Edit : Solved
To create a flashable stock recovery so that my bricked phone looked like untouched for repair service here is what I did :
(follow this guide only if you know what you're doing)
- I took an existing flashable kernel/recovery (tried with Abyss Kernel or Speed Core 15)
- Unzip it in one of my computer folder
- from a stock rom .tar I took the zimage file and copied it over the zimage file in the unzipped folder, replacing previous file
- I selected both zimage file an META-INF folder and zipped them in a new zip named stockrecovery.zip (right clicked with 7zip, chose add to zip...) with Normal compression Level (note when opening the zip file you must directly find zimage and META-INF folder)
- Copied the zip to external SD and installed zip from recovery (signature check disabled)
Hope this may help others.
Note: I can't go in adb shell since though my device is seen. I don't know/think I'm unrooted, but I'll say I did all I could (at my level to make the phone looked like genuine/untouched)...
NB: I prefer not to post the file I created.

Re: Going back to Stock Recovery
I think if you look Dr Ketan in the stickies has posted links to original firmwares and kernels.
Sent from my GT-N7000 using xda app-developers app

I really looked in the thread and didn't find a flashable stock kernel from recovery. (My phone does'nt work with odin anymore...)

eljuggy said:
I really looked in the thread and didn't find a flashable stock kernel from recovery. (My phone does'nt work with odin anymore...)
Click to expand...
Click to collapse
What about Modile Odin? does it get stuck with Mobile Odin as well?

Re: Going back to Stock Recovery
Download the philz kernel ics rom zip file. Also download the stock kernel from the stock ics rom. This will be a zimage.
Now open the philz zip file and replace the zimage in that zip file with the stock one. Place it on sd card. Now boot into recovery and flash it. As you have Cwm this should flash.
As always. Do this at your own risk.
Edit: Use speedmod as it has a simple updater script.

Ok, so I tried exchanging the zimage file in the Phil'z zip with the zimage file from the stock rom tar, but it states "installation aborted" when trying to flash...
surely there's a signature system in the meta folder or something...
I also noticed that in Phil'z zip is busybox and superuser apk... which I don't want ...
well, I'll post in Dr Ketan thread... for help again.
Thanks !

Re: Going back to Stock Recovery
Yeah. I forgot that. I check speedmod k15 and it just has a zimage and the updater script. Try with that. If it fails, try the signature verification toggle in recovery.

Well...
without signature verification I also got "installation aborted"....
with signature verification I get "signature verification failed"
there's something blocking the update and it's before the script into the zip starts and prints "Flash SpeedMod Kernel"...

Re: Going back to Stock Recovery
Can you tell me how are you replacing the zimage?
---------- Post added at 04:12 AM ---------- Previous post was at 03:54 AM ----------
Do not EXTRACT the package. Just open it using 7z and replace the zimage.

Ok, I used 7zip to build the zip and compression level was none... that was the problem.
I used normal compression and was able to flash the zip...
Now my phone really looks like stock (I've got the white box and the little green droid when trying to go to recovery then lot of errors and Android System recovery (3e) and also a clean bootloader screen) !
Ready for repair service !
Thanks a lot !

Ok Great

Ok I edited first post... and I'm ready to go to repair service !
One last thing, is it normal I can't do "adb shell" anymore once in stock recovery (adb devices list my devices, but adb shell is stucked) ?
I wanted to verify that the phone is unrooted now? Do you think it is ?

just replacing the kernel to stock doesnot unroot the phone. hopefully they will not know.. not sure about adb shell

[Solutions] OTA update not insatalling stuck at Red triangle

Many user at XDA everyday asking this same Question again and again.
Our phone not updating after getting OTA update.
Symptoms
Phone reboots to recovery but stuck at red triangle
Requirements
>>Stock recovery ( custom recovery TWRP/CWM can't flash OTA )
>>Stock system unmodified (custom kernel modifies system files so if you flashed custom kernel you need original files to restore)
>> Data/preload Apps ***Most Important*** according to phone software version (different CID contaions diffrent apps) when we unlock bootloader it delets data partition so data/preload apps also when OTA check OS integrity it also check data/preload apps with their md5/sha-1 match.
{How to Do}
1. 1st we need flash stock recovery (if you already have, skip this point ) you can flash it via Fastboot or Flash Image GUI App
fastboot flash recovery recovery_name.zip
Link for stock recovery
you can extract stock recovery from firmware zip here
2. Stuck at Red Triangle
means stuck at OS verification stage. You have to do 2 things
verify data/preload apps
verify system
extract OTA updater-script (open with Notepad++) from OTA (Meta-inf/com/google/android/updater-script) match apk file to OS.
Getting missing files - find these apks according to your system software version Like This or fastboot getvar all
Where to find apps
Previous OTA
Guru ROM Reset
Nandriod Backup
Anyone uploaded over internet
Find a HTC One m7 same version backup apps with ES File Explorer
Restore files using Root Explorer
rename apps according to updater-script copy to phone storage copy to data/preload REBOOT.
Most apps
calculator, flashlight, Htcringtonetrimmer, HtcSoundrecorder, 7digital, soundhound, Twitter_client.apk + more
Tools
Notepad++
MD5 & SHA-1 check
If this process is boring Lengthy to you, use RUU, Guru reset rom to get stock & then flash OTA.

Don't want download OTA again or use PC downloaded OTA
Don't want download OTA again or use PC downloaded OTA
copy ota file to PC.
start downloading OTA at phone over wifi again
stop wifi at 1% ( don't cancel OTA dialog )
match file name phone storage/download/ota file to PC file rename it.
copy PC file to phone/download overwrite existing file.
resume wifi it will show download complete Start Installing.....

The correct way to flash recovery is
fastboot flash recovery nameOFrecovery.img
fastboot erase cache
fastboot reboot-bootloader
Don't skip the last 2 steps !!

[Q] Manually flashing Android 5.0 on Moto G 2nd Generation XT1068 dual sim

I tried following this link to manually install 5.0 on my device. Using a youtube video (link of video is on the image) But came across this problem the problem where i cant flash the the zip file to the phone and an error comes up saying: E: Error executing updater binary in zip ' /sdcard/download/blur version ...... i kept trying but it wouldnt work. I also tried factory reseting it and deleting all the dalvik cache, it still came back with the same response. And i have a custom recovery (twrp recovery). So what do i do?? Help me <<NEED URGENTLY>>

try to flash the rom via fastboot, using the commands on 4.2 on this thread
You need a XML zip of the rom , to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download is very slow, download, unzip, to the some folder of mfastboot and give the commands a try, while the phone is conected via USB to the PC, you must have motorola driver update, to know if you have the drivers, just plug the phone on normal on mode, and see if you can copy and past files to the phone...
If you follow this procedure you will erase everything on the phone, so do a backup...
Or find a TWRP backup of the OS you wanna and use it.

[GUIDE] Downgrade Zenfone 2 Laser to any official firmware

I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
(!less_than_int(1457089250, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Mar 4 19:00:50 CST 2016) over newer build (" + getprop("ro.build.date") + ").");
Click to expand...
Click to collapse
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold "volume down Up" button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.

Successfully downgraded to 1.16.40.763 from 1.17.40.1234 without root
Thanks!

sziraqui said:
I have discovered multiple ways of downgrading ZenFone 2 Laser out of which two methods proved out to be easy and reliable. Both methods have been tested and are working.
Method 2 doesn't require root while method 1 needs root access.
Pre-requisite: Stock firmware zip file. You can find download links from index thread for all variants.
WHILE THIS GUIDE HAS VERY LESS CHANCES OF MESSING UP YOUR DEVICE, HUMAN ERROR CAN ANYWAY HARM THE DEVICE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO ANY DEVICE. YOU ARE DOING THIS AT YOUR OWN RISK
METHOD 1: Requires ROOT-
Short instruction:
Some users say you can downgrade by renaming the OTA zip to correspond to a higher version but that will NEVER work because the update script has this line
The recovery reads ro.buid.date.utc value from buid.prop. If the value is less than the value in updater-script (like the value highligted in above quote) any recovery will not flash it, neither stock nor custom. Just increaase the value of ro.build.date.utc (in build.prop) to any value higher than the value in updater-script and then flash the zip via recovery.
Detailed Instructions:
1. Open updater-script from the firmware zip. It will be found in /META-INF/com/google/android inside the .zip
2. look at the first line (!less_than_int(1457089250, getprop("ro.bui....
3. The value 1457089250 is taken as an example, your updater-script may have a different value. Keep a note of this value.
4. Install any root file manager like ES file explorer (if you dont have already)
5. Goto /system (the system folder) using the root file manager. Grant root access if prompted
6. Open buid.prop file as text and look for the line "ro.build.date.utc=1446585430"
1446585430 is taken as example, your phone will have a different value.
7. Now increase this value in build.prop to any number greater than the value you noted from updater-script
for example, if my updater-script has 1457089250 this value and buil.prop has 1446585430 this value, I will simply change the value in build.prop to 1546585430 or 1448585430 or 1457089251. Any number greater than 1457089250 will work in my case.
8. Now reboot to recovery (vol down + power)
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Method 2: Without root, requires computer
Short instructions:
As I mentioned earlier, recovery reads "ro.build.date.utc" But you can bypass this check by erasing system partition.
Just do
Code:
fastboot erase system
from fastboot mode and then flash the zip from recovery
Detailed Instructions:
1. Install Asus drivers to your computer. (link in index thread)
2. Download adb_fastboot.zip and extract its contents
3. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after Asus logo appears and then release volume down button. Your phone is now in bootloader mode.
4. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should display "Fastboot mode!"
5. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
6. On command prompt type
Code:
fastboot devices
and hit enter
and check if it is detecting your device.
7. Then type
Code:
fastboot erase system
(this will erase your current OS, you are warned!)
8. After it is done type
Code:
fastboot oem reboot-recovery
to boot into recovery mode
9. Select "apply update from external sd card" select your firmware zip file, and then select yes to flash. It will take 5-10 min
10. (optional but recommended) Wipe factory/data . If you don't do this, you will see the annoying "Android is upgrading.." screen which takes around 30-40 mins to reach home screen.
Click to expand...
Click to collapse
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that

ThanveerAliSayed said:
Currently iam on marshmallow. My phone is zenfone laser 550kl. Iam having some problems with the marshmallow recovery because of that when doing apply update from sd card it is resulting an error.
Failed to mount/asdf.
So i like to flash the lolipop recovery while iam on the marshmallow and then do apply update from sd card. I like to go back to the 1.13 lolipop firmware
Is it possible to to flash the lolipop recovery while iam on marshmallow. If possible. Help me how to do that
Click to expand...
Click to collapse
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user

sziraqui said:
"Failed to mount /asdf" error is harmless you will get that error even on latest twrp. You can ignore the error and use the MM stock recovery like normal. Recovery will do its job it can format, install updates, clear cache and everything, you just need to ignore that /asdf error
But you can use any stock recovery from any firmware version lower than or equal to your current firmware version. Drawbacks: You cannot apply update to MM OTAs if your recovery version doesn't match the current firmware version.
Going back to stock 1.13 is a bad idea. I would recommend you to stay on MM since it has many performance improvements.
But still if you want to go back to lollipop, consider downgrading to the last lollipop update i.e. v1.17.40.1531
Xda Tips: 1. Never quote the entire OP (the main post here, called original post)
2. Don't say thanks, instead hit the :good: button
3. Use "Post Reply" option on top if you want to reply to a post. Use @username to gain attention of a user
Click to expand...
Click to collapse
I got a 412 mb ota update some days before. I downloaded it. Apply it for proceed. Then it start checking system as usual phone restarted. But update did not happened. Instead this same error show up. Then i can only reboot system. Got an update failed message.since that when i check for updates iam not even getting any. May be it will be solved by a factory reset .but even if i get an ota. The update wont proceed .because the recovery wont allow me to do that
And also that wipe cache partition also results the same error .so without solving this error i cant update to the latest MM too :/ .

In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:

where can i find the recovery file in Stock rom
4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Thanks for the Information, Can you please help to find the recovery file in Stock rom.
Click to expand...
Click to collapse

The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?

4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
Hi, I see only boot.img in the zip file. Is there a hidden recovery?

4llerbuntu said:
The recovery is included in the stock ROM zip file. Extract the zip and you will find it inside.
Presumably if you want to flash the stock ROM you have already downloaded it?
Click to expand...
Click to collapse
I see only boot.img file , i didn't find any recovery.img file, in case if you have already done this probably yes then please share us the steps to get recovery from Stock rom.

4llerbuntu said:
In my experience, the most reliable method is to
extract the recovery from the version of stock ROM you want to upgrade or downgrade to
Flash that recovery with fastboot
Wipe /system in fastboot
Reboot to recovery and update with the stock ROM .zip
Or
Even easier, use Sziraqui's fastboot ready .IMG files and just flash them via fastboot.:good:
Click to expand...
Click to collapse
I cant find any recovery.img in the firmware zip. :/
Can you detaily explain that fastboot method as it is for flashing the lolipop recovery for downgrading to 1.13.
Iam a beginner in android. This is my first android phone.

murat124 said:
Hi, I see only boot.img in the zip file. Is there a hidden recovery?
Click to expand...
Click to collapse
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa

ThanveerAliSayed said:
I found out that recovery for each firmware is available here. You should use a desktop browser to use this website.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
Click to expand...
Click to collapse
Thank you.
Can ZE551KL use the recovery.img from ZE550KL? My ZE551KL has the extra 1700(AWS) band.

Please where are you guys downloading your stock rom from?
The stock zip is NOT flash-able like a custom ROM .zip. That's not how it works. If the Roms you have are custom recovery flash-able, they are not the OEM rom, they have been modified.
All the Roms I have come with a recovery.img file...
Then again if I have to explain how to use fast boot to flash the recovery, there is a good chance you shouldn't be messing around with fast boot.......
---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------
murat124 said:
thank you.
Can ze551kl use the recovery.img from ze550kl? My ze551kl has the extra 1700(aws) band.
Click to expand...
Click to collapse
no it cannot. Do not try it

Weird ..... I can find recovery.img

Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery

ThanveerAliSayed said:
Can anyone explain me detail. How to flash recovery only. My bootloader is not unlocked. Someone said that i need to unlock bootloader to flash the stock recovery
Click to expand...
Click to collapse
You don't need to unlock bootloader for flashing stock recovery that you downloaded from the above mega drive.
To flash the recovery.img (or any .img) You need to have Adb and fastboot files in your pc as well as Asus Zenfone drivers installed
All info and downloads for adb and fastboot can be found here
Search and download Asus ZenFone 2 laser drivers.
Once you have your pc setup with these tools,
With Administrator priveleges, locate the folder where adb.exe and fastboot.exe files are present. Hold down shift key and right click on that folder and select "open command window here". Then reboot your phone to fastboot mode [power off, hold vol up +power, release power when logo appears]
Connect your device to pc.
Type the following command on cmd
Code:
fastboot devices
Output should be something like this
Code:
FCAHSJSJJAKAK fastboot
This command will check if your device is connected or not
If output is blank, device is not being detected.
To flash recovery.img, copy the recovery.img file to the same folder where fastboot.exe exists and then type
Code:
fastboot flash recovery recovery.img
Output is easy to understand, if it says [OKAY] then flashing succeeded

Tried downgrading ze551kl by fastboot erase system then installing .zip from Asus website (via sdcard). All of the Asus updates except the earliest fail with 'fota return code 403'.
1.14.40.550 installs ok but then boots (gets as far as displaying the wallpaper), gives an error message in german (looks like 'android media process stopped') and goes into boot loop. Anyone seen this before?
Also, any way to build a recovery.img from the Asus update files?

invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.

Leftrand said:
invalid boot image whenever i flashed stock recovery,any one know why ?
What i do is flash the stock recovery and flash relock bootloader.
Click to expand...
Click to collapse
I think OP needs a small correction to enter into FASTBOOT you need to press volume up and power instead of volume down and power buttons
---------- Post added at 05:45 PM ---------- Previous post was at 05:38 PM ----------

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.