FORUMS
Remove All Ads from XDA

[TWRP] How to root ("newbie friendly"!) :

856 posts
Thanks Meter: 584
 
By bibikalka, Senior Member on 25th July 2016, 03:23 PM
Post Reply Email Thread
Quick root guide for Prime BLU R1 (any ROM version at the moment):
(the subject is so important that it needs it's own thread !!! )

If you are really advanced, you can actually start from unlocking the bootloader via SPFT (before you get to TWRP or SuperSU). Download SP-Flash-Tool-R1-HD-bootloader-unlock.zip package from : http://rootjunkysdl.com/files/?dir=B...%20HD%20Amazon . Load the scatter file, Download frp partition. Then : adb reboot bootloader ; fastboot oem unlock ; fastboot format userdata ; fastboot reboot With the unlocked bootloader, you could boot into TWRP via the fastboot command :
fastboot boot twrp.img


For the more "normal" path, copy TWRP into recovery partition, as per the instructions below :
1) copy SuperSu to /sdcard (internal storage):
https://download.chainfire.eu/969/Su...etrieve_file=1
2) download SP flash tools, the latest version (5.1628):
https://androidmtk.com/smart-phone-flash-tool
3) download the TWRP package from here (Prime BLU R1) :
http://rootjunkysdl.com/files/?dir=B...%20HD%20Amazon ( TWRP_Scatter_R1_Prime.zip )
4) install MTK preloader drivers on your PC (these have to kick in when you plug in your BLU in the off state to the USB port). Thanks to @Tzul for providing a link to the signed version of the drivers for Win 8/10 :
https://www.androidfilehost.com/?w=files&flid=68715
5) run SP flash tools, select scatter file from 3)
6) flash TWRP into recovery partition (Download option in SP Flash tools). Specifically, first select "Recovery" partition only via the checkbox (see the attached image on how SPFT will look like), push the "Download" button. Turn off your BlU R1, and then plug it into the USB port. The preloader runs as BLU is trying to boot up, and that is where SPFT will kick in.. Note that if BLU is booted up, it's way too late for SPFT to work!
7) Once SP Flash tools is done, press "Pwr" + "Vol+" on BLU R1, choose boot into recovery
8) In TWRP, first mount /system partition as read only, and back up all system partitions (optional, but highly recommended !!! )
9) Install SuperSu zip from 1), and reboot into system
10) If you care to use apps like ES File Explorer (those that are not updated yet to handle system-less root), you'll need to run these commands in adb :
Code:
adb shell
su
mount -o remount,rw /system
mount -o remount,rw /
touch /sbin/su /system/bin/su /system/xbin/su
mount -o remount,ro /system
mount -o remount,ro /
For the regular (non-Prime version), see this (the path is slightly different):
http://forum.xda-developers.com/show...&postcount=503

Note, SuperSu will go for "systemless" root, and will patch boot.img. The original boot.img will be saved as /data/stock_boot_*.img.gz It's highly recommended that you backup this boot.img elsewhere (off the device), in order to be able to restore the device and accept the OTAs.

Huge thanks to people who made this possible : @ jasonmerc, @ mrmazak, @ bullet25, @lopestom !!!!!
Attached Thumbnails
Click image for larger version

Name:	spft1.png
Views:	6604
Size:	50.5 KB
ID:	3829360  
The Following 15 Users Say Thank You to bibikalka For This Useful Post: [ View ] Gift bibikalka Ad-Free
 
 
25th July 2016, 03:34 PM |#2  
triggerlord's Avatar
Senior Member
Thanks Meter: 102
 
More
Is it weird I didn't have to install any drivers when I did this?
25th July 2016, 03:39 PM |#3  
OP Senior Member
Thanks Meter: 584
 
More
Quote:
Originally Posted by triggerlord

Is it weird I didn't have to install any drivers when I did this?

You prob had them from some times before ? Do you have other MTK devices ?
25th July 2016, 03:41 PM |#4  
ariesgodofwar's Avatar
Senior Member
Flag Fenton
Thanks Meter: 187
 
More
Quote:
Originally Posted by triggerlord

Is it weird I didn't have to install any drivers when I did this?

Not if you have other Mediatek devices. I came from the world of Nexus and Qualcomm, so my biggest challenge was figuring out how to install an unsigned driver on a 64 Bit Win 10 machine.......
25th July 2016, 04:26 PM |#5  
triggerlord's Avatar
Senior Member
Thanks Meter: 102
 
More
Nope, I just reinstalled windows 10 last week in fact. It was essentially a fresh install.

Sent from my BLU R1 HD using XDA Labs
25th July 2016, 05:22 PM |#6  
Senior Member
Thanks Meter: 54
 
More
Quote:
Originally Posted by triggerlord

Nope, I just reinstalled windows 10 last week in fact. It was essentially a fresh install.

Sent from my BLU R1 HD using XDA Labs

I have observed the R1 HD installing drivers (at least that's what I think it was doing) in a Win 10 machine while I was connected and messing with the USB Configuration menu. I saw a loading window that went away after a few seconds.

I'll see if I can reproduce it.
25th July 2016, 05:48 PM |#7  
ariesgodofwar's Avatar
Senior Member
Flag Fenton
Thanks Meter: 187
 
More
Quote:
Originally Posted by limpet

I have observed the R1 HD installing drivers (at least that's what I think it was doing) in a Win 10 machine while I was connected and messing with the USB Configuration menu. I saw a loading window that went away after a few seconds.

I'll see if I can reproduce it.

I had drivers load, 2 of them, when I plugged it in. The second one took forever, so I cancelled it, and then manually installed. Had I waited, that 2nd driver may have been the Generic CDC driver.
25th July 2016, 06:15 PM |#8  
Senior Member
Thanks Meter: 54
 
More
Quote:
Originally Posted by ariesgodofwar

I had drivers load, 2 of them, when I plugged it in. The second one took forever, so I cancelled it, and then manually installed. Had I waited, that 2nd driver may have been the Generic CDC driver.

I just did this.

Found ADB Interface in device manager. Right click, uninstall, accept reboot. Disconnected phone before restarting.

Selected "Charging only" in USB configuration and plugged in. This appeared almost immediately.

Click image for larger version

Name:	dm2.jpg
Views:	2100
Size:	40.2 KB
ID:	3823552

Clicked on MTP in USB configuration. No notification, but about 30 seconds of disk activity. Device list changed to this.

Click image for larger version

Name:	dm1.jpg
Views:	2084
Size:	36.1 KB
ID:	3823553

ADB was happy.
25th July 2016, 06:33 PM |#9  
Junior Member
Thanks Meter: 1
 
More
What MTK Drivers are being used? The original thread is super long now. Could we get a link to the ones that are known to work? I can't get my phone to be recognized while in an off state
The Following User Says Thank You to pathia For This Useful Post: [ View ] Gift pathia Ad-Free
25th July 2016, 06:39 PM |#10  
Senior Member
Thanks Meter: 54
 
More
Quote:
Originally Posted by pathia

What MTK Drivers are being used? The original thread is super long now. Could we get a link to the ones that are known to work? I can't get my phone to be recognized while in an off state

What does >adb devices return?
25th July 2016, 06:42 PM |#11  
ariesgodofwar's Avatar
Senior Member
Flag Fenton
Thanks Meter: 187
 
More
Quote:
Originally Posted by pathia

What MTK Drivers are being used? The original thread is super long now. Could we get a link to the ones that are known to work? I can't get my phone to be recognized while in an off state

See this post for detailed instructions: http://forum.xda-developers.com/show...&postcount=549

The drivers found here: https://androidmtk.com/install-andro...river-manually are what worked for me. Note that if you are on a 64 bit Windows 10 Machine, you will need to disable Driver Signature Verification, or the driver will fail to install.
The Following User Says Thank You to ariesgodofwar For This Useful Post: [ View ] Gift ariesgodofwar Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes