Related
Hello all,
Apologies for some brevity. Wrote a long, overly-detailed post before my browser crashed and left me frustrated as hell. I'll still try to be clear with my problem and my device information.
The Problem
During a trial-and-error process of getting my G4 (2016) unlocked, flashed, and rooted I've ended up in an odd predicament. The phone will not boot straight into Android-- it has to explicitly enter the Bootloader and be told to START. Otherwise (either by reboot or by powering on from off) it will enter the TWRP recovery. I don't know enough about the boot process to speculate as to why this is happening, but I can assume it's something I've done incorrectly during my myriad of errors on the process.
Device Information (Fastboot)
Code:
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.45R ATHENE_RETUSA_CUST
Product/Variant: athene_13mp XT1625 16GB P2A
Serial Number: ZY223CKDPQ
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
Console [NULL]: null
Battery OK (Charging)
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
System Unlock/Recovery/Root Summary
Bootloader has been unlocked with Official Motorola Unlocker Tool
TWRP Recovery flashed successfully (downloaded from twrp_athene_20160526.img)
Bootloader Warning Message overwritten (tried several logo.bin before finding a good one)
SuperSu installed using the Guide on rooting w/ TWRP and SuperSu via MANDATORY SYSTEMLESS ROOT.
Can anyone speculate and help me figure out what the issue is with this phone? I can't find stock firmware for the XT1625 yet or I would most definitely be willing to wipe everything, and start from scratch to experiment with the issue. I am also very foolish in that I did not IMMEDIATELY make a backup of the device upon successful TWRP flash, but did shortly after-- no backups I can restore from will fix this issue.
Thanks,
jwarner112
volume button sticking?
hi jwarner112,
if you have successfully bootloader unlocked your phone, you can enter fastboot mode of your phone by pressing both power+volume down button at the same time. but before you do this, you need to make sure you install the following items on your computer:
make sure to install the latest motorola drivers on your computer. here is the link to the drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
after installing the latest motorola drivers, download and install rsdlite for windows(latest version 6.2.4). here is the link to the latest rsdlite:
http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
finally download the latest stock firmware for motorola xt1625 non-prime exclusive (athene) from here:
http://rootjunkysdl.com/files/Moto%20G%204th%20Gen%20XT1625/Firmware/ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip.
After downloading this firmware, put your phone in fastboot mode by pressing on power+volume down button at the same time. once the phone enters into fastboot mode, now plug the device into your computer via usb.
now open the latest version of rsdlite on your computer and click on "show device". it should detect your device in fastboot mode, which is necessary to flash the stock firmware file which you have downloaded. click on the "..." button in rsdlite to browse to the stock firmware file and once you find it (make sure you open the file while it is in ".zip" format), decompress and flash it. Remember, this will wipe everything on your phone and will be more like a complete factory data reset.
Now the flashing process should be going on and once it is over, you will restore everything back to normal. Note that bootloader will still be unlocked, but root will gone and twrp recovery will be gone. Like before, flash your twrp, but before you do a root of your phone make a complete backup of your phone in twrp recovery so that you have a good place to start if root goes bad.
Also make sure when you install root, use the latest version 2.76. I accidentally installed the older versions of supersu, which didnt support systemless root and ended up soft bricking my phone. Here is the link to the latest version of root that is compatible with systemless root on the moto G4:
http://download.chainfire.eu/supersu-stable
Prior to flashing supersu, make sure you go to the adb terminal in twrp and type in the systemless root command so that it will force a systemless root installation of supersu. In order to do this, in TWRP go to Advanced and open the Terminal, and in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded (version 2.76 or higher) and swipe to flash it and reboot.
Once all of this is done, I hope you have a working phone with bootloader unlocked, twrp recovery, and systemless root. if you still have problems attaining this features in your phone, please let us know! otherwise, hit me a thanks!
Good Luck!
mikeruss said:
volume button sticking?
Click to expand...
Click to collapse
I don't believe this is the issue because I've got two identical phones with the same behavior. It seems intuitive to me that the error lies in the process.
fastboot oem fb_mode_clear
Should fix the issue.
aznindguy4u said:
hi jwarner112,
if you have successfully bootloader unlocked your phone, you can enter fastboot mode of your phone by pressing both power+volume down button at the same time. but before you do this, you need to make sure you install the following items on your computer:
make sure to install the latest motorola drivers on your computer. here is the link to the drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
after installing the latest motorola drivers, download and install rsdlite for windows(latest version 6.2.4). here is the link to the latest rsdlite:
http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
finally download the latest stock firmware for motorola xt1625 non-prime exclusive (athene) from here:
http://rootjunkysdl.com/files/Moto%20G%204th%20Gen%20XT1625/Firmware/ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip.
After downloading this firmware, put your phone in fastboot mode by pressing on power+volume down button at the same time. once the phone enters into fastboot mode, now plug the device into your computer via usb.
now open the latest version of rsdlite on your computer and click on "show device". it should detect your device in fastboot mode, which is necessary to flash the stock firmware file which you have downloaded. click on the "..." button in rsdlite to browse to the stock firmware file and once you find it (make sure you open the file while it is in ".zip" format), decompress and flash it. Remember, this will wipe everything on your phone and will be more like a complete factory data reset.
Now the flashing process should be going on and once it is over, you will restore everything back to normal. Note that bootloader will still be unlocked, but root will gone and twrp recovery will be gone. Like before, flash your twrp, but before you do a root of your phone make a complete backup of your phone in twrp recovery so that you have a good place to start if root goes bad.
Also make sure when you install root, use the latest version 2.76. I accidentally installed the older versions of supersu, which didnt support systemless root and ended up soft bricking my phone. Here is the link to the latest version of root that is compatible with systemless root on the moto G4:
http://download.chainfire.eu/supersu-stable
Prior to flashing supersu, make sure you go to the adb terminal in twrp and type in the systemless root command so that it will force a systemless root installation of supersu.
Once all of this is done, I hope you have a working phone with bootloader unlocked, twrp recovery, and systemless root. if you still have problems attaining this features in your phone, please let us know! otherwise, hit me a thanks!
Good Luck!
Click to expand...
Click to collapse
This fixed the issue for me. That is to say, I was able to flash the stock firmware for MPJ24_139-48 and from there re-flash recovery, logo, and systemless root.
Thank you!
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.
Do the camera and fingerprint work?
Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.
I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?
xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )
Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug#b. Enable OEM unlock
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:type: adb reboot-bootloader ___ (Wait 1-3 second)type: fastboot devices ___ (verify device is detected)#b. verify bootloader unlock statustype: fastboot getvar all ___ and you get= warranty: yes= unlocked: no#c. unlock bootloadertype: fastboot oem unlock ___ and you get-> start unlock flow---> on screen appear:vol UP=Yes; void warranty, clear ALL datavol DWN=no; no unlockPress Vol UP#d. verify bootloader unlock statustype: fastboot getvar all ___ and you get= warranty: no= unlocked: yes#e. May be phone restart
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txtas per normal way (You know this , after some trying...)
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons#b. choose recovery with Vol Up and confirm with Vol Down
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.
when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file
I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file
xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?
The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.
I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...
As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?
Hi guys,
I am a total noob with flashing etc.
Can somebody please be so nice to post here the right tutorial for my case? I want the Original Firmware.
I have read so many threads but they all sound different for me. :silly:
I have got an Motorola X Pure Edition from Ebay. It has Android 6.0 installed. I want to update to 7.0 but when it downloads the new firmware it will reboot and TWRP starts. I have downloaded the firmware 7.0 manually and tried to run it with TWRP but I get always error messages.
According to Bootloader:
Product: clark XT1575 32G P3C
Devise is unlocked
Status Code: 3
Software Status Modified
Do you need information about Baseband Version, Kernel and so on?
Appreciate your help :victory:
Nougat firmware for XT1575 is on androidfilehost.com linked to this thread. The linked thread includes instructions on how to use fastboot to flash the update. Updated baseband, kernel and all that are included in the full firmware package.
You'll need a PC setup for flashing too. Assuming you're using a windows PC you'll need to moto drivers you can get from here, and a minimal fastboot installation you can get from here.
Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.
Muffycheeks said:
Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.
Click to expand...
Click to collapse
No, you don't need to worry about returning to stock 6.0 to get an XT1575 to 7.0 anymore. Motorola-Firmware-Team released a leaked full firmware package for clark_retus-user 7.0 NPH25.200-22 linked to that acejavelin thread that I linked to. It isn't an incremental update, it is the whole package. Thanks to that, you don't have to return to fully stock 6.0, take or sideload an OTA, and hope for the best anymore.
Motorola Device Manager - Windows 10
Thanks guys for your comments.
Unfortunately I have already problems with the Motorola Device Manager (MDM). Seems like the drivers wont install.
Fastboot message = waiting for any device
I have run the MDM as an admin, activated USB Debugging and MTP but after installation of the MDM i get the congratulations message but i cant open the program.
I have installed the Media Feature Pack for Windows 10 and tried it again without success.
When i open the Motorola_Mobile_Drivers_64bit file from the Temp folder i can Repair or Remove Motorola Mobile Drivers Installation 6.4.0 but I can`t run it.
Other cable and USB Port does not help either.
Device Manager: Android Device --> Motorola ADB Interface
Any ideas how to fix this issue?
Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson
dzidexx said:
Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson
Click to expand...
Click to collapse
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found
Jonasson said:
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found
Click to expand...
Click to collapse
https://youtu.be/3Q8b0SuGvmI
https://www.google.pl/search?q=inst...1ZHYAhVN2aQKHSi7AoIQ_AUIESgB&biw=1056&bih=660
https://www.google.pl/search?biw=10...k1j0i8i30k1j0i8i13i30k1j30i10k1.0.Pe-SF0MQFkc
Go to movies in google results.
Thanks to all of you. I finally understood how it works. :angel:
Android 7.0 on it :good::victory:
Hi guys,
I did the update with above tutorial to Android Version 7.0. (Android security patch level: 1.September.2017)
But now they ask me to download new Android security updates . (New system software: 25.201.1 (8,0 MB)
Unfortunately when it is doing the restart it shows the error message:
Error!
And it shows a dead Android Robot.
Any ideas what has gone wrong. Not sure why I get the Software-update failure after doing the upgrade successfully from 6.0 to 7.0.
Moto X Pure Edition
Probably you forgot something, I think:
fastboot flash recovery recovery.img
dzidexx said:
Probably you forgot something, I think:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks dzidexx..it does finally work
hello . i need NPH25.200-22-1 android for moto x pure;
any idea?
morvarid said:
hello . i need NPH25.200-22-1 android for moto x pure;
any idea?
Click to expand...
Click to collapse
No full images were ever released/leaked for anything newer than:
Style: NPH25.200-15
Pure: NPH25.200-22
You either need to get one of those to work for you, or move on to something else or a custom ROM. Sorry, but the version you have was never released as am image (that -1 sub version probably never was a full image internal to Moto either, most likely an OTA only) and no later version has ever leaked out. You can stop asking in multiple threads, the answer is the same.
I've spent a few hours searching these forums to learn as much as I can about rooting the OEM variant of the BLU R1 HD smart phone and have come across a handful of guides:
Blu R1 HD Unlock bootloader, install TWRP, and root (Non prime) by lil chickenz
For NONE prime R1HD by mrmazak
[TWRP] How to root ("newbie friendly"!) : by bibikalka
Amazon Blu R1 HD TWRP Recovery and Root Tutorial (https://www.youtube.com/watch?v=KMobKWfZbJg)
I found those guides very helpful but there were spots where the guides glossed over a few things that a new member, like myself, found vague and mysterious. Therefore, for my own personal use, I opted to compile a more thorough list of directions that I can follow when I root my device.
With all that said, as more experienced members, would any of you double check the steps and provide clarification when needed?
Thanks in advance!
(See my next post for my list of directions.)
Disclaimer: This list of instructions is my attempt to comprehend information from a variety of sources on how to root the R1 HD OEM Variant. I'm nearly positive that I'm doing something wrong or another. If I am, and you know the right way, please explain it to me! Thank you!
[SIZE="+2"]Required Software, Drivers, & Files[/SIZE]
MediaTek SP Drivers (https://androidfilehost.com/?w=files&flid=68715) | Install these drivers onto your Windows PC so that you can utilize the SP Flash Tool.
SP Flash Tool (https://androidmtk.com/smart-phone-flash-tool) | Install this application via Windows so that I can backup the ROM, including the partitions, of the unmodified smart phone.
ADB (https://forum.xda-developers.com/showthread.php?t=2588979) | Install this application and drivers using Windows in order to unlock the bootloader and flash the TWRP so that I might root the device.
SuperSu (https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip) | This file needs to be uploaded / downloaded to the smart phone's internal storage aka /sdcard (internal storage). Eventually it will be installed to root the phone.
TWRP Scatter R1 Prime (https://www.mediafire.com/folder/usifl1vdnma1t/BLU_R1_HD) | This file is needed to flash the TWRP onto the smart phone.
[SIZE="+2"]Preliminary[/SIZE]
Ensure that the required software, drivers, and files are installed and placed appropriately.
Power on your smart phone, navigate to Settings -> About then scroll down to and tap Build Number multiple times until you are granted Developer Access.
Enter Developer Settings then enable USB Debugging as well as OEM Unlock.
Power off your smartphone (The battery must be removed to backup the ROM later. Should I remove it now?) then connect it to your computer with the mini-USB to USB cable.
[SIZE="+2"]Enter Bootloader[/SIZE]
On Windows, navigate to the ADB installation directory (Usually C:\adb) then double click on Runme.bat.
When in the shell and prompted type the following case sensitive code to put your smartphone into its bootloader:
Code:
adb reboot bootloader
[SIZE="+2"]Unlock Bootloader & Factory Reset[/SIZE]
Wait until your phone is in the bootloader (The smartphone will display text along the lines of "fastboot...") then, on Windows, type the following case sensitive code to unlock the bootloader and factory reset your smartphone:
Code:
fastboot oem unlock
[SIZE="+2"]Backup ROM[/SIZE]
Now that the bootloader is unlocked, on Windows, open your web browser then naviate to the following guide:
ROM Backup using SP Flash Tool 'Readback' feature by codelover
Follow the directions listed to Backup your ROM replacing 'Honor3C' with 'R1 HD,' and 'MT6582_Android_scatter.txt' with 'MT6735_Android_scatter.txt (Is this accurate?).'
Follow the directions to Process the dumped ROM files to create the SPFT Flashable files.
[SIZE="+2"]Flash TWRP Custom Recovery[/SIZE]
On Windows, extract the TWRP Scatter Prime zipped file into the ADB installation folder (Usually C:\adb).
Flash the custom TWRP by typing the following case sensitive code:
Code:
fastboot flash recovery recovery.img
[SIZE="+2"]Root[/SIZE]
Now that the TWRP is flashed onto your smart phone you may enter into its Recovery mode by pressing the 'Power' and 'Volume Increase' buttons for more than a few seconds. You may have to disconnect the smart phone from the PC first.
Navigate to the Recovery by using the volume button to highlight an option and the power button to select it.
Mount the system partition as read only then backup the partitions (select everything) to the specified storage location (including a SD card).
4. Install the SuperSu from the zipped file that you uploaded to your smart phone's internal storage in the Software, Drivers & Files section (After I wrote this I realized that the file may have been deleted when the phone was factory reset. Reconnect the phone back to the PC and you're able to access the internal and external storage from the PC. Drag the file into internal storage now.)
[SIZE="+2"]Optional[/SIZE]
In order to use apps like ES File Explorer, apps that aren't yet updated to handle system-less root, enter the following case sensitive code (Where am I entering this code? On the smart phone? On the PC using the 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 /
Thanks again for taking the time to review this process and make any clarifications!
Wait! The MOST important thing is checking what version of the ROM you are currently running. If you have updated your phone with an official ROM to version 8.0 or greater (I think that's the version), then you will NOT be able to run SPFT and replace the bootloader as Blu disabled SPFT in the updated ROM. So the most important first step is to find out what ROM you have installed and whether SPFT will even work. If not, you will not be able to replace the bootloader or root.
I am not sure what the equivalent version of the non-Amazon ROM is where they disabled SPFT. Maybe V17?
yaconsult said:
Wait! The MOST important thing is checking what version of the ROM you are currently running. If you have updated your phone with an official ROM to version 8.0 or greater (I think that's the version), then you will NOT be able to run SPFT and replace the bootloader as Blu disabled SPFT in the updated ROM. So the most important first step is to find out what ROM you have installed and whether SPFT will even work. If not, you will not be able to replace the bootloader or root.
I am not sure what the equivalent version of the non-Amazon ROM is where they disabled SPFT. Maybe V17?
Click to expand...
Click to collapse
Thanks for the response, yaconsult. Here's the specs:
Android Version | 6.0
Baseband Version | MOLY.LR9.W1444.MD.LWTG.MP.V79.971
Kernal Version | 3.18.19+
Build Number | MRA58K
Custom Build Version | BLU_R0011UU_V21_GENERIC
BLUper said:
Thanks for the response, yaconsult. Here's the specs:
Android Version | 6.0
Baseband Version | MOLY.LR9.W1444.MD.LWTG.MP.V79.971
Kernal Version | 3.18.19+
Build Number | MRA58K
Custom Build Version | BLU_R0011UU_V21_GENERIC
Click to expand...
Click to collapse
Having your build number as V21, I am affraid you are stuck, without possiblity to unlock bootloader, so no flashing custom recovery with fastboot mode. Or modified root enabled boot.img
Also with build #V21, no possible method to connect with spft to flash custom recovery. Or modified root enabled boot.img.
With these restrictions, all the past information you have gathered will do you no good. Sorry. BLU has locked you down
mrmazak said:
Having your build number as V21, I am affraid you are stuck, without possiblity to unlock bootloader, so no flashing custom recovery with fastboot mode. Or modified root enabled boot.img
Also with build #V21, no possible method to connect with spft to flash custom recovery. Or modified root enabled boot.img.
With these restrictions, all the past information you have gathered will do you no good. Sorry. BLU has locked you down
Click to expand...
Click to collapse
Thanks for your hasty response, MrMazak. The information that I gathered isn't too complete a loss - I was able to learn more about and have a greater understanding of the root process.
Is there a part of the XDA forums where I might ask around, or dig through, to find smart phones in the $100 USD range that are still root-able?
BLUper said:
Thanks for your hasty response, MrMazak. The information that I gathered isn't too complete a loss - I was able to learn more about and have a greater understanding of the root process.
Is there a part of the XDA forums where I might ask around, or dig through, to find smart phones in the $100 USD range that are still root-able?
Click to expand...
Click to collapse
Not specific page or thread, but a general search of the full forum would be a good start
So I'm confused, these BLU phones or which phones or all phones cannot be rooted any more? I have the BLU R1 PLUS and it doesn't even have a Developer option for unlocking the firmware ( BLU_R0051UU_V13_GENERIC 14-03-2017 10:40). Of course I cant run an oem unlock either.
How does anyone reload an image onto them if they can't be rooted? Thanks!
Donphillipe said:
So I'm confused, these BLU phones or which phones or all phones cannot be rooted any more? I have the BLU R1 PLUS and it doesn't even have a Developer option for unlocking the firmware ( BLU_R0051UU_V13_GENERIC 14-03-2017 10:40). Of course I cant run an oem unlock either.
How does anyone reload an image onto them if they can't be rooted? Thanks!
Click to expand...
Click to collapse
your device is different than the R1-HD
the plus (afaik) is not able to be unlocked, means no twrp, and probably no root.
I had this same device in hand for 3 weeks, and could not get anywhere with root.
maybe someone else has had more luck.
this is another thread that i respnded to for the device too.
https://forum.xda-developers.com/r1-hd/help/rooting-r0051uu-t3795795
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
akhil520c said:
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using Tapatalk
If you can't install TWRP on pie, try reverting to Oreo with AFT and then flash TWRP in fastboot. Also make sure you have unlocked the bootloader whether by the official tool or the unofficial method. THIS WILL DELETE ALL DATA SO BACK UP.
Thanks arko. Is there Asus Flash Tool available for Linux also? Will try and revert. Thanks :svetius
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
akhil520c said:
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
Click to expand...
Click to collapse
Windows 10 ? Its bcuz Driver Signature Enforcement
Disable it and reinstall adb and fastboot drivers, it will work for sure.
Windows driver security wouldn't accept drivers without proper Signatures,so like i said, just disable it and you are good to go.
:good:
Tried steps you mentioned, doesn't work. In fastboot mode, #fastboot devices gives me no output. Looks like my pie ROM is buggy. Basically, I need to install lineage on the phone.
Hi all,
Finally got everything done in about 5 mins I booted up Ubuntu Mate (32 bit) on my other laptop, and found I'd already installed adb and fastboot on it from the repositories (not from google). I booted my phone in fastboot mode, and tried the #fastboot devices command, and voila, my phone got detected! After that, it was a matter of a few minutes, following the installation instructions (of twrp and lineage) from the lineage website. Thanks for all your inputs and help
P.S: I realised (again), after more than 2 decades, that windoze mighty sucks lol.