Hi there!
I'm newby with android and unlocking the device. My device ZTE Axon 7 A2017G
I want a device running on Lineage os. So I try since 3 days to backup and flash the recovery with axon7tool.
I get always the error message: failed to connect.
I try to install the driver with zadig and now i see the Q...BULK device but still become this error...
I was on android 7.1 B01 and now have downgraded to android 6.0.1 (A2017GV1.0.0B10)
Still the same error.
I changed the computer, still this stupid error.
Can anybody help me, I'm frustrated...
I had this issue and solved it by showing all file extensions in windows. When you rename the recovery.img to recovery.bin you have to make sure that it's actually an BIN file and so you need to have show all file extensions on in the windows settings.
thanks for your answer.
I'm realy shure that I have activated this option, because of other development stuff
Even the first command in each tutorial is not working: "axon7tool -r gpt boot recovery"
When I disconnect my axon and then run the command again I become this error: "Device not connected/found, Failed to connect"
So this means, if I connect the device and I see only the error: "Failed to connect"
the axon7tool see my device but can't connect to them?
p.s. after the downgrad from android 7.1 to 6.0.1 I don't see any updates such as android 7 and I haven't a connection to mobile data (3G/4G). Very frustrated when I want to use whatsapp outdoor
Sorry. I don't know what your issue is then. I'm sure someone else here can help you.
Do you have then Qualcomm drivers installed? If not, try this: QUD.WIN.1.1 Installer-10039.2.zip
If it's still not detected, use the Zadig Tool found here
I had a similar issue. You have to grant admin rights when opening a command window.
Send from ZTE A2017G using Tapatalk
KwesiJnr said:
Do you have then Qualcomm drivers installed? If not, try this:
If it's still not detected, use the Zadig Tool found
Click to expand...
Click to collapse
thank you. What should I select in the wizard when he ask me for the following:
Please choose between WWAN(NDIS6.20) and ETHERNET(NDIS 5.1)
- WWAN-DHCIP is not used to get IPAddress
- ETHNER-DHCP is used to get IPAddress
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
KwesiJnr said:
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
Click to expand...
Click to collapse
oh wow! One step further.
The tool waits a second an then I see this error:
C:\Users\bearbeer\Downloads\adb>axon7tool -r boot
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
I dont understand the message.
bearbeer said:
oh wow! One step further.
The tool waits a second an then I see this error:
I dont understand the message.
Click to expand...
Click to collapse
Good, reboot your device into EDL mode once more and try again.
KwesiJnr said:
Good, reboot your device into EDL mode once more and try again.
Click to expand...
Click to collapse
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
bearbeer said:
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
Click to expand...
Click to collapse
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
KwesiJnr said:
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
Click to expand...
Click to collapse
thanks again. It works!
What's the next step to become lineageos running on my device? Download and install lineageos or do I need something else before?
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
KwesiJnr said:
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
Click to expand...
Click to collapse
Ok I have flashed the TWRP Recovery (not the latest because the latest boot not up) and unlocked the bootloader. What's the Nougat Bootstack and how do I install it?
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
KwesiJnr said:
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
Click to expand...
Click to collapse
What's the best way to upgrade the twrp?
bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
0. Reboot to TWRP, then copy the desired Recovery Image file you want to upgrade to, (e.g. twrp-3.1.0.0-ailsa_ii.img) to your Internal Storage.
1. Tap Install Image from the lower right corner. Proceed to select the recovery image you just copied to your device.
2. You should now see a radio list. Select Recovery, then swipe to flash.
3. Reboot.
That is all.
Alternatively, you can flash the recovery upgrade file via fastboot, like you did the older version. Just make sure you flash the older version first, THEN the newer. Should work like a charm.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
metpolds said:
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
Click to expand...
Click to collapse
Lmao. I feel you, bro. Pretty convinced he's new to these forums as you guessed, and I'm sure he likely doesn't know about the 'Thanks' system. You know, benefit of the doubt and all.
Ultimately, I just wanted to help out. I know how frustrating it can be with these things so...
Thank you! Ok I'm now on "twrp-3.1.0-0-ailsa_ii.img" and it works.
Yes this is correct. I don't saw the "thanks" button...
I'm so happy that all of you help me. As a newby there are so many threads, tuts, ... an everywhere all goes right. But on my device nothing works at first try. Thank you a lot! :good: :laugh:
Related
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.
Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.
Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...
iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.
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=Blu R1 HD Amazon . 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/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_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=Blu R1 HD Amazon ( 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/showpost.php?p=67890586&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 !!!!!
Is it weird I didn't have to install any drivers when I did this?
triggerlord said:
Is it weird I didn't have to install any drivers when I did this?
Click to expand...
Click to collapse
You prob had them from some times before ? Do you have other MTK devices ?
triggerlord said:
Is it weird I didn't have to install any drivers when I did this?
Click to expand...
Click to collapse
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.......
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
triggerlord said:
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
Click to expand...
Click to collapse
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.
limpet said:
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.
Click to expand...
Click to collapse
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.
ariesgodofwar said:
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.
Click to expand...
Click to collapse
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.
Clicked on MTP in USB configuration. No notification, but about 30 seconds of disk activity. Device list changed to this.
ADB was happy.
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
pathia said:
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
Click to expand...
Click to collapse
What does >adb devices return?
pathia said:
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
Click to expand...
Click to collapse
See this post for detailed instructions: http://forum.xda-developers.com/showpost.php?p=67891724&postcount=549
The drivers found here: https://androidmtk.com/install-android-cdc-driver-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.
It works on Linux too using the latest version of Linux SP Flash Tools.
ariesgodofwar said:
See this post for detailed instructions: http://forum.xda-developers.com/showpost.php?p=67891724&postcount=549
The drivers found here: https://androidmtk.com/install-android-cdc-driver-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.
Click to expand...
Click to collapse
Nevermind! Got it to work, I just kept trying over and over again, then tried another laptop and it seemed a little more happy with that one.
Awesome work folks!
I'm from the UK , is this phone same as the BLU Life Mark?
And how do I check if I have a prime version or not
can somebody please tell me what i am doing wrong. no scatter files
---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------
can someone please tell me what i am doing wrong, downloaded drivers. SP Flash Tools V. 1628 but when i launche no scatter files. thanks in advance
johnnybabble87 said:
can somebody please tell me what i am doing wrong. no scatter files
---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------
can someone please tell me what i am doing wrong, downloaded drivers. SP Flash Tools V. 1628 but when i launche no scatter files. thanks in advance
Click to expand...
Click to collapse
The scatter file is provided together with TWRP, see the link in the post #1 for details. Then just choose the scatter file, and it'll load the TWRP image there.
anyone tried xposed yet?
im interested in this device mostly because it a steal at this price point and now this is rooted, i'd like to know if xposed is working on this?
AshokMarannan said:
im interested in this device mostly because it a steal at this price point and now this is rooted, i'd like to know if xposed is working on this?
Click to expand...
Click to collapse
Yeah, there's another thread on how to install Xposed.
Sent from my BLU R1 HD using XDA Labs
---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------
jediknight111 said:
I'm from the UK , is this phone same as the BLU Life Mark?
And how do I check if I have a prime version or not
Click to expand...
Click to collapse
They have the same SoC but they're not the same device.
Sent from my BLU R1 HD using XDA Labs
triggerlord said:
Is it weird I didn't have to install any drivers when I did this?
Click to expand...
Click to collapse
Well, one things for sure.
Big brother windows 10 seems to have added mtk drivers to windows update.
MFW it's probably on the 1411 update.
This says whether im 8gb or 16gb im good?
You guys are doing the lords work.
Help!!!
I reached step 8 and realized I have not copied supersu.zip to the phone. So I rebooted the phone and copied supersu.zip to internal SD card. Here came the problem. I CANNOT enter into TWRP after that. It showed "no command"! Then I pressed power button and volume up button simultaneously and entered into the stock recovery, where I cannot flash supersu.zip.
Anyone can help me figure it out? I tried to re-flash recovery.img with SPFT, but it did not work.
I have the Chinese version of axon 7 and under development options I can click on OEM unlock then it asks for a pin number. How do I get that pin number?
Have you contacted zte customer service?
Please let me know how this turns out
I've been around these forums multiple times now and the ways that should work don't seem to work for me :/ Can't find a confirmed unlock of the Chinese version and am stuck on B13 while I wany Cyanogen.
If you go and sign up for ztes website and then go to the developers lounge there is a lot of talk about bootloader unlock. The way I read it you could have signed up to receive a pin number to unlock bootloader but zte has put that on hold? But are suppose to start it back up?
you can flash unlock bootloader in port 9008, I unlocked successfully by this way
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
enkrs said:
@jiabing520a could you explain how?
after booting into recovery my device isnt visible in the device list from adb.
Click to expand...
Click to collapse
Did you flash twrp ? Official recovery does not support adb.
If you have already flashed twrp, then open computer manager- device manager, you will see your phone doesn‘t work correctly (triangle) , right click on the triangle, and click update driver, then computer will fix this proble automatically.
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
enkrs said:
Can not even get to flashing the TWRP, so stock recovery.
I want to backup the recovery.img in case i brick the device after doing
adb reboot recovery the device cant be found any more in the adb device list so nothing from that.
I tried to sideload it using the adb sideload but the same
it`s saying waiting for device and stays there even when i`m trying to send a file to the device.
Click to expand...
Click to collapse
waiting for device...you should kill adb process first, and then reconnect your pc
---------- Post added at 11:33 ---------- Previous post was at 11:32 ----------
enkrs said:
Ok little update.
tried to downgrade but getting the error footer not correct and unable to verify.
Normaly saying you can disable this using the TWRP system as i cannot even get the bootloader to unlock.
So i cant get TWRP installed on the device.
If anyone knows how to downgrade the b13 to the b10 so we can use the tools provided in other posts
Please help how further .
Click to expand...
Click to collapse
if you want to downgrade the b13 to the b10，maybe you should use official recovery
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
enkrs said:
If you can explain how to downgrade using the original recovery please i have tried sideloading
and placing the rom file in the location reserved for update etc.
Click to expand...
Click to collapse
Hello Mate,
I am in the same situation as you. I have been looking all over the internet and came across a Chinese forum. Apparently, it is possible to unlock and root B13. However, I have used Google translater to translate the page. It's hard to understand the steps. I have not tested it. But maybe someone out there will have a better understanding and could give it a go. Here is the link
http://www.myzte.cn/forum.php?mod=viewthread&tid=320458&mobile=2
Hope that helps
[UPDATE]: USE THIS ONLY FOR NOUGAT 7 OR 7.1! THERE IS A DIFFERENT GUIDE FOR ANDROID OREO!
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502 (Written by YasuHamed, not me!)
If you are not interested in android Oreo, or you want to go back to Nougat, this guide is still valid! [End of Update]
This is a guide for newbies or for people that are simply confused. If you have any questions, you can always ask me, and I will reply. but please make sure you haven't made mistakes and do not ask about things that are already stated here. Let's go!
BEFORE DOING ANYTHING, NOTES
-make sure you have installed ADB : https://forum.xda-developers.com/showthread.php?t=2588979
-make sure ADB can read your phone with the correct drivers installed. If you have trouble with that, read "DRIVERS" section
!It is absolutely necessary to install the drivers correctly!
-Backup your stuff if you have any, you will need to delete everything from the phone
-Enable USB debugging
-Note: some of these instructions apply to Windows OS only!
-Note: links to downloads have been shortcutted as much possible to make it easier for you!
-Find some stock roms here! https://forum.xda-developers.com/xperia-x/how-to/sonyx-f5121-downgrade-8-0-0-to-7-1-1-to-t3754986
(Credit: HEKER510)
-Warning: you will lose your warranty!
-I am not responsible for any damage done to your device.
BACKUP DRM KEYS (OR WORKAROUND)
You may want to unlock your bootloader. If you unlock it without backing up the DRM keys, you will lose them. I did that mistake and I regret it. If you already did, there is an alternative solution, skip to step 8.
1) If you are running android 7 nougat, you will need to downgrade to MM. If you are running MM, skip to step 7.
2) You will need to wipe everything before rolling back, so if you have any data back it up
3) Download any stock MM 6.0.1 firmware for the xperia X. You can find one here : https://mega.nz/#!1xRj2CYS Decryption key: !qBVi7yky8AL84eUF3bpTTGQ2YmN0ePCjc-eSDZGIZCI
Watch out: if you have the dual SIM model, F5122, you need to download accordingly!
For more firmwares, check "BEFORE DOING ANYTHING"
4) Download the latest flashtool: http://www.flashtool.net/downloads.php
Upon installation, tick on fastboot, flashmode drivers! If it didn't ask you, go to the installation folder and run Flashtool-drivers.exe. Please read "DRIVERS" section!
5) Flash the .tft file
How to flash?
0. Go to "C:\Users\[Your PC Name]\.flashTool\firmwares" , and put your firmware .ftf file in there!
1. Open Flashtool and click on the lightning bolt icon (first one from the left)
2. In the prompt, choose flashmode.
3. Under firmware, click on the version you put (It should probably only be one option)
4. Under wipe , tick everything. Under the others, do not make any changes.
5. Click "Flash"
6. When the popup appears, connect your device. It needs to be powered off, and connected while you are holding the
"volume down" button.
7. Wait for it to finish.
8. Done. Boot up the device, it might take some time to open so don't worry.
Click to expand...
Click to collapse
6)If your phone bootloops, try flashing again or a different firmware and make sure you followed the steps correctly.
7) Once your phone successfully boots android MM, use Dirtycow to get your DRM keys out: https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
8) If you unlocked the bootloader before backing up your keys, you can use DRM kernel fix. You can get it here: https://forum.xda-developers.com/xperia-x/development/kernel-drm-fix-nougat-t3530849 Before using it check out the custom rom that includes this fix and other things.
UNLOCK BOOTLOADER
This is relatively easy and you can follow official sony instructions to do it.
1) Go to your phone settings, developer options, and enable OEM unlock
"But there is no developer options!" -Go to the bottom of your settings, system, about phone, and tap multile times on "Build Number", also at the bottom.
Click to expand...
Click to collapse
2) If you haven't already , install ADB fastboot and configure drivers (Link on top )
3) Follow the steps on the Sony website to get your unlock code: https://developer.sonymobile.com/unlockbootloader/email-verification/
4) After unlocking, a warning message on boot is normal!
INSTALL RECOVERY
Installing TWRP on your xperia X is very important, since you can flash zips and img files so easily, plus wipe, backup and other features.
1) Download the TWRP .img file: https://androidfilehost.com/?w=files&flid=197369 (Credit: eagleeyetom )
2) Make sure you have USB debugging enabled
3) Open your downloaded twrp folder
4) Run CMD in that folder (shift + right click inside the folder, Open CMD here )
5) Connect your Xperia X to your PC
6) Type these lines:
adb reboot bootloader
fastboot flash recovery recovery.img [where recovery.img is your twrp file name]
fastboot reboot
7) If no errors, twrp is now installed. Once your phone boots , turn it off,. To access TWRP recovery hold power button and volume down button until the TWRP menu appears.
STOCK ROM, ROOT
If you just want to root and not interested in additional features and tweaks, you can simply flash SU through TWRP to get your phone rooted.
Note: Current best stock ROM available: 7.1.1 (252) - better features than older ver, and good battery life.
0) Install your desired stock firmware using the exact same previous instructions, (under DRM section) with flashtool.
1) Download SuperSu
Or magisk, using YasuHamed guide mentioned on top, but I have not tested with anything other than Oreo 8.0
Use magisk if you want more stability / root features (like hide root from apps, modules )
2) copy it anywhere on your phone
3) Run TWRP
4) Tap on install
4) Flash the file
5) Reboot, you are now rooted
6) Insert your DRM keys if you have them
Custom ROMS
After unlocking the bootloader and installing TWRP this is the best way to go in order to get full root, tweaks.
https://forum.xda-developers.com/xperia-x/development/rom-xperia-x-pexorom-v1-0-0-f5122-f5121-t3590552
^ This is a very good custom ROM made by prmk74. You can see its features in his thread.
1) Download the rom and copy it to your phone
2) Run TWRP
note: It is recommended to wipe dalvik, cache, data ( your storage partition doesn't need to be wiped)
3) Tap install, find your downloaded file and execute
note: It is recommended to wipe dalvik, cache, data ( your storage partition doesn't need to be wiped)
4) Follow on-screen instructions, do not stop the booting after finishing the installation, it will take some time
5) Insert your DRM keys if you have them
6) For those who lost their keys: Now the functions like vivid image mode are working properly.
DRIVERS
For Windows 8/8.1/10 users, how to solve driver problems:
1) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers. Go to the flashtool install location and run the drivers.exe again, check fastboot and flashmode
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine
TO CONCLUDE:
This is what you may want to do to get the most out of your new xperia x:
1) Backup DRM
2) Unlock BL
3) Install TWRP
4) Flash Persian (or a different rom) through TWRP (And subscribe to the thread so you receive updates)
5) Restore DRM
Notes:
None of the links, tools are of my work, I'm just writing a guide for my fellow XX owners
^^ this guide is so really good :3. I post flash script for someone dont know how to find it ^^
unzip it in this position.
C:\Users\[user-name]\.flashTool\mydevices
max26292 said:
^^ this guide is so really good :3. I post flash script for someone dont know how to find it ^^
unzip it in this position.
C:\Users[user-name]\.flashTool\mydevices
Click to expand...
Click to collapse
Thanks!
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
brianx87 said:
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
Click to expand...
Click to collapse
These USB drivers are very annoying to work with. I got mine to finally work using a program called ADB driver installer. http://adbdriver.com/downloads/ Choose automated installation and try what I said. I believe it should fix your problem, after installing the drivers reboot and flash again.
Other than that, I have to ask are you 1000% sure you used the exact commands?
I saw another thread someone mistook
"flash recovery recovery.img" for "flash recovery.img"
"recovery" should be included before the recovery file name
brianx87 said:
Thanks for this, I need some help!
All was fine until I tried flashing the recovery, comes back "partition unknown" error. I was unable to bring the device up under an adb device only as a fastboot device.
34.0.A.1.264_R3A firmware.
Different official sony driver (Sony bootloader guide driver didn't work)
Device now hangs on the Sony logo after boot messgae warning "OEM bootloader unlocked, device not trusted," any help would be appreciated.
Click to expand...
Click to collapse
Why didn't the sony guide work? It worked for me. Just so you know, the "device cant be trusted" message is appearing on everyones' phones after unlocking the bootloader, it's not a problem or something
the part of restoring DRM is skipped,
please xplain
YasuHamed said:
the part of restoring DRM is skipped,
please xplain
Click to expand...
Click to collapse
I know, as I said there is room for improvement. The reason I did not include it is because I never did it myself, so I don't want to write something wrong or something that could lead to problems. I write something only if I am 100% sure. If anyone of you is kind to offer that piece so the guide is complete I will be glad
FoxTheLegend said:
Why didn't the sony guide work? It worked for me. Just so you know, the "device cant be trusted" message is appearing on everyones' phones after unlocking the bootloader, it's not a problem or something
Click to expand...
Click to collapse
Ok I figured out what I did wrong and was able to amend another issue I edited out of this post.
brianx87 said:
Ok I figured outwhat I did wrong (able to boot into the os and warning message no longer an issue ) and the issue I am now facing is that twrp is hanging on the boot screen. Is this version of twrp built to a specific version of android?
Click to expand...
Click to collapse
What do you mean hanging? the twrp logo frozen?
FoxTheLegend said:
What do you mean hanging? the twrp logo frozen?
Click to expand...
Click to collapse
Working now, used a previous version of twrp by mistake. Using latest build works fine now, have to wait to get home from work to proceed with the rest, annoying procedures this stuff but your guide is great.
brianx87 said:
Working now, used a previous version of twrp by mistake. Using latest build works fine now, have to wait to get home from work to proceed with the rest, annoying procedures this stuff but your guide is great.
Click to expand...
Click to collapse
Thanks, Im glad to it works now
FoxTheLegend said:
I know, as I said there is room for improvement. The reason I did not include it is because I never did it myself, so I don't want to write something wrong or something that could lead to problems. I write something only if I am 100% sure. If anyone of you is kind to offer that piece so the guide is complete I will be glad
Click to expand...
Click to collapse
thank you for the answer sir
i am unable to find any twrp that work for my F5122, it always bricks and i have to reset.
is there any twrp recovery image that works correctly with f5122?
YasuHamed said:
thank you for the answer sir
i am unable to find any twrp that work for my F5122, it always bricks and i have to reset.
is there any twrp recovery image that works correctly with f5122?
Click to expand...
Click to collapse
Hmm.. Did you try the one from the poison thread? I myself have still the old version installed (not 3 or 3.1) if I find it on my pc I will share it with you
FoxTheLegend said:
Hmm.. Did you try the one from the poison thread? I myself have still the old version installed (not 3 or 3.1) if I find it on my pc I will share it with you
Click to expand...
Click to collapse
I have to modified kernel
all i want is to boot it via fastboot command
for example i have the rooted kernel SU installed (but battery drain is high) so i what wana do is flashing kernel with all securities OFF and then with twrp image i will do
Code:
fastboot boot twrp.img
i will boot the X in to twrp and i will flash SUPERSU via twrp.
thanks all
YasuHamed said:
I have to modified kernel
all i want is to boot it via fastboot command
for example i have the rooted kernel SU installed (but battery drain is high) so i what wana do is flashing kernel with all securities OFF and then with twrp image i will do
i will boot the X in to twrp and i will flash SUPERSU via twrp.
thanks all
Click to expand...
Click to collapse
I see, but don't you want to figure out why it's not working normally? Noone has reported a similar problem
FoxTheLegend said:
I see, but don't you want to figure out why it's not working normally? Noone has reported a similar problem
Click to expand...
Click to collapse
since there is no offcial twrp for X out yes and only DORA (XA) is available) even XA don't work for X
so either twrp 2.8, 3.0 or 3.1 any should just boot in order to let us flash superSU.
YasuHamed said:
since there is no offcial twrp for X out yes and only DORA (XA) is available) even XA don't work for X
so either twrp 2.8, 3.0 or 3.1 any should just boot in order to let us flash superSU.
Click to expand...
Click to collapse
=-= try to use this command fastboot flash recovery [your_recovery_name].img
I use f5122 and flash successfull twrp 3.0.2 and 3.1. with this, i flash some kernel and rom without any problem.
Everything is working good for me now, the only issue now is restoring the DRM keys, has anyone found a credible source for doing this on this device?
How can I be sure I have a full root? I can't seem to be able to uninstall some of the bloatware only disable it!
brianx87 said:
Everything is working good for me now, the only issue now is restoring the DRM keys, has anyone found a credible source for doing this on this device?
How can I be sure I have a full root? I can't seem to be able to uninstall some of the bloatware only disable it!
Click to expand...
Click to collapse
Well titanium backup can assure you but I don't see why you wouldn't have full root... You need an app uninstaller to uninstall bloatware, it can't be done through the settings you know that right
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?