yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I am on win 10 64bit also, so that should not be any problem.

I can't explain why this is happening for you, yet.

Try to manually check for fastboot connection.

Start terminal (command) and type "adb devices" make sure it shows a device , then type "adb reboot fastboot" give it about 10-20 seconds then type "fastboot devices". Make sure it shows connected to fastboot.

After that if it is connected in both checks, exit fastboot either with "fastboot reboot" or force power off by holding power button.

Make sure you are "not" running the tool as administrator.

And make sure downloaded zip is "all extracted ", there are hidden files and folders , not just the batch file.

Lastly make sure that the files are extracted somewhere that you have write privileges. Some folders on Windows system do not allow you to write into them.

***currently the log is not very helpful when there are problems, working on that this week.

**right now the files that might help troubleshoot are put into a "working" folder. That working folder needs to be cleared when the script is exited, to prevent problems the next time it is used. (even though I suspect this is a one time use tool).

New script with rough more rough logging is up on the github repo. If you want to try it and review the log to see what might be missing. It cannot tell if your drivers are working, but if certain files are not created it can help narrow it down. Also the logs copy to the log.txt file on exit, so tool must exit to copy logs.
[BLU R1 HD Guides, News, & Discussion] mutantchipmunk:
Figured out what i did wrong. I extracted the zip to a folder on my desktop with a space in the folder name. Moved it to C:\ and got rid of the space and the tool didnt crash when i chose step 3 and 4. The hidden files were there too. I manually had to put my phone into fastboot and run step 3 and 4 and i was able to get twrp installed and running. The windows mtp driver kept changing and i think that's why my phone couldnt connect via adb. But i threw the SU zip and the debloat zips on my phone and ran them in twrp so now im rooted with no ads. Didnt know my phone would reset in the process but i can get everything back. Thanks for the help.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I looked A little deeper into this. and I think I found some helpful information. It looks like once there is a problem connecting to either adb or fastboot the status is stored in memory and the way I am checking for connection always fails once it fails once. I added an "adb kill-server" command to the top of the main loop and this should clear any errors stored so once driver or connection problems are fixed it will connect again. I added this to V7 of the tool.

V7.1 is now current version, It has a fix for the FM-Radio app , no more need to have to extra "su" files added , this may have been issue to some users.
[BLU R1 HD Guides, News, & Discussion] spawn1000:
Help

good day i am running 7.4.2 on my r1HD i already have adb and fast boot installed, but when i run dirtycow (7.1) i keep getting this error when i try to execute step 1 : [W] Files pushed to phone do not match reference file. I'm a noob so i don't understand or know what to do. any help is appreciated thank you.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
this means that maybe your download is corrupt, or you did not keep the script in the same folder with the unzipped files from the download.

Run the tool again and "maximize the window of the tool. Then run number one again and compare what is on your screen to the attached photo. So we can find what file is not matched. there are 6 files that are checked, and give same message to the log.
[BLU R1 HD Guides, News, & Discussion] spawn1000:
i just ran the tool again its saying that the MD5 file isnt found. I will re download the tool to see if that helps. Thank you.

---------- Post added at 04:31 PM ---------- Previous post was at 04:19 PM ----------

Re downloaded the file and got the same error: DIRTYCOW-R1_HD-TOOL-V7.1\\WORKING\PHONE_FILE_MD5.TXT

busybox file does not match
[BLU R1 HD Guides, News, & Discussion] mrmazak:
alright, look in the /working folder. open the text file "phone_file_check.txt"

should look like this

-rwxrwxrwx shell shell 1194144 2016-11-02 15:42 busybox

-rwxrwxrwx shell shell 448 2016-11-15 14:10 cp_comands.txt

-rwxrwxrwx shell shell 130 2016-11-15 14:11 dd_comands.txt

-rwxrwxrwx shell shell 13784 2016-11-09 19:16 dirtycow

-rwxrwxrwx shell shell 18068 2016-11-15 13:29 recowvery-app_process32

-rwxrwxrwx shell shell 1048576 2016-10-30 10:31 unlock

the "phone_file_md5.txt" should look like this

18ab1955384691a35b127a3eebd6ef72 /data/local/tmp/unlock

d201fb59330cc11343452479757f6c40 /data/local/tmp/recowvery-app_process32

8259b595dbfa9cea131bd798ad4ef323 /data/local/tmp/dirtycow

28443a967a9b39215b5102573ef1731b /data/local/tmp/dd_comands.txt

df5cf88006478ad421028c58df5a55ad /data/local/tmp/cp_comands.txt

b5eec83df6dd57902a857f6c542e793e /data/local/tmp/busybox

next clue will be to look at top portion of the screen-shot i put up before. it lists files transferred to phone, yours should be the same.

note the /working folder is cleared when you exit the tool so if it is empty , run step one again but do not exit the tool. And the folder is set to be "hidden" you will need to show hidden folders to see it.
[BLU R1 HD Guides, News, & Discussion] spawn1000:
I opened the file as you said

and nothing matches

the phone file md5 has :

/system/bin/sh: /data/local/tmp/busybox: not found

/system/bin/sh: /data/local/tmp/busybox: not found

/system/bin/sh: /data/local/tmp/busybox: not found

/system/bin/sh: /data/local/tmp/busybox: not found

/system/bin/sh: /data/local/tmp/busybox: not found

/system/bin/sh: /data/local/tmp/busybox: not found

and the phone check file is blank

i downloaded version 7 and tried it too see if it would make a difference but it was the same.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I just did a little test and can get failed results , if I unzip to a folder with spaces in the name, or even is the user's home folder has spaces.

so make sure the path to the tool has no folders with spaces in the name.

. example extract the zip to "c:\dirty-cow" not "c:\dirty cow"

I will try to change the code to allow spaces, for V8
[BLU R1 HD Guides, News, & Discussion] spawn1000:
i moved the folder to the C drive and steps 1 and 2 worked but step 3 failed.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
what do you mean failed..

What is the display from tool say,?

What is in the log?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
V8 is up now.

it fixes the problems that come from unzipping the tool to a location with spaces in the name.

It also waits longer during the dirtycow part. I noticed on my test phone running V17 that the time needed to spawn the shell varies. sometimes it took 35 seconds sometimes it can take 2 minutes 30 seconds, so i increased the wait time.

and made some of the commands in the root shell text file doubled, just in case.
[BLU R1 HD Guides, News, & Discussion] spawn1000:
I now saw this reply. I will download V8 and retry this another day. Thank you so much for your help thus far. I will let you know if everything works out.
[BLU R1 HD Guides, News, & Discussion] Huchman1:
Thank You!

Is there a preferred way to block OTA? Is it even necessary if you do tha Amazon debloat? :good:
[BLU R1 HD Guides, News, & Discussion] mrmazak:
the amazon debloat should have blocked the ota.

It renames the "fota" program so it is not found
[BLU R1 HD Guides, News, & Discussion] spawn1000:
I tried V8 this time and still no luck with the bootloader unfortunately
[BLU R1 HD Guides, News, & Discussion] mrmazak:
looking into that, now.

I changed the quotes on the find string along with the push lines. Maybe it left syntax incorrect. It worked on my test phone though. --- seems to be correct---

update.

I was able to get the error you had if the "unlockability.txt" file was blank, Or missing the line that is being searched for.

so for some reason the file is not being created correctly

what is the list of files inside the "working" folder at the point it is failing?

so far my tests show:

1: if file does not exist there will be an error message saying so. Your ouput did not show file not found , so the text file is there just not as expected.

2: if unlockability.txt has a "0" , which means "un-lockable" script will tell you un-lockable like is should

3: have not found scenario that makes the text file differently, but that is what i suspect is happening.

please let me know what the text file "unlockability.txt" has in it.
[BLU R1 HD Guides, News, & Discussion] sinsforeal:
Issues with step 3

At step three my phone reboots when I initiate boot loader unlock and it says no adb connected devices. Or it will start but it will then fail after the second count down putting my device in fast boot mode which I have to hold the power button to exit. Please help a noob out I have read through some of this thread and people with similar problems have some confusing solutions.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
It is supposed to be rebooting to fastboot mode. And you are not getting "found fastboot" message so your drivers are not setup correct.
[BLU R1 HD Guides, News, & Discussion] sinsforeal:
I tried both download versions of the drivers but it still can't find the device and the phone still says fast boot mode, Any suggestions?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
not sure, what both versions you mean.

Did you install the recomended adb+fastboot from the op?
[BLU R1 HD Guides, News, & Discussion] sinsforeal:
Yes it was the current version and the 1.3 version of the recommended fast boot in the link

Mon 03/13/2017 18:51:54.18 [E] No fastboot device detected.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Gonna have to open device manager and find the phone when connected in fastboot mode and update driver
[BLU R1 HD Guides, News, & Discussion] sinsforeal:
So far so good now I will install the ones I want from 5.

---------- Post added at 01:23 AM ---------- Previous post was at 12:41 AM ----------

Also is it safe to go to 6.6 when I am completely finished with everything?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I wouldn't recommend to do that. The whole purpose of this tool was to fix the ability to unlock and root this phone. Things that 6.6 block. So no, don't to go 6.6, unless you mean the modified version from in the XDA forum. But really 7.4.2 and 17 are newer and more upto date.
[BLU R1 HD Guides, News, & Discussion] sinsforeal:
Also another issue. It can't find the recovery when I try to use super su flash it says null device not found yet I have it loaded up on my phone the recovery menu
[BLU R1 HD Guides, News, & Discussion] mrmazak:
on the twrp recovery did you swipe to allow modification and then reboot recovery. then reboot to android again. before trying the su flash?

if you don' t reboot to recovery and allow the modification I have seen adb fail to connect to recovery. also sometimes if there are no files already in the "Download" folder , I have seen differing problems pushing to that folder. I think i will change the push to location lines to try and improve stability. In the mean time you can try to push files to phone through "mtp". (phone should show on your pc a a device you can use as portable storage.
[BLU R1 HD Guides, News, & Discussion] sinsforeal:
omg thank u so much do u have a paypal?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I made a test script to help find problem on your process.

attached is just the verification lines that seem to be failing for you. Please let me know the output from it.

rename the .txt file to a .bat so it can run

This batch file will (supposed to) create a new txt file in same folder that you save the batch file to.
[BLU R1 HD Guides, News, & Discussion] Agielx:
Working great!

Great job, I rooted my R1 HD V7.4.2 16/2gb prime version using this, and removed the ads with the partial debloat, anyone can use it following the instructions. Be aware if you use a download manager to get the files, I use jdownloader2, and the autoextraction feature of this unzipped some files it didn't shouldn't be unzipped.
[BLU R1 HD Guides, News, & Discussion] drashu:
Work in 7.4.2?

i have a blu r1 hd prime version 1gb/8gb 7.4.2

the tool really works? for root
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I didn't test with the 8 gb verson , but it should.

Just finished some troubleshooting with user having trouble with the version of fastboot. So now there is a V 9 available.
[BLU R1 HD Guides, News, & Discussion] spawn1000:
This worked on my phone thank you very much! Used V9 on 7.4.2 2/16GB version!
[BLU R1 HD Guides, News, & Discussion] gsaltar:
All I have to say is THANK YOU VERY MUCH [MENTION=5312578]mrmazak[/MENTION]! It worked and it is great! Please keep up the good work!
[BLU R1 HD Guides, News, & Discussion] drashu:
Questions

I will try the weekend, when unlocking the bootloader factory reset the phone? Is there any risk of brick? Does the AMZ Debloat option work to remove ads?
[BLU R1 HD Guides, News, & Discussion] AIDAROUZE:
unlook tool

I thing I got problem with adb driver, I cant go further than step 4,phone stuck in fastboot, I need help to figure out please.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
kind of working blind here.

ADB is used on step 1-3 so not thinking it is adb driver. Step three also uses fastboot so if that finished not sure is is fastboot driver.

So can't go further that step 4 , does that mean step 4 finished or no?

Stuck in fastboot ? Are you at the point that has note on screen that says

ONCE THE FILE TRANSFER IS COMPLETE HOLD VOLUME UP AND PRESS ANY KEY ON PC

IF PHONE DOES NOT REBOOT THEN HOLD VOLUME UP AND POWER UNTILL IT DOES

ON PHONE SELECT RECOVERY FROM BOOT MENU WITH VOLUME KEY THEN SELECT WITH POWER
[BLU R1 HD Guides, News, & Discussion] inahas@gmail.com:
Thank you so much! I finally rooted my BLU R1 v6.6 successfully. Here are some notes that might be of help to others having issues.

I couldn't download the linked files from here (keep getting 'no mirrors found' error) so I downloaded the source from Github. I ran the 'one-click-root.bat' batch file and went through the process. It took me a couple of times but I finally got TWRP installed and running. From that point I followed the steps in this video www-youtube-com/watch?v=KMobKWfZbJg (starting at 5:00) (Sorry, not allowed to post links)

I downloaded SuperSu from supersu.com website and installed it from TWRP as instructed in the video.

Now my phone is rooted but I wasn't sure how to debloat it and remove Amazon ads. I saw some several zip files in the /pushed directory that looked relevant. I copied the bluR1-AMZ-FULLdebloat-blockOTA_v2.zip file on the phone, then went back into TWRP and installed the app from there. Ads Gone!
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Good to hear.

FYI. There is two download sources. The links in op to android-file-host and also there is a download tab on the top of every page of this thread hosted here on XDA.

Also the GitHub has the current unlock-tool.bat.
[BLU R1 HD Guides, News, & Discussion] whosthisdude:
I must be missing something...

I just got my HD1 today and running into the following issue...

I can see the device via `adb devices`

I can reboot the device into bootloader and see it via `fastboot devices`

However, when I run the provided .bat I get "Not BLU_R1_HD device"

After looking in the code I ran the following command: `adb shell getprop ro.build.product`

for which I get `R1_HD`

This is not expected per the code which is apparently looking for `p6601 BLU_R1_HD`

I've been trying for hours to get this thing unlocked :eek:
[BLU R1 HD Guides, News, & Discussion] whosthisdude:
I was able to solve my own problem by removing the entire product check at the start of the bat. I also removed the ADB daemon restarts. Now my HD1 is rooted and TWRP is installed :cool:
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Yeah they have changed the product name. I have three and they are all "BLU_R1_HD" and the p6601 I used because that's the name in the lineage14 that is built.

Good to hear you got past that. I think I should edit the script again.

This might be the final one, seems like it might be the last bug in the tool.
[BLU R1 HD Guides, News, & Discussion] L_123:
I'm new fam.. I've been jumping through threads for a day now trying to work out what, or how, I can go about putting a custom or stock OEM rom on my R1 HD (prime version). Ultimately I'd like to get rid of the bloatware and ads.

I'm a bit of a newb and I'm really trying hard to solve this stuff.

I have the ota update 7.4.2 and I've got ADB and fastboot good to go on my PC (after final solving device showing up offline on ADB).

Thing is I have no idea where to start/go to get to my end goal.

Does one just follow this guide? Where can I find the drivers referenced to make this work? Do I root/twrp/unlock bootloader first?

I'm sorry this sounds dumb and you might be thinking I can work this out easily but going through the guides on here are clearly for people in the know already and everything with a step by step (rootjunky vids) scripts don't seem to work or I might be doing it wrong.

Any help or guidance will be greatly appreciated.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Yes just follow the steps in the tool.

it was made to be able to be used by most newbie.

drivers mentioned are also linked in the op right where they are mentioned. But if adb and fastboot working you should be all set.
[BLU R1 HD Guides, News, & Discussion] hdrums:
Hi everyone... I am trying to do the unlock-root method on my R1 HD, my version is 6.6... I installed the drivers, adb and fastboot but in the process when the phone is on in normal mode it recognizes it with command " adb devices " but after it enters fastboot mode when I enter command "adb devices" it does not appear anymore .. I don't know if this is so, when I start the tool and select option 1 indicates that there are no adb devices connected, what could it be? I have tried several times with the same result. regards

note

: I am in windows 7 a modified ligh.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I'm confused a little on what you are explaining.

Of course "adb devices" will not show connected device when phone is in fastboot mode. That's where you need "fastboot devices" to check for device connectivity

You need to start the tool with phone on in normal mode with adb available.
[BLU R1 HD Guides, News, & Discussion] hdrums:
Oh I see haha, I was confused by the txt of the instructions I was running the tool dirtycow-tool.bat immediately after verifying that fastboot works, don't reboot, I am a little noob on this and I was translating (I don't speak English). which version of the tool do you recommend? My R1 is V6.6. Thank you.

[IMG="Instructions txt"]https://i.imgur.com/sRiVSYi.png[/IMG]
[BLU R1 HD Guides, News, & Discussion] mrmazak:
V10 is newest version
[BLU R1 HD Guides, News, & Discussion] L_123:
I guess I'm a super noob.

puu.sh /v1SpR/ c45fc0a323 .png

After following the instructions in the tool-v10 zip txt ~ check to see if adb and fastboot work, and they do ~ then when I run the dirty-cow-tool bat file I get what you can see there.

What have I done wrong here? And sorry but are you saying the required drivers are included in this v10 tool download?

---------- Post added at 04:41 AM ---------- Previous post was at 04:17 AM ----------

Seems this is the same problem that I'm having but I dont think I'm in the know enough to figure out which lines of the .bat to remove. any help would be greatly appreciated.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I already made a note about this in the OP. it is listed right in the change log area
[BLU R1 HD Guides, News, & Discussion] L_123:
YAY! Got it done at last. Sorry for being a bulk noob.

Ahh I think that script change is missing a couple '/', adding them made it work for me.

So I backup'd an image in TWRP and saved it on the phone before debloating the phone (no more google/amazon filler!!!).

I wanted to ask just one last think MrMazak; what sort of care do I need to take from this point on? No more updates from android? is there anything I need to do with regards to SuperSU/TWRP?

Thank you so much for this product you've created and the diligent assistance you've given myself and many others in this thread.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
that strang. I copied and pasted those changes from my master script. I dont know why the "/" are missing.

right, no taking "ota" updates. The debloat you did should have blocked anyway.
[BLU R1 HD Guides, News, & Discussion] Royjuanka:
i dont know how to do it

I have a blu r1 hd with bloatware , what i have to do? I mean i have the adb and the files, but i scared that in the middle of the process , the phone will brick, and the sp flashtool is blocked, my version is 7,4,2 what cons do i have???
[BLU R1 HD Guides, News, & Discussion] mrmazak:
If you are scared of make a brick, then don't do any thing.

I mean it's your choice to do or not to do any modifications. As with all software mods there is risk. Very rare on this device has there been a brick that did not come back, once bootloader has been unlocked.

Your question, is "what do I have to do?"

Nobody

can answer that question.

It is too vague.

Because you posted in this "unlock tool" thread I assume you mean to use the tool. But I do not want to assume.

But if your intention is to use the tool , then my answer is read the first post every thing you need to know is there.simple 1,2,3 directions
[BLU R1 HD Guides, News, & Discussion] xike17:
Thank you [MENTION=5312578]mrmazak[/MENTION], I was able to unlock and remove the bloatware and ads. However, I can't make phone calls. I used FreedomPop SIM. I was able to make phone calls before unlocking the phone. I also tried Google Handouts but couldn't make calls either. Then I used the same Google Voice account on iPhone. Calls made in Handouts on the iPhone worked just fine. Any suggestion to fix this?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I have not idea about what you have going on. This unlock method has been used for 9 going on 10 months and this is a first time problem.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Doesn't sound like an unlocking problem, sounds like so called bloatware and ads removal.

Just restore your backup, or flash another rom, this time be careful what you remove.

Sometimes leaving the bloatware is better than having a phone that doesn't work correctly.
[BLU R1 HD Guides, News, & Discussion] xike17:
De-bloated the phone. Outgoing and incoming calls worked fine again. Lock screen and notification ads gone as well, is this supposed to happen? By all means, I like them gone. Just thought de-bloat would bring them back. Also tried two times to fully de-bloat Amazon, while the ads were gone, the apps stayed. Thanks, anyway!
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I was just pointing out unlocking device didn't cause your problems.
[BLU R1 HD Guides, News, & Discussion] xike17:
I agreed. Just providing some feedback on de-bloating the phone. Might be an isolated case to me, though.
[BLU R1 HD Guides, News, & Discussion] diavel:
In cmd prompt my phone is recognized and I was able to boot phone into fastboot mode but...

"THEN CHECK FOR CONNECTION WITH "fastboot devices", IF THIS SHOWS

CONNECTED THEN YOU CAN CONTINUE TO USE THE TOOL" <---nothing happened. "IF THIS SHOWS CONNECTED" nope I got nothing. I have fastboot installed, I checked twice.

I have 7.4.2 firmware 16GB version just received from Amazon.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Try the drivers mentioned in this thread and then try to manually update the drivers for fastboot as described in same thread.

https://xdaforums.com/r1-hd/help/actually-drivers-to-root-device-t3586351
[BLU R1 HD Guides, News, & Discussion] diavel:
Thanks for reply. I got now fastboot on cmd prompt.

But upon starting dirty cow tool, it shows

"device (null) not found

ECHO is off"