yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
I messed up.

Hello, I have a small problem. My R1 was originally on ColtonDRGs stock oem flashed via SPFT, vamps original twrp and it seemed to have updated to one of the later poison Amazon OEM roms with preloader botched.

I did some housecleaning involving factory reset. Failed attempt at running dirtycow exploit, and finally installing 8.4 OEM patched via twrp.

I promptly installed fm radio patch, downgraded preloader (unlocked bootloader from menu) and rooted using super su all in the same zip queue.

At the end of the day I have old preloader back, but I can't boot anything.

I then installed Colton's original v17 system, boot and recovery.img and I'm still bootlooping.

I have access to:- volume up and fastboot.

Recovery doesn't boot, nor does system.

Some important data is on the user partition.

Please send help.

I was doing housecleaning which involved factory reset, I
[BLU R1 HD Guides, News, & Discussion] mrmazak:
You should only do the preloar step by itself. If you had done it with the unlock tool it would have done the follow-up​ step needed. Now you Must do oem-unlock, and format userdata again to get Past boot loop.
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Okay thank you I will try :(
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Thanks you, all is well now, I owe you beer. Never forget those like you
[BLU R1 HD Guides, News, & Discussion] musclesbenz:
Step By step

A. Make sure you have developer mode turned on and debugging mode enabled(go to settings- about device- and rapid click on build number until developer options appears, then tick usb debugging)

B.Uninstall any and all drivers for the phone and restart computer

C. Install 15 second driver in administrative mode

You have to be booted into the android operating system in order to get the phone to install the adb driver. (In my case I had to go to device manager and manually set it to adb device).

You have to be booted into the fastboot by typing "adb reboot bootloader" into a cmd prompt in order to get the operating system to install the fastboot driver. (In my case I had to go to device manager and manually set it to fastboot device).

D.Turn phone on and plug it in,

E. There will be a thing that asks you (on the phone) if you want to always trust connections from such and such a computer click yes.

F. The cord that shipped with the phone would not allow me to install the fastboot drivers when using the OEM cord (that came in the box with the phone) it gave me this error: This device cannot start. (Code 10) error when attempting to install the driver for the bootloader.

G. When starting step 3 you must be in Android mode (and fastboot drivers must be operational) Check this by OPENING A COMMAND PROMT AND CHECK FOR ADB CONNECTION WITH "adb devices"

IF THIS SHOWS CONNECTED THEN ISSUE "adb reboot bootloader" TO BOOT PHONE INTO

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

CONNECTED THEN YOU CAN REBOOT PHONE WITH "FASTBOOT REBOOT" OR IF THAT NOT WORKING HOLD

POWER BUTTON TILL POWER OFF THEN POWER BACK ON.

IF "FASTBOOT DEVICES" DOES NOT SHOW A CONNECTED DEVICE, YOU MAY NEED TO GO TO PC DEVICE MANAGER

AND LOOK FOR A LISTED ANDROID DEVICE WITH WARNING "TRIANGlE" SYMBOL ON IT. AND MANUaLLY UPDATE THAT DRIVER.

Right click the Android device with yellow triangle, select update driver, browse my computer, let me pick,

there should be "Android bootloader interface" in the list somewhere.

after step 3 (in the dirtycow V11 tool) I had to reboot it manually twice and re enable the developer options/debugging tool and reallow the connection to the computer from the phone (popped up after trying to run step 4 the first time)

This was a prime Blu R1 HD with 2GB of Ram. Operating System V6.6.. I installed V11 of the dirty cow.
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Sometimes during the script, the phone can appear as 'p6601', or when TWRP appears, and you enter adb sideload mode, script continues to say no device found/adb mode not found. What could be issue?
[BLU R1 HD Guides, News, & Discussion] sfcaarnut:
V8.4 will not Root

Tried rooting and Dirty cow step 1 ok. Won't load step 2. Any updates?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
No.

Like the title of this tool says versions below V8

This method only works because of dirty cow exploit. And the new kernel has blocked the exploit.
[BLU R1 HD Guides, News, & Discussion] big_ben_guy:
Mine is V8.4, and I have the same issue

adb shell /data/local/tmp/dirtycow /data/local/test/frp /data/local/tmp/unlock

returns "load destination error"
[BLU R1 HD Guides, News, & Discussion] SomeGuy2008:
Just want to say Thanks. I bought a $50 BLU R1 HD Phone on Amazon. It came with 7.4.2 and after about 15mins a reading a few posts I now have a fully rooted and bootloader unlocked phone. SWEET!

~SG
[BLU R1 HD Guides, News, & Discussion] Phazed47:
Just went though this process on my R1 HD. While everything seemed to go OK (I have Super SU installed, TWRP runs without errors and AMZ debloat worked fine), I never saw the Android guy on his back. My phone hangs when told to reboot in fastboot mode, I thought I followed the instructions correctly but did I miss something?

I have not put in a SIM or permitted the phone on WiFi yet.
[BLU R1 HD Guides, News, & Discussion] SomeGuy2008:
I had the exact same thing happen to me, no android guy on his back ever showed but it did hang for about 5-10mins or so on the BLU boot logo. I didnt think much of it as in the end I was rooted, bootloader unlocked,and had twrp installed which was all I cared about.

~SG
[BLU R1 HD Guides, News, & Discussion] big_ben_guy:
what's your version? There are still no solution for V8.4 yet
[BLU R1 HD Guides, News, & Discussion] mrmazak:
if twrp was allowed to install then the previous steps had to have completed. Not seeing the "android-guy" during the initial wipe may be hidden or not shown on the newer (v6.6 and above)
[BLU R1 HD Guides, News, & Discussion] Phazed47:
Thank you for the confirmation, that's what I was figuring. This is as delivered by Amazon:

October 5, 2016

BLU_R0011UU_V7.4.2_GENERIC 09-11-2016 13:38​

Confirming that AMZ debloat does work on 7.4.2 - after phone reboot, I saw the AMZ stuff for a few seconds, then it was removed.

Thank you very much for your efforts - time to test on T-Mobile.
[BLU R1 HD Guides, News, & Discussion] gustavofaria25:
Any news for v8.4? Thanks.
[BLU R1 HD Guides, News, & Discussion] Jaa-Yoo:
I have a brand new r1 and im trying to use this tool but every time i run the dirty cow .bat file, a cmd window opens and then closes before i can read whats going on. Nothing else happens. Ive run the file many times now and have tried looking for a solution in this thread but havent found on. Any help would be appreciated.

Im using a fully updated windows 10. adb and fastboot are installed and the phone shows up in device manager and while in fastboot mode it comes back as connected.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
What version is the ROM on your phone? If you updated the phone using the over-the-air update to 8.4, then the bootloader can not be unlocked and the phone can't be rooted.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
In the begining of the .bat file, it is supposed to check for certain folders used for running the tool , and create them if needed.

Please check in the folder that the tool.bat file is for these folders: "working" , and "dirty-cow-log".

I have made the script run in a sub-process to try and prevent the window from closeing when an error happens,

general conditions needed for tool to run.

1. files must be un-zipped to a folder

2. un-zipped folder must be in location that user has "write" permissions (not in root of C or program folder)
[BLU R1 HD Guides, News, & Discussion] Jaa-Yoo:
Thanks,

I did all that but still had the same issue.

I got it sorted out though. After many attempts to run the tool, i was finally able to read some of the info before the window closed. adb was returning a device not found error...because the phone was still in fastboot mode! :silly: The phone doesnt respond when issued the reboot command and it didnt occur to me that the tool was using abd. I did manual reboot and ran the tool again without a problem.

Thanks
[BLU R1 HD Guides, News, & Discussion] Phone geek wayne:
should the phone be on?

Should the phone be on when this is happening, or turn off?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Phone must be on. Tool uses adb so phone must be on and adb enabled, PC must be authorized.
[BLU R1 HD Guides, News, & Discussion] Phone geek wayne:
Version 8.5

i dont know if it is something wrong with my phone, the verison is 8.5 recent update last month security patch june 5, where do i turn on adb?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Well that's a problem.

Tool no longer works past v8
[BLU R1 HD Guides, News, & Discussion] killerderk:
When trying to do anything on the 5th menu, It reboots with the android but on his back with a red /!\ and pressing any key gives me an error.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Did steps 1-4 work?

Options on menu 5 all use recovery, so if recovery did not install correct then that might explain it.
[BLU R1 HD Guides, News, & Discussion] killerderk:
That was it, didn't install twrp. :laugh:
[BLU R1 HD Guides, News, & Discussion] Jô$èph D:
I have your solution m8 you must have your adb and fastboot files in the same folder as the dirtycow.bat see picture for reference
[BLU R1 HD Guides, News, & Discussion] sourpickles:
I have a new blu r1 hd, the 8.3 update has downloaded but I haven't installed it, still on 7.4.2. Assuming I can do a factory reset and prevent it from installing the update, is it still possible to root/debloat using the linux scripts or is it recommended to use windows? Also, as long as I'm not flashing a new OS I don't need an SD card, right?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
the linux version may have bugs. It has not been tested as much as windows version.

and you do not need sdcard , even if changing os, it can be done without sdcard.
[BLU R1 HD Guides, News, & Discussion] jimmythefung:
Thanks for the note... I will try the windows version.

I just got my phone this week and I am new to Android world.

I ran into a number of problems with the linux tool (R1-HD-TOOL.sh) that I git cloned from your repository and I'm getting pretty nervous.

For example

-missing "working" directory

-md5sum mismatch: cp_comands.txt

-md5sum mismatch: dd_comands.txt

I manually ran md5sum on each of the pushed files and found that the actual checksum value of the 2 files mentioned above differ from the hardcoded values in the R1-HD-TOOL.sh

I will give the windows version a try. But those shell scripts are very sophisticated. Thanks for your wonderful work!
[BLU R1 HD Guides, News, & Discussion] mrmazak:
yeah, thats what i mean by having some bugs. I made some minor changes to the cp and dd comand text files but didn't change the md5 lines in shell.

i thought the working directory was suppoed to be corrected by the shell,i know the windows version creates the directory. anyway, thanks for the compliment.
[BLU R1 HD Guides, News, & Discussion] sourpickles:
Thanks for all your help mrmazak and everyone else.

I too tried the linux version and got some errors during the adb_check and fastboot_check saying no devices found. When running `adb devices` on my own it shows up though.

I should have access to a windows PC at some point but will I need to install adb/fastboot or is it all self-contained in the zip file now?
[BLU R1 HD Guides, News, & Discussion] jimmythefung:
I ran into the same issue. After investigating, I discovered that the output of "fastboot flashing get_unlock_ability" fails to redirect to unlockability.txt. (Note I also had to "sudo apt-get install fastboot" to use the fashing get_unlock_ability command)

This is very strange.

So I experimented a little more:

1. "flashboot flashing get_unlock_ability | grep OKAY"

-stdout still prints everything! (I was expecting only the line "OKAY [ 0.007s]" get printed)

2. "flashboot flashing get_unlock_ability | wc -w"

-stdout print everything. Plus an additional line indicating the value of word counts is 0

So it looks like the output of "flashboot flashing get_unlock_ability" can't be worked with.... I don't understand!

For now I'll just change the script to bypass this check since my phone's unlock_ability = 16777216 (great than 0).
[BLU R1 HD Guides, News, & Discussion] mrmazak:
yes needs install at least the 15 second install version mentioned on op. and also drivers

but you dont need to use the script as a "tool"

it can be done as individual typed commands.

I have attached two text files which should help you to manually do the unlock while still in linux, but not using it as a "tool" or automatic script
[BLU R1 HD Guides, News, & Discussion] sourpickles:
Awesome thanks! If I were to proceed with that method and do the same for the supersu and debloat steps, would I require an sdcard at that point or could I transfer the zip files over some other way? I noticed they transfer to the /sdcard/ in the R1-HD-TOOL2.sh. Would it be okay to swap that for /data/local/tmp/ or somewhere else? Sorry for asking so many questions, this is my first android phone and first experience with rooting/flashing hardware.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
On the phone /sdcard is internal memory. So no need for external sdcard.
[BLU R1 HD Guides, News, & Discussion] sourpickles:
I was able to unlock the bootloader and flash twrp. Thanks so much for the help mrmazak . :D
[BLU R1 HD Guides, News, & Discussion] jimmythefung:
I really enjoyed reading your shell scripts learning how it works and modified it just a little enough to root my phone.

Am curious:

1. What was the rationale behind the md5sum check? To ensure no malicious code downloaded from different place? or correct version of file?

2. How did you get into the android dev scene? What books/resource would you recommend me to learn enough to develop these system level android tools? (I took operating systems last semester, but it's too generic and conceptual for android meddling).

3. It seems like the R1-HD dev community is... relatively quiet, and learning examples are limited. Is there another cheap phone that continuously gets lots of on-going development attention?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
1. MD5, yes just as a method to prove the files were in tact as intended. Who knows what might have happened if somehow different/ wrong files got pushed and used.

2. I wouldn't consider my contribution quite on a Dev level yet. More of a spaggetti codder. As evidence in my script. Which was inspired/ modeled after "carliv android kitchen tool" and rootjunkie "Kindle super tool"

As far as resources to look at. You seem to be on the right path, you studied my script. Search internet for other tools and look at them too. Problem might be other common tools are not readable batch files.

3. I don't know
[BLU R1 HD Guides, News, & Discussion] jimmythefung:
#2 is cool. Thoughtful work is evidenced in the script. Having seen the result, now you inspired me :)
[BLU R1 HD Guides, News, & Discussion] driz:
just thought I'd chime in. I just bought 2 of the 50$ 2g ram ones and got them today. I immediately enabled developer options and came to xda. I ran this script (which ill be honest, was bothersome, i'm used to doing commands myself, but I was being lazy and trusting) and it worked perfectly. I just finished running the ad removal and debloat scripts (as well as blocking ota (it came on 7.4)). things are working perfectly.

I've got project fi sim cards in and they're very fast. my daughters are extremely happy. Great work and much appreciated guys!
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
By running either of the Amazon debloat scripts automatically blocks OTA?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
supposed to
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Awesome thank you ?
[BLU R1 HD Guides, News, & Discussion] mr_norr:
Anyone have trouble failing the MD5 compare at Step 2? Every device I try this on it can't get past that
[BLU R1 HD Guides, News, & Discussion] mrmazak:
At step two it is confirming if the dirty-cow part completed, .

First question that comes to mind is what version of the tool and what version of phone?
[BLU R1 HD Guides, News, & Discussion] mr_norr:
Thanks for the response, I tried the tool with both versions 8 and 11.

The version of the phone is: MRA58K BLU_R0010UU_V8.5_GENERIC 13-06-2017 18:25.

I later realized after posting my comment that your exploit was intended for versions 8 and below, silly me for updating so often.

Has there been any recent developments within the XDA community with exploiting anything post v8?

Edit:

I did try removing the MD5 comparison statement from the script to see if it would go along anyways but it didn't resolve the issue, it ends up failing after that point regardless
[BLU R1 HD Guides, News, & Discussion] yaconsult:
There are no known exploits for the latest ROM version of the Blu R1 HD. If the phone is still within the Amazon 30 day return windows, return it and don't let the replacement connect to either phone network or wifi until after you reflash and root it. Never accept an over-the-air update for a phone that you want to modify.
[BLU R1 HD Guides, News, & Discussion] mr_norr:
I was actually part of the first batch of phones lol, I took part in the preorder. Lesson learned though :cool:
[BLU R1 HD Guides, News, & Discussion] zombie_ryushu:
My Phone is expected to get here tomorrow.
[BLU R1 HD Guides, News, & Discussion] yaconsult:
Do not update it if you want to root it or remove ads. It would be good to know which release the phones are currently shipping with - please let us know what you get. It's in Settings->About device->Custom build version. If it is less than version 8 then you can reflash it.
[BLU R1 HD Guides, News, & Discussion] zombie_ryushu:
I have no intention of updating it or connecting it to any network until I can load Lineage OS on it. If for some reason it has v8, I will return it. This is a used device listed as having "Minor Cosmetic Damage"
[BLU R1 HD Guides, News, & Discussion] Jô$èph D:
This tool is great I love it me and my family have this phone and it has worked with all of them the only issue I had was on v7.12. I used super su to root when I tried to remove it it says uninstall failed
[BLU R1 HD Guides, News, & Discussion] zombie_ryushu:
Its here. It arrived with no case, no screen protector, just a box and a charging cable. And a discharged battery.
[BLU R1 HD Guides, News, & Discussion] zombie_ryushu:
Okay, So it appears to be V6.1. I have installed nothing in the device. As of yet.
[BLU R1 HD Guides, News, & Discussion] alexytoo:
I have a blu r1 hd version 8.5 and I can not rootear, I have used all the methods and still have not got it, any suggestions?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
no. Not posible at this time. Somebody may find a way, but right now there is none.

and please do not "quote" the entire op.
[BLU R1 HD Guides, News, & Discussion] Cheapo2311:
Seeing there is at least one senior member here, how similar is the Blu Advance 5.0 (D030UX) to the Blu R1 HD? I was considering upgrading to the R1, but I am able to root the Advance 5.0 in less than 25 secs with Kingroot. Is that possible with the R1? Does the R1 allow OEM Unlocking?

Sorry for so many questions! If you could answer with experience, please do so.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
the original, "non-prime" version . Had oem unlock toggle. but the prime did not. Thats why this tool thread is here, It forces the ability to do oem unlock. Then once unlocked twrp installs and root is as easy as install superSU. NO KINGROOT here.

But amazon has caught up to us here and trumped our progress with ther V 8 and above buils.

So as lng as new device comes lower than V 8 , you are good to go. 2 to 5 minutes total to unlock and root , as long as you know how to install drivers. Some people took days to complete because trouble getting drivers.
[BLU R1 HD Guides, News, & Discussion] Cheapo2311:
With a V8, wouldn't the simple solution be to simply flash an older firmware for the model and then root as instructed?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
There is no way to flash it. It will not connect to sp flash tool, and bootloader is locked so cannot fastboot flash it.
[BLU R1 HD Guides, News, & Discussion] ivarme:
I installed FM radio from this thread but it appears it broke safetynet attest.

Did I do something wrong?

Or any idea how to make phone to fix safetynet test?
[BLU R1 HD Guides, News, & Discussion] Cheapo2311:
I think, based on my own experience, any application that comes built in as a system app is denied installation because it has a line of code that verifies certificates from the system_server. To install it, I think you'd need to root your phone, and then use either ADB or a SuperSU app to install as system app "/system/apps".
[BLU R1 HD Guides, News, & Discussion] castalos:
I used this method to root my BLU R1 HD (no Amazon ads version) a few months ago. I only have one program which needs root, I haven't used root to installed anything else other than what was in this thread (ADB, Fastboot, OEM unlock, SuperSU). Unfortunately, I got signed out of Snapchat and can't log back in because of the root (apparently Snapchat checks for root and gives a message " Oh no! Your login temporarily failed, so please try again later...." if it detects root).

Is there a way to get signed back into Snapchat without having to unroot, signin to snapchat and then re-root?

And if I need to unroot, do I just go to SuperSU and select the Settings Tab and select Full unroot? Then start all over again? Please in simple terms as I'm a Noob and all this is new to me.

Thanks!
[BLU R1 HD Guides, News, & Discussion] Gizmosis350k:
Awesome, works like a charm :)
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I dont use snapchat, so my information has only come from google. But a quick search on "snapchat rooted device" brought me to this page.

https://www.quora.com/My-phone-is-r...ng-me-to-log-in-what-can-I-do-to-hide-my-root
[BLU R1 HD Guides, News, & Discussion] KyleStilkey:
I personally use Magisk. It's supported way better and that's what I use on my wife's R1 HD. I would recommend uninstalling SuperSU and grab Magisk, then in the settings of Magisk, enable Hide Magisk option and you should be good to go. I've been using the latest version without any issues.
[BLU R1 HD Guides, News, & Discussion] Darkyputz:
Hello and THX to all the contributors to this great Tool...

Phone is de bloated and rooted successful in no time

A small question on the site...are there updates for R1 that keep Bootloader open and su/root active or is any update bad?!

Have TWRP installed...if i catch an update and it takes stuff away...will it also lock boot loader and kill TWRP or can i always go back since TWRP is in and Bootloader is permanent unlocked now?!

THx for your answers
[BLU R1 HD Guides, News, & Discussion] mrmazak:
so far experience has been that having root will cause the ota to fail. Which ends up a good thing that it fails, because the updates change the "preloader" and "lk". Making sp flash tool unuseable.

To date if an ota update comes through and you were not rooted but had unlocked bootloader, the update causes a bootloop. And to clear need to perform oem unlock again. (which requires format of data)

I have a thread up in the forum that has all the update patches applied in twrp format installable roms.

The updaed roms will require refashing SuperSU (or magick) re re-apply root.
[BLU R1 HD Guides, News, & Discussion] Darkyputz:
Thx for the info...great to hear that OTA will fail anyways...

Will check for your thread...still great work here...
[BLU R1 HD Guides, News, & Discussion] Shadow899:
The instructions here are nuclear science to mine eyes. If someone makes an easy-to-follow video (like the ones RootJunky makes), I will give you my left leg (I'm a girl). My version is 6.6.