yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Would have been a lot simpler, had he mentioned he was trying to flash a miracle backup via flashtool.
[BLU R1 HD Guides, News, & Discussion] dxtian:
Thanks, now trying with miracle, I have another problem, the brick phone when reading the miracle closes. But right now connect the other one that works for me and if it loads it.
[BLU R1 HD Guides, News, & Discussion] dxtian:
:(

me da este error :(

---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------

[IMG]https://xdaforums.com/picture.php?albumid=14206&pictureid=55692[/IMG]

---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------

---------- Post added at 04:37 AM ---------- Previous post was at 04:37 AM ----------

---------- Post added at 04:41 AM ---------- Previous post was at 04:37 AM ----------
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I linked maybe to wrong backup. That backup should be ok if you did not format all, but you did format.

Try this one.

https://www.androidfilehost.com/?fid=745425885120728157
[BLU R1 HD Guides, News, & Discussion] overthc:
[MENTION=5355478]ColtonDRG[/MENTION] [MENTION=5312578]mrmazak[/MENTION] I bought a mobile with Amazon Prime and came up with version 7.4.2 how can I get rid of Amazon's add-ons?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
first, make sure not to connect to internet till mods are done. if it does an ota update it will not be able to modify it

need to unlock bootloader, then install twrp or boot twrp if not want to install.

https://xdaforums.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555

from twrp can run debloat-3.zip from [MENTION=6782683]emc2cube[/MENTION] to remove ads

https://xdaforums.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555

or flash a pre-modified rom
[BLU R1 HD Guides, News, & Discussion] overthc:
It dies not work.. see attached image
[BLU R1 HD Guides, News, & Discussion] mrmazak:
that is why i did not say to use sp flash tool.

official updates to all versions above 6.6 will have no connection to sp flash tool.

must follow the guide (tool) i linked you to. It uses combination of dirty-cow adb command and fastboot to unlock bootloader and through the process will install twrp.
[BLU R1 HD Guides, News, & Discussion] overthc:
I can´t flash nothing because I have no installed TWRP and I can´t find the links of this post to do this process.. Help me please!!!
[BLU R1 HD Guides, News, & Discussion] mrmazak:
put the same link twice before.

here is link to unlock tool

https://xdaforums.com/r1-hd/how-to/unlock-tool-t3561333
[BLU R1 HD Guides, News, & Discussion] overthc:
I´ve downloaded R1-HD-Tool-V11.zip from the post and unpack it, the I run the dirty-cow-tool.bat and open a windows command for 3 seconds and close withouth make nothing.... ( pre installed adb-setup-1.4.3.exe)
[BLU R1 HD Guides, News, & Discussion] mrmazak:
this happens usually when adb cannot connect to phone or cannot write to text file on pc.

so make sure adb is enabled on phone and you have allowed (authorized) connection

and make sure tool is not unzipped to write protected area on hard disk.
[BLU R1 HD Guides, News, & Discussion] overthc:
TKU... I had bad setup debugging... It work perfect until step 4

Now.... May I flash the v8.4 mod by you (https://xdaforums.com/r1-hd/development/modified-8-3-stock-rom-t3602672) ? May I install a backup from other Blu with v8.4 mod?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
i recommend to use 8.4 there was some problems with 8.3, thats why blu quickly made 8.4

now to install the 8.4.

connect phone, should see phone as portable device on pc. copy zip file to phone. Reboot to recovery.

either by holding volume up when rebooting or with adb command "adb reboot recovery"

then in twrp select install and browse to the zip file added.

I usually also wipe (factory reset) at this time
[BLU R1 HD Guides, News, & Discussion] overthc:
[MENTION=5312578]mrmazak[/MENTION] Error 7 flashing v8.4-twrp-install.zip and error 225 installing a backup with v8.4........ Must I flash V21 coming from non Amazon Prime?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
you are confussed me a little. You have asked from beginning about starting from v7.4.2 (a prime version)

now say it has trouble because of being non-prime.

anyway you can use either one.

error 7?

error is generic.

the zip is good, many have used it.

should work with either recovery (vampire, or lopestom)

must swipe on first screen of recovery to allow modification of /system

and /system needs to be not mounted when starting install.

error 225 could be not enough space on memory.

Is this the 8gb phone you asked about before?
[BLU R1 HD Guides, News, & Discussion] overthc:
Yes, my phone it´s amazon prime and I taken off the amazon ads-on. But now I want to flash tne last ROM avaiable to my phone, and I thought I could flash v8.4. Can I do it or not? If not what´s the latest version avaiable to update v4.2.1 debloated?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
v8.4 and v21 both should work.

but you did not answer is the phone 8gb storage 1gb ram or 16gb storage 2gb ram?

having the ads removed makes no difference at this time.
[BLU R1 HD Guides, News, & Discussion] overthc:
Excuseme, it´s 2 GB of RAM
[BLU R1 HD Guides, News, & Discussion] mrmazak:
then the error 7 has no explanation. other than a damaged phone, or mounted /system.

make sure in twrp menu -- mount -- that system is not check marked (not mounted)
[BLU R1 HD Guides, News, & Discussion] overthc:
The only thing I could install was the nandroid of stock v.7.4.2 I´d backuped.

I´m downloading Blu-R1-HD-V21-twrp_install.zip to flash it to see what happens. I´ll tel you.

Edit: I did a dirt flash of v8.4 over v7.4.2 and work properly.(I was making it clean wiping everything)
[BLU R1 HD Guides, News, & Discussion] bdvstore87:
hello friends, there is the possibility to root my R1 hd R0030uu, I have the latest update V 9.0, I have never rooted the phone, I have never unlocked the bootloader.

sorry for my english, thanks for your help
[BLU R1 HD Guides, News, & Discussion] yaconsult:
No. With version 9 of the Blu ROM you can not unlock the bootloader or root. Also, the bootloader can not be downgraded to allow unlocking or rooting.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
I am following your amazing work and trying to fix my kid's phone ... my fault :(

I am not sure if it got upgraded to 6.6 or not... it was 6.5 but know i get the problem with SuperFlash..

As soon as I plug the cable to the computer while SP is waiting for it, the phone starts booting, doesn't stay off. I can still get it in fastboot and run any command from it. Is it still too late???

Please help !

Thanks
[BLU R1 HD Guides, News, & Discussion] mrmazak:
It all depends if the device still boots, and has access to adb.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
Let me tell you what I am doing:

- Phone off. Vol UP + Power. Phone boots and I select FastBoot <<<===

-I can connect to it via fastboot from my PC. and it sees my Blu R1 HD. I do the oem unlock, get the message on the phone to press Vol UP to agree to it. Then I turn the phone OFF. Start the Flash Tool, click Download.

-As soon as I plug the phone , I get the error and the phone starts to boot (the white BLU Bold Like US logo)... and stays in a boot loop.

Please see the video here: https://screencast-o-matic.com/watch/cFnQFgoEaN

Please help !!

Thanks a lot for taking the time to respond
[BLU R1 HD Guides, News, & Discussion] mrmazak:
After oem unlock, phone needs to do factory reset to format /data

This is done with stock recovery.

Sometimes formating data and cache with fastboot clears this loop you have , but not all ways.

For sp flash need to start with phone off and unplugged. Plug phone in after click dowoad.

But if phone was updated you will not be able to sp flash tool because the update blocks the preloader from connecting to it.

.did phone work before you tried to unlock it?

Please fill in some details for me to help better.

1 phone working or not

2 stock rom or custom

3 stock recovery or custom

4 enable oem unlock switch in developer settings on

5 status of unlock and secure results when run this command

"fastboot getvar all"

Assumptions I make based on your problem as I can tell.

You had some previous modification on device. Because you said you think it was on v6.5 , and your video shows "oem unlock" completing. V6.5 could not do "oem unlock" without being modified. By flashing a different "frp" partition with sp flashtool or by using "dirty-cow" to replace the "frp"
[BLU R1 HD Guides, News, & Discussion] jcmachado:
This is the output of that command:

C:\adb>fastboot devices

N7CALN8SCAEYW8VS fastboot

C:\adb>fastboot getvar all

(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.084s
[BLU R1 HD Guides, News, & Discussion] mrmazak:
ok, good. Confirmed unlocked.

should be able recover from most situations from there.

Don't know what your original problem was, so can only take it one step at a time.

lets see if booting stock recovery helps..

From the fastboot mode

"fastboot boot %userprofile%\downloads\stock-6.1-recovery.img"

unzip the attached recovery to downloads folder.

I expect this to cause the stock recovery to do a factory reset. Then continue to boot the rom.

If there is other issues let me know.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
C:\adb>fastboot boot "c:\Users\juan\Desktop\Amazon R1\last\stock-6.1-recovery.img"

downloading 'boot.img'...

OKAY [ 1.586s]

booting...

OKAY [ 0.047s]

finished. total time: 1.633s

then it rebooted by itself...

now back to the reboot loop, showing the WHITE BLU BOLD LIKE US logo...
[BLU R1 HD Guides, News, & Discussion] mrmazak:
OK.

I went back through your old posts and i see you did dirty-cow one year ago. That's good to know.

And flashed modified 6.6 then removed ads. All fine. But needed to know.

Now your recent post that started in this thread few days ago, say you trying to repair sons phone (your fault).

that needs to be explained more, to try and help.

because you had unlocked bootloader and flashed recovery and rom before, there was not really reason to unlock again, making these steps unnecessary, and possibly complicating the original problem.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
After getting an email from Amazon regarding Blu R1 HD and them stopping doing the ADs and after reading a lot of posts here, what I did was to download one of the images from this forum to set it back to the Amazon stock from here: http://rootjunkysdl.com/files/?dir=Blu R1 HD Amazon/TWRP Stock Amazon Backup .

That set my phone back to the point when I bought it from amazon ... then I got an update pop up, I guess that's what you call OTA (please excuse my ignorance, I am here to learn) and it got applied. After that... boot loops and that's why I am here asking for help.

All I wanted was to set it back to the original state, go to the Play store and let it remove the ads as Amazon indicated.

Thanks again for your expert help.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
ok.

that update is making trouble, that I have not seen before.

No other reports of taking latest OTA update while bootloader unlocked.

I am always nervous about re-locking bootloader, as sometimes it makes fixing brick too difficult. But I think in this case, it is brick already, so might as well try.

try to relock bootloader.

"fastboot oem lock"

be advised this might not work and might not be able to unlock again.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
I get LOCK FAILED in the phone screen and this from my PC:

C:\adb>fastboot oem lock

...

(bootloader) Start lock flow

FAILED (remote:

lock failed - Err:0xfffffffe

)

finished. total time: 6.786s
[BLU R1 HD Guides, News, & Discussion] mrmazak:
maybe try to fastboot boot twrp

will be back this evening to check any updates.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
You mean trying to boot into Recovery Mode from the phone? I tried that, it just goes to the reboot loop. Or do you mean trying to run that command from Fastboot? If you mean the second, I get this:

C:\adb>fastboot boot twrp

cannot load 'twrp': No such file or directory
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Yes it is the later one.

But just like the last command I had you download the stock recovery and direct the boot command to that downloaded file.

You need to point the boot command to your downloaded twrp.

For an example.

"fastboot boot %userprofile%/downloads/twrp.img"
[BLU R1 HD Guides, News, & Discussion] jcmachado:
C:\adb>fastboot boot "c:\Users\juan\Desktop\Amazon R1\twrp-3.2.1-0-twrp.img"

downloading 'boot.img'...

OKAY [ 0.468s]

booting...

OKAY [ 0.053s]

finished. total time: 0.522s

tried to boot into recovery (twrp), same thing... boot loop.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Alright, maybe still options here.

Because it tried to boot twtp it gives me hope. Perhaps the. V6.1 stock recovery won't do. When I get back to my PC I will redo my phone so makes the v9 stock recovery and send you that to try and boot.

But first

Try

"fastboot format userdata"

"fastboot format cache"

"fastboot format misc"

Then try to fastboot twrp again
[BLU R1 HD Guides, News, & Discussion] jcmachado:
C:\adb>fastboot format userdata

erasing 'userdata'...

OKAY [ 0.068s]

formatting 'userdata' partition...

Creating filesystem with parameters:

Size: 838860800

Block size: 4096

Blocks per group: 32768

Inodes per group: 7328

Inode size: 256

Journal blocks: 3200

Label:

Blocks: 204800

Block groups: 7

Reserved block group size: 55

Created filesystem with 11/51296 inodes and 6651/204800 blocks

sending 'userdata' (14952 KB)...

writing 'userdata'...

OKAY [ 2.033s]

finished. total time: 2.101s

C:\adb>fastboot format cache

erasing 'cache'...

OKAY [ 0.016s]

formatting 'cache' partition...

Creating filesystem with parameters:

Size: 419430400

Block size: 4096

Blocks per group: 32768

Inodes per group: 6400

Inode size: 256

Journal blocks: 1600

Label:

Blocks: 102400

Block groups: 4

Reserved block group size: 31

Created filesystem with 11/25600 inodes and 3310/102400 blocks

sending 'cache' (8192 KB)...

writing 'cache'...

OKAY [ 1.167s]

finished. total time: 1.184s

C:\adb>fastboot format misc

formatting 'misc' partition...

Formatting is not supported for filesystem with type ''.

FAILED ()

finished. total time: 0.003s

C:\adb>fastboot boot "c:\Users\juan\Desktop\Amazon R1\twrp-3.2.1-0-twrp.img"

downloading 'boot.img'...

OKAY [ 0.453s]

booting...

OKAY [ 0.063s]

finished. total time: 0.516s

---

That made it reboot ... into a boot loop again...

tried to boot into recovery from phone, same issue.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
On that last command instead of format misc

Make it "fastboot format para"

See if that works

Past that the options get even further into untested methods.

"ie"

Fastboot flash aboot

Or

Flash tee1

Tee2

All of which can make solid bricks.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
C:\adb>fastboot format para

formatting 'para' partition...

Formatting is not supported for filesystem with type 'raw data'.

FAILED ()

finished. total time: 0.016s
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Ok, we know that the update replaced

And signed all parts of the bootloader.

And because getvar shows bootloader is unlocked we can assume that the "preloader to the lk" stage of boot up is ok.

Maybe it's not.

Will suggest try to boot the v9 boot.img from my modified v9.

I will send you file if needed.

It is made bypassing the signature. Because it is intended for unlocked systems.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
Please, send me the img file and I will try it. Just spell out all the commands you want me to run. Thanks again !
[BLU R1 HD Guides, News, & Discussion] mrmazak:
similar to before. download file here to downloads folder

"fastboot boot %userprofile%\downloads\boot.img"
[BLU R1 HD Guides, News, & Discussion] jcmachado:
OK, applied the new boot.img, fastboot rebooted it. Back to reboot loop.

tried to go into recovery, same results.

This is the getvar all, in case you want to see it:

C:\adb>fastboot getvar all

< waiting for device >

(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.039s
[BLU R1 HD Guides, News, & Discussion] mrmazak:
this next idea might make your phone "turn off for the last time" if you get my meaning.

only try if you understand that last statement.

"fastboot flash lk %userprofile%\downloads\lk.bin"

This will require a reboot to see if any change took place.

It may require another "fastboot oem unlock" once rebooted, as the lk.bin is part of the bootloader.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
C:\adb>fastboot flash lk "c:\Users\juan\Desktop\Amazon R1\lk.bin"

target reported max download size of 134217728 bytes

sending 'lk' (328 KB)...

OKAY [ 0.053s]

writing 'lk'...

OKAY [ 0.016s]

finished. total time: 0.069s

Well... it looks like my phone is now dead :(

Ouch... It doesn't want to turn off now.

When connected to a PC, I can "hear" is rebooting every other second" ....
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Not what I was hoping for, but Knew it was a possibility.

And long pressing power button (maybe as long as 2 minutes) does not force it off?
[BLU R1 HD Guides, News, & Discussion] jcmachado:
Let me try... :(

---------- Post added at 09:54 PM ---------- Previous post was at 09:28 PM ----------

Nope ...

Looks like it is completely dead now... :(
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Wait .. it is stuck "ON" not off.

that's backwords.

does fastboot still connect to it?

I assume not.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
No, it does not. ANYTHING else you want me to try ?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
no, i have no more idea.

unless condition changes after battery dies and it is forced to power off.
[BLU R1 HD Guides, News, & Discussion] jcmachado:
Nope... I let the battery died... exact same behavior after it get a charge back... Thanks
[BLU R1 HD Guides, News, & Discussion] kal250:
Just followed all your guides here ColtonDRG for prime to oem, I had previously completed rootjunkys guides and was successful, but your approach was much more straightforward. I did a complete factory reset prior to your flash, and as expected it said I was still bootloader unlocked, however i went through the unlock steps once more, i expected it to fail (HTC will throw an already unlocked error) it proceeded to reboot a couple times, then TWRP and root per your guides, everything so far is flawless, so thanks for everything. And BTW i still had to move over Microsoft Excel, Word, PowerPoint, and MX player, they just refuse to play nice with adoptable storage. So if anyone complains about your quide and flaky apps on adoptable storage, let em know... Lol bit seriously you rock, thanks for pointing us all in the right direction with this!!!
[BLU R1 HD Guides, News, & Discussion] :
Yeah, doing this procedure without wiping data is kinda hit or miss.