yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] mrmazak:
At this point I suggest redoing the twrp install part, but choose the option 2 recovery (lopestom) and same way hold volume and power. to reboot.

then swipe to allow modification. then reboot from the menu in twrp. once phone fully booted up . bo another reboot and hold volume again to enter into recovery and see if it has "stuck"

if so reboot one more time and flash su

attached photo is what you should see. See the installing zip location.
[BLU R1 HD Guides, News, & Discussion] gabriel986:
the recovery just doesn't stuck
[BLU R1 HD Guides, News, & Discussion] mrmazak:
is this a new phone?

did you complete the unlock step?

if you did, did the stock recovery finish its factory reset?

what version rom is on it?

did you encrypt the phone before?

your phone not responding like the rest means lots of unanswered questions.
[BLU R1 HD Guides, News, & Discussion] gabriel986:
I got it last week.

It's running on BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38

No encryption.
[BLU R1 HD Guides, News, & Discussion] Zafy29:
works on v9.2

worked on my BLU R1 HD :good:

followed instructions, did all steps but some of them (like step 4 - TWRP ) didnt work at first time but second worked. I dont remember which other needed to be repeated, but worked for me.

Also step 5 option 1 (root) and option 2 (amz full debloat) worked for me too.

So now I have my R1 with bootloader unlocked (confirmed with fastboot) and root access. :)

my version: BLU_R0010UU_v9.2_GENERIC.

Thanks :good::good::good:
[BLU R1 HD Guides, News, & Discussion] luisfcova:
You are muy hero!

Amazing work dude you are awesome now i have a rooted Blu R1 hd with Xposed. Question where is located the bootlogo? (i don't like the Blu original splash)
[BLU R1 HD Guides, News, & Discussion] Alter baruch:
help

im on v9.2 and whenever i try to "run dirtycow" it fails and says "new_frp_md5 does not match" someone plz help

---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------

what version of dirty cow did you use?
[BLU R1 HD Guides, News, & Discussion] Alexander machado:
Hola que tal foro??? Alguien sabe cómo actualizar el Android del Blu R1 HD al 7.0
[BLU R1 HD Guides, News, & Discussion] sctanf:
On v9.2, mtk-su worked, thanks!
[BLU R1 HD Guides, News, & Discussion] miker1111769:
Were these files are hosted is god awful slow, took 15 minutes to download a 45 mb file, and it's saying over a day for the 1gb twrp.. on a network that has speed up to 2.5Mbs
[BLU R1 HD Guides, News, & Discussion] joedajoester:
How is everybody getting fastboot to recognize their phone? Ive tried installing a couple mtk drivers and nothing works. ive tried two windows devices and linux and none are able to see my r1 hd in fastboot mode, or adb.....
[BLU R1 HD Guides, News, & Discussion] mrmazak:
oh f***

thats 8gb phone ?

R0011uu is the 16gb.

you need different recovery
[BLU R1 HD Guides, News, & Discussion] gabriel986:
It's the 16gb ROM and 2gb RAM version
[BLU R1 HD Guides, News, & Discussion] mrmazak:
i am guessing the unlock did not fully finish. or did not do full data format. can you put phone into fastboot mode either by button combo, or "adb reboot bootloader".

then open cmd window on pc . enter these commands to clear data and cache.

1. "fastboot oem unlock"

on phone you need to confirm this with volume up button

2. "fastboot format userdata"

3. "fastboot format cache"

then reboot phone and allow it to run through setup. no need to sign into anything. you can skip wifi , google , amazon, all of them

turn developer options on again

reboot once more.

then try to run tool again and install recovery
[BLU R1 HD Guides, News, & Discussion] gabriel986:
Done....

The recovery refuses to stick
[BLU R1 HD Guides, News, & Discussion] mrmazak:
the only time I had the recovery give those failed to mount errors was when the unlock was done without the stock recovery installed to do a factory reset.

maybe twrp was installed too soon , and this is caused a problem.

you said the twrp does not stay. So try to do factory reset with stock recovery, then

manually try to "fastboot boot recovery.img"

and see if it has the mount errors or not.

you can check that by the bottom right button in twrp screen.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I have confidence that I know what happened, now.

You have phone that does not accecpt the "fastboot reboot" command. Because it is the updated version.

the last line in the unlock section is "fastboot reboot"

And then it returns to the tool menu. Because the phone did not reboot is did not really finish the unlock.

Then the next step of installing twrp did in bad.

and stock recovery keeps getting restored , if you try using the tool to run unlock again(it will fail because it will check and say already unlocked) .

I suggested you run the commands again but maybe should not have had you do the format.

do just the "fastboot oem unlock"

when done hold power button till it turns off. then turn it back on.

The expected thing to happen is that when it comes on it will loop 2 times into stock recovery, flash to the android on its back (doing reset)

then if that goes well, should be able to continue.
[BLU R1 HD Guides, News, & Discussion] gianlucaos:
I tried running this on Windows 10 on Parallels (from Mac Osx), connecting the R1 HD over USB but I get an error "no adb connected devices...". I must have done something wrong with the drivers.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Im not familiar exactly with mac or parralells, but use virtual box on windows host. And know that in order to get usb connections in the vm you need "filters" set so the host (mac in your case) passes to connection the virtual machine.

Could it be that simple?

not sure why your not just doing it native on the mac

adb and fastboot are available. aren't they.

here is first result in seach I did for "adb+fastbook mac" its very old thread. there may be newer guide out there.

https://xdaforums.com/showthread.php?t=1917237
[BLU R1 HD Guides, News, & Discussion] gianlucaos:
Oh, wait, I had no idea I could do it on my mac. What do I need to do to root the R1 HD on mac then? I have no experience with android.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I might be mistaken but dont linux .sh scripts work same way on mac?
[BLU R1 HD Guides, News, & Discussion] gianlucaos:
Thanks for the quick replies mrmazak. I have no clue about that. I'll look into it later. I would love to hear from other Mac users if they were able to root the R1 HD with this tool or through some other way. I have struggled to find any info about rooting the R1 HD on Mac.

I have always used iPhones, last year I tried the Jailbreak and all, and after hearing about rooting and seeing Bluestacks, recently I decided to check out an Android phone, so I picked this up from Amazon, to explore the Android system.

Now, back to the problem.

I noticed that my Mac doesn't even mount the device.

I might try with another cable, to see if that's the problem, but there might be something else.

I have tried to root this device through Parallels, with Windows and Ubuntu, but there's been always something wrong (Windows doesn't recognize my device, I can't find the drivers or how to install them, Ubuntu can't connect to the internet to download them), that I need to figure out if I want to take that path.

If I go with the virtualization way, I might try with Virtual Box. I have had some experience with it in the past, I had used it for quite a while to virtualize windows 7. Parallels is giving me headaches with the internet connection sharing between my mac and the virtualized machine.

I have also tried setting up a USB to boot Ubuntu from it as a live version, but it didn't run.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
the other user was long before I wrote the tool, but the tool really just seperates the same script that was written befoe, that he did use so , i will reasch out to him.

Edit:

What I have come up with on this subject of using the script on Mac.

The script should work no problem itself. The problem is that on a mac, apparently permissions for a script to access adb and fastboot is touchy.

So in a terminal you may be able to do all the steps, bit in a script it may not.

The suggestion I was told is that if getting adb to "play nice" is a problem it might be better for you to use parallels.
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
I have absolutely no clue what i'm doing.

When I try step 1 on the bat file, it says no adb device connected. What do I do?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
First step is listed above downloads and use instructions on first page. Says to I stall adb and fastboot with drivers. There is a link.

It's a quick simple install, bit needs to be run as administrator.

Then on phone need to enable developers options. And adb debugging.

With drivers installed and debugging turned on, try again. Look for a "pop-up" message on the phone asking to allow connection to pc.

This developer options and debugging and allow connection step needs to be completed again after the unlock step before the install twrp step.

I think that should cover it
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Thanks so much mate, but after step 5, I got this error

Found ADB

failed to copy 'pushed/UPDATE-SuperSU-v2.76-20160630161323.zip' to '/sdcard/Download': No such file or directory

/system/bin/sh: /sbin: can't execute: Permission denied

/system/bin/sh: recovery: not found

Press any key to continue . . .

What should I do no now?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
OK need to know if twrp has installed good.

You did do steps 1-4 right.

It is important that phone reboots in between step 3 and 4.
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Ah. Alright, I think step 3 might have gone wrong. I had to mannualy reboot after the transfering.

Should I try step 3 again?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
need to see what is in the file "working\getvar.txt"

and "working\unlockability.txt"

in the folder that was unzipped. need to show hidden files and folders.

you can also just do a search in that folder for the file name

also when you forced it to reboot did you get the android lying on his back screen?
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Alright. Getvar.txtx

(bootloader)	max-download-size: 0x8000000

(bootloader)	partition-size:flashinfo: 1000000

(bootloader)	partition-type:flashinfo: raw data

(bootloader)	partition-size:userdata: 32000000

(bootloader)	partition-type:userdata: ext4

(bootloader)	partition-size:cache: 19000000

(bootloader)	partition-type:cache: ext4

(bootloader)	partition-size:system: a7000000

(bootloader)	partition-type:system: ext4

(bootloader)	partition-size:metadata: 2500000

(bootloader)	partition-type:metadata: raw data

(bootloader)	partition-size:nvdata: 2000000

(bootloader)	partition-type:nvdata: ext4

(bootloader)	partition-size:frp: 100000

(bootloader)	partition-type:frp: raw data

(bootloader)	partition-size:tee2: 500000

(bootloader)	partition-type:tee2: raw data

(bootloader)	partition-size:tee1: 500000

(bootloader)	partition-type:tee1: raw data

(bootloader)	partition-size:keystore: 800000

(bootloader)	partition-type:keystore: raw data

(bootloader)	partition-size:secro: 600000

(bootloader)	partition-type:secro: raw data

(bootloader)	partition-size:oemkeystore: 200000

(bootloader)	partition-type:oemkeystore: raw data

(bootloader)	partition-size:seccfg: 80000

(bootloader)	partition-type:seccfg: raw data

(bootloader)	partition-size:expdb: a00000

(bootloader)	partition-type:expdb: raw data

(bootloader)	partition-size:logo: 800000

(bootloader)	partition-type:logo: raw data

(bootloader)	partition-size:recovery: 1000000

(bootloader)	partition-type:recovery: raw data

(bootloader)	partition-size:boot: 1000000

(bootloader)	partition-type:boot: raw data

(bootloader)	partition-size:para: 80000

(bootloader)	partition-type:para: raw data

(bootloader)	partition-size:lk: 80000

(bootloader)	partition-type:lk: raw data

(bootloader)	partition-size:protect2: a00000

(bootloader)	partition-type:protect2: ext4

(bootloader)	partition-size:protect1: a00000

(bootloader)	partition-type:protect1: ext4

(bootloader)	partition-size:nvram: 500000

(bootloader)	partition-type:nvram: raw data

(bootloader)	partition-size:proinfo: 300000

(bootloader)	partition-type:proinfo: raw data

(bootloader)	partition-size:preloader: 40000

(bootloader)	partition-type:preloader: raw data

(bootloader)	off-mode-charge: 1

(bootloader)	warranty: no

(bootloader)	unlocked: yes

(bootloader)	secure: no

(bootloader)	kernel: lk

(bootloader)	product: P6601

(bootloader)	version-preloader: 0.1.00

(bootloader)	version: 0.5

all: Done!!

finished. total time: 0.005s

And Unlockability.txt

...

(bootloader) unlock_ability = 16777216

OKAY [ 0.007s]

finished. total time: 0.007s
[BLU R1 HD Guides, News, & Discussion] mrmazak:
looks like i expected it .

what about when it rebooted did you have the android on his back doing a factory reset?

that is what I am expecting is causing trouble, if it did not happen
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Ummmm,The dead android guy on his back with his belly open? Yes that happened.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
ok all that is what i expect. now what about when you reboot to recovery?

not with the tool

just power off phone and hold volume up while powering on, then select recovery.

then in recovery screen if it is twrp push buttin in lower right corner. the stacked line. If there are errors with the recovery they should be listed there
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
When I try recovery mode all that happens is the dead android guy appears on a black screen, and then it reboots.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
ok twrp did not install . this makes two that do not work.

lets try manually install

in folder that tool is unpacked in

press "alt + shift +right click"

choose option to "open command window here"

type "adb devices"

verify is shows a device

type "adb reboot bootloader"

type "fastboot devices"

verify it has a device

type "fastboot flash recovery pushed\recovery.img"

look for completion

then press and hold power and volume up ( for me int was 11 seconds) till screen goes off

keep holding volume let go of power

the keep holding volume and hold power ( for me it was 7 seconds) till screen come on

choose recovery

should be twrp

swipe to allow modification

then choose reboot - recovery
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
When you say look for completion, what do you mean? The prompt just says waiting for device.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
that means its not seeing the phone in fastboot mode.

I miss- typed it the fist time, and edited the post

did you do "adb reboot fastboot" that was wrong it needs to be "adb reboot bootloader"

this puts phone into fastboot mode. Screen is mostly black and in bottom corner it says fastboot mode
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Alright. Done.

Now Do I Just Move on back to step 5?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
No check it one more time

Reboot into android then again to recovery
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Working fine I think. It's on the TWRP Recovery menu again
[BLU R1 HD Guides, News, & Discussion] mrmazak:
this strange its like needed to be done multiple times. I dont know .

yes now try to continue with the supersu part now
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
So now on the supersu, after running it for a while it just says Found adb. The phone is on the TWRP recovery menu.

Do I have to press something on the recovery menu?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
should not have to. it was supposed to have been in android system when started. then is was supposed to reboot to recovery and automaticly install then reboot back to android

edit I was affraid of this .

I think the two recoveries have different commands that they need to do this.

I am running a test right now hold on
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
It does not seem to be doing anything...
[BLU R1 HD Guides, News, & Discussion] mrmazak:
yep.

the automatic part ,the way it is written seems to only work in vampirefo 's version, the other one needs a different format.

your options are

1. the supersu is alreadtyon the phone in the download folder, so you can press install and navigate to "update-supersu-..........."

2. go back to the tool now that recovery is sticking and install the other one (it is set as default), then use the tool.

this method makes sense if you are gonna do the other debloats.
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
So, uh, on the tool, which step do I need to go back to for the other one
[BLU R1 HD Guides, News, & Discussion] mrmazak:
step 4 "twrp"

it is working for both recoveries now. But something about the way I have the script "wait-for-device" is hanging the script. I need to change it to timeout instead maybe, but of course that will have its own problems too.

Ok pushing yet another version. This one has redundent flashing commands for recovery. and also a manual pause that waits for user confirmation that recovery has booted before trying to start a recovery flash. I ran multiple times in both recoveries.

Still cant see why you and [MENTION=4931076]gabriel986[/MENTION] had issue that recovery did not stick. but adding manual instructions , got it to flash.
[BLU R1 HD Guides, News, & Discussion] xblindeye:
when i click do bootloader unlock my phone goes black and says "FASTBOOT Mode..." and the program no longer recognizes my phone on my computer, what do i do?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Dis you set up drivers first?, Before starting.

The unlock part is supposed to reboot into fastboot, but if you don't have the drivers installed it cannot continue.

From this point, to get out of fastboot, just press and hold power button. To turn off, then again to turn back on I to normal boot

If you left phone in fastboot since your post, then the battery is gonna be 100% dead.

Battery drain is faster in this mode and does not charge

Now you should install the drivers. There is a link in o.p. for adb+fastboot with drivers.
[BLU R1 HD Guides, News, & Discussion] xblindeye:
I already installed those drivers all successfully had no problems with that but it still isnt working? I didnt leave it in fastboot either i shut the phone off, not sure why its doing this
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Need to put phone into fastboot mode and check device manager for devices with warning "triangle"

And update driver , the fastboot setup puts drivers into the windows drive store, but if phone was set up before with different driver maybe it just needs to be updated
[BLU R1 HD Guides, News, & Discussion] xblindeye:
error:device unauthorized

this adbd's$ADB_VENDOR_KEYS is not set; try 'adb kill-server'

i get this while trying to root
[BLU R1 HD Guides, News, & Discussion] mrmazak:
There should be a "pop-up" message on the phone asking g for permission to connect to adb.

You need to allow it.

If you do not have the pop-up go into developer options and turn debugging g off and back on. With computer connected

Wait;:

I'm confused a little. You are having common beginner problems but in "reverse" order.

Your first problem was could not detect fastboot mode, and to get to that point adb had to have been working.

But now adb is not working.?

Now if you finished the unlock part , that part does a factory reset, so maybe that is why you had the second error, but after the reset you would have had to turn debugging on. which should have reset the request for authority anyway.
[BLU R1 HD Guides, News, & Discussion] Mighty_Warthog1:
Hey mrmazak, when flashing supersu on the latest dirtycow, I get this far but it just stays there and does nothing.. What should I do?

Found ADB

"press any button when recovery has fully loaded"

Press any key to continue . . .

8832 KB/s (4973493 bytes in 0.549s)

/sbin/sh: /sbin: Permission denied

BOARD_HAS_NO_REAL_SDCARD := true

TW_NO_REBOOT_BOOTLOADER := true

RECOVERY_SDCARD_ON_DATA := true

I:Lun file '/sys/devices/msm_dwc3/f9200000.dwc3/gadget/lun0/file' does not exist, USB storage mode disabled

TW_HAS_DOWNLOAD_MODE := true

TW_INCLUDE_CRYPTO := true

I:TW_BRIGHTNESS_PATH := /sys/devices/mdp.0/qcom,mdss_fb_primary.190/leds/lcd-backlight/brightness

I:Specified brightness file '/sys/devices/mdp.0/qcom,mdss_fb_primary.190/leds/lcd-backlight/brightness' not found.

I:Find_File: Error opening '/sys/class/backlight'

I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'

I:TWFunc::Set_Brightness: Setting brightness control to 162

I:LANG: en

Edit: Nevermind mate, I manualy installed it through TWRP.

Again, mate, Thanks for evreything.
[MENTION=5312578]mrmazak[/MENTION], your a true inspiration.

Thank you. :D
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Thanks for the feedback. I have tried but cannot repeat your errors.

Shows permission denied -- I got rid of that error by replaceing the lines "/sbin;recovery" with "/sbin/recovery"

but my tests showed it worked both ways in both recoveries. I went back and tried both recoveries , just made an error with the "new line" symbol, instead of a path .

Each time I got that message was when the recovery session has started and was running the "install".zip

I'm gonna try to ignore the wait comment and try to start the command too soon and see if that creates the error, will post results.

ok if i start too soon (before recovery is ready) it just fails to push the file and ends the process, goes back to the menu on the tool.

Also your recovery text is different from what I get .

Mine shows "device ID" and "product model"

look at your output log , it shows "qcom" in the "brightness" string. so you are on the lopestom recovery

that string information comes from the recovery.

here is the output I have from vampirefo recovery

Found ADB
"press any button when recovery has fully loaded"
Press any key to continue . . .
130 KB/s (5541 bytes in 0.041s)
/sbin/sh: /sbin: Permission denied
I:=> product model: 'p6601'
I:=> using device id: 'p6601'
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/mt_usb/musb-hdrc.0.auto/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
debloat scripts curtesy of emc2cube
Press any key to continue . . .

this was from one of the debloat options, but that should not matter.
[BLU R1 HD Guides, News, & Discussion] nelomen:
I just got two of these phones for my daughters and I'm trying to remove the ads, I've used the recowvery method before for my V20 so I'm somewhat familiar with the process. I am having problems from the beginning with this walk through because the first zip file link says the file is no longer there. Is there somewhere else I can download it?

(never mind, found the files)

Works great. Now my daughters don't have to have those annoying adds.
[BLU R1 HD Guides, News, & Discussion] mutantchipmunk:
Having the same issue here and cant find a resolution. I have the default windows mtp device drivers installed, and also installed the 15sec fastboot mentioned in the op. Getting debug to pop up on the phone is the hard part, i will have to kill and start the adb server, hit ok on my phone to allow permission a few times to do one of the steps. I was able to do step 1 and 2 but when i get the adb to work and when i hit step 3 the device goes into fastboot the dirty cow tool crashes, i relaunch the tool and in cmd text comes up and a message flashes that says fastboot and some other stuff and crashes again. I'm on Win10 x64 and unable to continue. While in fastboot i see "android bootloader interface" under "TP-Link Android Phone" tree in device manager.