Database Users

[GUIDE] XT1030 w/ Unlocked Bootloader and Root for $185

If this helps anyone, great. If not, sorry, I tried. I intentionally left some of the details out to keep it short, but I can expand items upon request.
I just bought my third Droid Mini (XT1030); I fell into a river with the first one, and the second one had a nasty failure with the headset detection circuit. I love this phone and can't find one that compares.
I'm by no means a power user, but I cannot live with a phone without root (and an unlocked bootloader is huge). I struggled to find the necessary information to take me back to the same state I was in with my previous phones and felt like a simplified, updated thread would help. The biggest problems I had was with dead links, scattered information, and more [confusing] information than necessary.
Disclaimer: The guide below will take you to KitKat 4.4. I realize you can go to 4.4.4 with no problems once you'll have an unlocked bootloader, but I had no interest. Also, most of this guide applies to the XT1060 and XT1080 (the filename in step 4 will be different, and I'd imagine they'll cost you a bit more).
1) Buy new phone with original Android 4.2.2 for $160 (http://www.amazon.com/Motorola-Veri...p/B00HE5FBPS/ref=cm_cr_pr_product_top?ie=UTF8)
- Note: If the phone has been updated to 4.4.4, I think you're hosed!
2) Power up phone
3) Download Sunshine to automatically unlock bootloader (costs $25; http://theroot.ninja/apks/SunShine-latest.apk)
4) Download KitKat 4.4 (google the filename: CFC-fastboot-obakem_verizon-user-4.4-SU2-3-15-release-keys.xml.zip)
5) Install Motorola drivers for PC (https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/95592/p/30,6720,8881)
6) Install RSD Lite 6.1.5 (http://rsdlite.com/RSDLite6.1.5.msi)
7) Plug your phone into your computer
8) Flash KitKat 4.4 (I felt no need to go newer)
- Power down the phone
- Boot into fastboot by holding the Power button and Volume Down for 10 seconds, then release the power button
- Flash the file using RSD Lite
9) Install Android SDK Tools for fastboot command line utility (http://dl.google.com/android/installer_r24.4.1-windows.exe)
10) Download TWRP (google the filename: twrp-2.6.3.1-ghost-4.4.img)
11) Flash TWRP
- Boot into fastboot
- Open a command prompt window
- Enter the command "fastboot.exe flash recovery twrp-2.6.3.1-ghost-4.4.img" (fastboot should be in "C:\Users\<Username>\AppData\Local\Android\sdk\platform-tools")
12) Run TWRP to get root
- Boot into fastboot, then select recovery (TWRP will load)
- Exit TWRP and it will ask if you want root (say yes!)
13) Follow Topsnake's perfect instructions to get native WiFi tethering (http://forum.xda-developers.com/showthread.php?t=2578410)
14) Disable OTA's (Over The Air updates, since these will fail unless you revert the native tethering changes)
- Launch Jrummy's Root Explorer
- Navigate to "system/priv-app/" and rename "3c-ota.apk" to "3c-ota-apk.bak"
Optional: Download Titanium Backup. This tool is great to restore games (like my Candy Crush boosters and DH 2016 progress). My old phone was alive enough to make backups, copy to the new phone, and restore.

Or you could buy one of the 3 unlocked ones I have for sale on swappa. 2 maxx's and 1 ultra
Sent from my XT1575 using Tapatalk

brownguy73 said:
Or you could buy one of the 3 unlocked ones I have for sale on swappa. 2 maxx's and 1 ultra
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Heh, I got my second phone that way, also on Swappa, but I gave up on a Droid Mini the 3rd time around after about a week of searching for one with no luck. But you're right, if you have this option, it'll save you quite a bit of time and might be worth it. I'm hoping this one lasts me another couple years until a better option comes around, so I'm pretty happy I got a brand new phone. I have no interest in a newer model unless someone comes out with a phone that is rootable and less than or equal to 4.8" in length (otherwise it won't fit in my breast pocket of the Wrangler snap shirts I wear, which is a big deal for me).

I could get the Mini for 8 dollars plus tax with promo code UPGRADE, however, the SUNSHINE app requires $25 that it is too expensive for a 3-yr old phone.

I hate to get rid of my Mini (best phone ever when it comes to size and features) but it will be going on Swappa soon, sunshine unlocked bootloader.

Phone Bricked Can Someone Help?

This method here seemed pretty straightforward to upgrade to Nougat: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
I was already unlocked so I figured I just need to flash the "Full" package then the "TWRP" package. TWRP is working, the bootloader still shows as unlocked in fastboot mode, but trying to boot just shows a Linux penguin and nothing else!
I just cleared everything in TWRP to see if that was somehow the issue then reboot, and TWRP says no OS installed! HOW?!
All this happened because I'm unclear on everything, and instead of a yes/no answer I get mocked. Someone please help.

Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.

tester2017 said:
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
Click to expand...
Click to collapse
I have access to fastboot mode. However I'm still confused as to what is going on.
At least I've figured out where it goes wrong, at the TWRP step. The "no OS detected" made no sense so I tried flashing using the same method but just the "Full" package first. It eventually does boot and it appears Android 7 is working.
The bootloader shows as unlocked. However when I install the TWRP package after, TWRP is restored but then the phone is bricked and TWRP says no OS detected. I'm not sure if this is because I clicked "allow modifications" and if so why that causes it to go wrong and what I missed. I tried flashing TWRP manually using fastboot mode in case something was wrong with that EDL package, and the result is the same, after installing TWRP and clicking allow modifications the OS is no longer detected.
What am I missing? I must have missed a step.

ok. go to twrp and format data to ext 4 then flash new and restart.

tester2017 said:
ok. go to twrp and format data to ext 4 then flash new and restart.
Click to expand...
Click to collapse
When go to "Format Data", enter yes to allow it, it fails and says:
"mkfs.f2fs -t 0 /dev/block/sda9 process ended with
ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption
Upadting partition details...
Failed to mount '/data' (device or resource busy)
... done"
Even if that went through I'm unsure what you mean flash new? Flash a new what?
When I enter repair/change it says the file system is ext4 anyway.

Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.

Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.

Cyrus D. said:
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Click to expand...
Click to collapse
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
This is clearly posted in the TWRP thread.

flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
Thanks, already read the TWRP thread and found what I was missing.
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Edit: Just to be clear, for step 2, when I said "or you can flash it from Fastboot" I meant TWRP in general, not the TWRP EDL package.

Cyrus D. said:
Thanks, already read the TWRP thread and found what I was missing.
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Click to expand...
Click to collapse
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications. ???

romeoh said:
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications.
Click to expand...
Click to collapse
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.

Cyrus D. said:
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Click to expand...
Click to collapse
Omg bro, To be honest I hate the software experience on that phone. It is the only thing that turning me off from it. I played a little with my brother's S7 edge the other day, and believe me the software experience is extraordinary. However I noticed that the S7 edge overheats a lot too without even using the daydream. In my opinion I think Axon 7 lacks in hardware wise a bigger battery and the support of the new RCS messaging feature, and in software wise a whole new developed system.

New Axon 7 Owner Here! - A Few Questions Relating to Screen and Software Problems

Hello!
New Axon 7 owner here, since Thursday! I had a couple of questions relating to this phone and thought it would be best to ask here since i'm already familiar with XDA from previous devices. First of all, I noticed that sometimes text on the screen will occasionally appear like it is vibrating, juddering or blurring for a couple of milliseconds whilst scrolling, as the page is moving either upwards or downwards. It seems to happen at random and it does not appear to have a connection with the colours or content being displayed.
I read on one website that it might be due to the pixels in the AMOLED display turning off momentarily when black is displayed on the screen, however, it cannot be the cause of the problem in this instance because it happens when there is no black displayed, for example in Boost for Reddit which uses a colour scheme of white text on a navy-blue background. I found that the issue seems to happen more often when flicking/flinging the page to scroll, rather than keeping my finger on the screen whilst scrolling through the content.
Has anyone else experienced the same thing and can comment on whether it is normal behaviour for this device? I have not owned an AMOLED device before, and so don't know whether this is typical for devices with this type of display. It could of course be a software issue; but it strikes me as more of a hardware-related matter. I would assume it is probably completely normal, since the phone is otherwise perfect and was fully tested prior to being shipped. :fingers-crossed:
Also...
The phone came from a Chinese reseller on AliExpress who exported the phone to myself in the United Kingdom. The device is a A2017 with the China Mobile branding on the back of it, but the phone has in their words been 'converted' to A2017G spec and is running the A2017GV1.2.0B01 ROM. (MiFavor UI v4.2 based on Nougat 7.1.1) The baseband version is TH.2.0.c1.9-00104-M8996FAAAANAZM. I have checked for OTA updates but it is showing the software as fully updated. When the phone is plugged into my Windows 10 PC it shows as 'ZTE A2017G'.
I am wondering whether this 'conversation' includes anything other than switching to the A2017G Global ROM that would need to be kept in mind when modifying software on the device. Like, would it be safe to follow the usual tutorials for flashing software for the A2017, or should I be looking at tutorials for the A2017G instead?
I would like to unlock the bootloader, install TWRP, flash the latest MiFavor UI v5.0 ROM and root it with Magisk, but i'm not sure where to start with this since none of the tutorials seem to cover phones which have been 'converted' to the A2017G firmware. I saw a warning in the Axon7Toolkit thread, saying that some A2017G models may be permanently bricked when flashing packages through EDL mode due to slightly different partition tables. I don't know whether this is something I should be worried about with my A2017 since it has been converted to A2017G status.
If anyone kindly offer some further insight on either of these points, it would be most appreciated. Thanks a lot.

P650SE said:
Hello!
New Axon 7 owner here, since Thursday! I had a couple of questions relating to this phone and thought it would be best to ask here since i'm already familiar with XDA from previous devices. First of all, I noticed that sometimes text on the screen will occasionally appear like it is 'vibrating' or juddering for a matter of milliseconds whilst scrolling, as the page is moving either upwards or downwards. It seems to happen at random and it does not appear to have a connection with the colours or content being displayed.
I read on one website that it might be due to the pixels in the AMOLED display turning off momentarily when black is displayed on the screen, however, it cannot be the cause of the problem in this instance because it happens when there is no black displayed, for example in Boost for Reddit which uses a colour scheme of white text on a navy-blue background. I found that the issue seems to happen more often when flicking/flinging the page to scroll, rather than keeping my finger on the screen whilst scrolling through the content.
Has anyone else experienced the same thing and can comment on whether it is normal behaviour for this device? I have not owned an AMOLED device before, and so don't know whether this is typical for devices with this type of display. It could of course be a software issue; but it strikes me as more of a hardware-related matter. I would assume it is probably completely normal, since the phone is otherwise perfect and was fully tested prior to being shipped. :fingers-crossed:
Also...
The phone came from a Chinese reseller on AliExpress who exported the phone to myself in the United Kingdom. The device is a A2017 with the China Mobile branding on the back of it, but the phone has in their words been 'converted' to A2017G spec and is running the A2017GV1.2.0B01 ROM. (MiFavor UI v4.2 based on Nougat 7.1.1) The baseband version is TH.2.0.c1.9-00104-M8996FAAAANAZM. I have checked for OTA updates but it is showing the software as fully updated. When the phone is plugged into my Windows 10 PC it shows as 'ZTE A2017G'.
I am wondering whether this 'conversation' includes anything other than switching to the A2017G Global ROM that would need to be kept in mind when modifying software on the device. Like, would it be safe to follow the usual tutorials for flashing software for the A2017, or should I be looking at tutorials for the A2017G instead?
I would like to unlock the bootloader, install TWRP, flash the latest MiFavor UI v5.0 ROM and root it with Magisk, but i'm not sure where to start with this since none of the tutorials seem to cover phones which have been 'converted' to the A2017G firmware. I saw a warning in the Axon7Toolkit thread, saying that some A2017G models may be permanently bricked when flashing packages through EDL mode due to slightly different partition tables. I don't know whether this is something I should be worried about with my A2017 since it has been converted to A2017G status.
If anyone kindly offer some further insight on either of these points, it would be most appreciated. Thanks a lot.
Click to expand...
Click to collapse
Look, first of all, I never had that problem, but it would be best if you recorded the phone with 60fps or something so that we can see what you mean. I don't really get the thing you're talking about
You should install A2017 firmware on your phone instead of using the G firmware, because:
-You won't get OTAs
-MiFavor 5.0 is pretty damn awesome
-Maybe the screen stuff will get fixed
First of all, go to Display and try to disable "Adaptive Display" which is a good idea but really badly implemented for some reason. If the display stuff gets fixed, you may as well not RMA it, and you can install the Chinese stuff on it. You're gonna lose all your data so back it up.
First download an official ZTE update zip. I think I've sent one to someone not much ago, I'll try to find it and put the link here
Then check if there's another zip inside. If there is, get that zip out (should be called update.zip) and throw it in the root of the internal storage
Go to Settings - Updates, and see if it detects it. if it does, install it.
After having the Chinese firmware, delete the zip from your phone, and go to Updates, and see if you get any OTAs. if you get one, after it gets installed go there again, because sometimes they are just incremental (you might have to do this 2-3 times depending on which version you install via zip)
This way you don't have to unlock the phone's BL. After having MiFavor 5.0 set up, download the Google apps if you want (I recommend Google Installer apk by Xiaomi, google it) and you're good to go.

Choose an username... said:
Look, first of all, I never had that problem, but it would be best if you recorded the phone with 60fps or something so that we can see what you mean. I don't really get the thing you're talking about
You should install A2017 firmware on your phone instead of using the G firmware, because:
-You won't get OTAs
-MiFavor 5.0 is pretty damn awesome
-Maybe the screen stuff will get fixed
First of all, go to Display and try to disable "Adaptive Display" which is a good idea but really badly implemented for some reason. If the display stuff gets fixed, you may as well not RMA it, and you can install the Chinese stuff on it. You're gonna lose all your data so back it up.
First download an official ZTE update zip. I think I've sent one to someone not much ago, I'll try to find it and put the link here
Then check if there's another zip inside. If there is, get that zip out (should be called update.zip) and throw it in the root of the internal storage
Go to Settings - Updates, and see if it detects it. if it does, install it.
After having the Chinese firmware, delete the zip from your phone, and go to Updates, and see if you get any OTAs. if you get one, after it gets installed go there again, because sometimes they are just incremental (you might have to do this 2-3 times depending on which version you install via zip)
This way you don't have to unlock the phone's BL. After having MiFavor 5.0 set up, download the Google apps if you want (I recommend Google Installer apk by Xiaomi, google it) and you're good to go.
Click to expand...
Click to collapse
Thanks for the response, I appreciate you taking the time to respond to my questions. I will try to record the screen problem over the next few days just so everyone can see for themselves what is happening; it might be easier than trying to explain it. In regards to the update to MiFavor v5.0, i'm just a bit nervous about flashing stuff through the stock recovery considering the phone has already been messed about with. It would actually feel safer to flash the entire phone in MiFlash on my computer, rather than just trying to install over the A2017G firmware and hoping for the best. I wouldn't mind having to unlock the bootloader because it's what i'd like to do anyway, since i'm interested in rooting to get things like AdAway which I have used on all of my previous devices. But I will have a search around for that official update ZIP anyway and see whether i'm able to find it.

Just got what you said and tried it. You're right it blurs when I fling to scroll. But this happens on LCD screens too.

Aj-jss said:
Just got what you said and tried it. You're right it blurs when I fling to scroll. But this happens on LCD screens too.
Click to expand...
Click to collapse
Well, if someone else is also having the same issue then that would make me feel a bit better about it, assuming we are talking about the same thing of course. I will try to record a video of the problem over the next couple of days, as it would be clearer than trying to explain it in writing. I should note that the blurring effect only lasts for a few milliseconds (Less than the duration of the fling!) and it only happens once in every 20 swipes or so. But when it does happen it can be quite distracting. I have owned 4 IPS devices before this (OnePlus One, LG G4) and none of them have had scrolling behaviour like the Axon 7.
I have also found the scrolling on this phone in general to be a lot less smoother than my ZUK Z2 which uses a 5.0" IPS screen and SD820. It seems the momentum each swipe has in propelling the page vertically is a lot less effective, and thus it takes more swipes to scroll down to the end of a page. Maybe this is because the screen is 5.5" opposed to 5.0" and so, it requires longer 'flings' or swipes on the screen to make up for the additional space. But this theory seems like a long shot and it still does not explain why the scrolling in general feels so laggy and stuttery.

The thing I saw on my two phones including Axon7 happens with every fling or swipe. Maybe I didn't quite understand you . Try to record and send the video so I get what you mean.

P650SE said:
Well, if someone else is also having the same issue then that would make me feel a bit better about it, assuming we are talking about the same thing of course. I will try to record a video of the problem over the next couple of days, as it would be clearer than trying to explain it in writing. I should note that the blurring effect only lasts for a few milliseconds (Less than the duration of the fling!) and it only happens once in every 20 swipes or so. But when it does happen it can be quite distracting. I have owned 4 IPS devices before this (OnePlus One, LG G4) and none of them have had scrolling behaviour like the Axon 7.
I have also found the scrolling on this phone in general to be a lot less smoother than my ZUK Z2 which uses a 5.0" IPS screen and SD820. It seems the momentum each swipe has in propelling the page vertically is a lot less effective, and thus it takes more swipes to scroll down to the end of a page. Maybe this is because the screen is 5.5" opposed to 5.0" and so, it requires longer 'flings' or swipes on the screen to make up for the additional space. But this theory seems like a long shot and it still does not explain why the scrolling in general feels so laggy and stuttery.
Click to expand...
Click to collapse
Did you root your phone? Do you intend to? If you do, you can use the conservative governor and fix the lag entirely. Many people believe that the conservative governor is laggier than interactive, but on the SD820 that's not the case. I've tried on SD6xx and 4xx devices (the Moto G2 and G4+ namely) and this is clearly not like this on those phones.
As for the fling thing, well I'd like to see a video, since I never noticed such a thing. I'm on MiFavor 5.0 so maybe something has been changed, because this is Chinese firmware (on the G).
And I believe that you have to fling more because ZTE may have messed up with some files, as they always did... probably not because of the bigger screen
But really, change your firmware to stock A2017. It's completely possible to have Google apps on it, but retailers install the G firmware on tbe Chinese just because they sell it to the global market
Here you go: Download this, and after you have the zip, open it with a zip manager such as winrar or 7zip. If you see a PDF and an update.zip inside, pull the update.zip out and put it in the root of the internal storage, then install it via Settings - Updates. If not just put the zip you downloaded on the root if the internal storage. but i think that zip actually has the other one inside.
https://archive.org/download/A2017B1320161104135351692/A2017-B13-20161104135351692.zip

Choose an username... said:
Did you root your phone? Do you intend to? If you do, you can use the conservative governor and fix the lag entirely. Many people believe that the conservative governor is laggier than interactive, but on the SD820 that's not the case. I've tried on SD6xx and 4xx devices (the Moto G2 and G4+ namely) and this is clearly not like this on those phones.
As for the fling thing, well I'd like to see a video, since I never noticed such a thing. I'm on MiFavor 5.0 so maybe something has been changed, because this is Chinese firmware (on the G).
And I believe that you have to fling more because ZTE may have messed up with some files, as they always did... probably not because of the bigger screen
But really, change your firmware to stock A2017. It's completely possible to have Google apps on it, but retailers install the G firmware on tbe Chinese just because they sell it to the global market
Here you go: Download this, and after you have the zip, open it with a zip manager such as winrar or 7zip. If you see a PDF and an update.zip inside, pull the update.zip out and put it in the root of the internal storage, then install it via Settings - Updates. If not just put the zip you downloaded on the root if the internal storage. but i think that zip actually has the other one inside.
https://archive.org/download/A2017B1320161104135351692/A2017-B13-20161104135351692.zip
Click to expand...
Click to collapse
Thanks for the response, once again! I tried to record the scrolling problem with my DSLR camera but it was a lot harder than you'd think to capture the blurring on there. I will have to review the footage on my laptop and see whether there's anything which clearly shows the effect. But having spoke to several people about this, it is probably normal behaviour for the AMOLED panel. I think the best option for me would be like you said, to flash the stock China firmware and see whether it makes a difference to my issues with scrolling lag. If it doesn't then there's no harm done, as the phone will be much better with the China firmware anyway.
I have one question, what would be the difference between the update package you posted and the one from the official ZTE website? I noticed there is one that says '7.1 Back 6.0 ZTE_A2017V1.1.0B11 Dedicated Upgrade Package (All Network Versions)' which would presumably allow me to revert back to A2017 Marshmallow firmware with OTA updates enabled, as you explained previously. Maybe it would be better to use this one since it is dated 20/03/2017 rather than 04/11/2016. And is it definitely 100% safe to use these update packages to switch from A2017G Global firmware to A2017 China firmware?
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78

P650SE said:
Thanks for the response, once again! I tried to record the scrolling problem with my DSLR camera but it was a lot harder than you'd think to capture the blurring on there. I will have to review the footage on my laptop and see whether there's anything which clearly shows the effect. But having spoke to several people about this, it is probably normal behaviour for the AMOLED panel. I think the best option for me would be like you said, to flash the stock China firmware and see whether it makes a difference to my issues with scrolling lag. If it doesn't then there's no harm done, as the phone will be much better with the China firmware anyway.
I have one question, what would be the difference between the update package you posted and the one from the official ZTE website? I noticed there is one that says '7.1 Back 6.0 ZTE_A2017V1.1.0B11 Dedicated Upgrade Package (All Network Versions)' which would presumably allow me to revert back to A2017 Marshmallow firmware with OTA updates enabled, as you explained previously. Maybe it would be better to use this one since it is dated 20/03/2017 rather than 04/11/2016. And is it definitely 100% safe to use these update packages to switch from A2017G Global firmware to A2017 China firmware?
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
Click to expand...
Click to collapse
Well, the package that you found will do too. Most people here expect everything to be done for them, and since I had already found a zip, I thought it would be best to share it at least.
You should actually follow the guide that I just posted - the reason why is that you have to unzip the file and put it in the root of the SD card. It's written so that everyone can understand, so sorry if it's too dense. but if you downloaded the package on the PC (and your phone is somehow able to connect via MTP [or FTP, i have to use this] to your PC) it's just unzip and send.

Choose an username... said:
Well, the package that you found will do too. Most people here expect everything to be done for them, and since I had already found a zip, I thought it would be best to share it at least.
You should actually follow the guide that I just posted - the reason why is that you have to unzip the file and put it in the root of the SD card. It's written so that everyone can understand, so sorry if it's too dense
Click to expand...
Click to collapse
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.

P650SE said:
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
Click to expand...
Click to collapse
You sure you booted to the bootloader? Most phones have it blocked and you can only access recovery, EDL and FTM.
Whatever, yeah, the Chinese recovery is in Chinese. G's and U's have it in English. But still, the option that you may need to use is the one that says 'sd' between some Chinese ideograms (install update from sd card). Ofc you'd need an SD card for that, that's why using the system option to update is preferred.

Choose an username... said:
You sure you booted to the bootloader? Most phones have it blocked and you can only access recovery, EDL and FTM.
Whatever, yeah, the Chinese recovery is in Chinese. G's and U's have it in English. But still, the option that you may need to use is the one that says 'sd' between some Chinese ideograms (install update from sd card). Ofc you'd need an SD card for that, that's why using the system option to update is preferred.
Click to expand...
Click to collapse
Ah, that's interesting! I'm certain it was the bootloader since I followed a tutorial on YouTube to access it. Basically, all I had to do was to switch the phone off and then hold both the volume-up and power buttons until the ZTE logo appeared, then release the power button and keep holding the volume button until the bootloader came up! Anyhow, i'll definitely follow your advice and use the update method via the settings menu in MiFavor. But first I will have to wait another hour for the update package to finish downloading, as my internet speed is only 3.3Mbps!

P650SE said:
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
Click to expand...
Click to collapse
My phone is A2017 too. This screenshot might help you understand those numbers.

^^^Ah, that's cool. So P996A03_N is basically just further identification for the device to indicate it is the Chinese A2017 version.
At the moment i'm having problems with the ZIP for rolling back to Marshmallow. It came packaged in an archive called 20170320111600705.zip which I extracted using WinRAR on my laptop. I copied the update.zip file to the root of my internal storage and to the root of the SD card, but neither are recognised when entering the 'System Update' screen. Is it possible that the reseller on AliExpress blocked the ability to update the ROM? I don't know whether to try running the update directly from the bootloader instead.
On the AliExpress listing for the phone is has a warning which says 'Please do not try to flash the phone by yourself. Otherwise your phone will be blocked and lose the network'. I assume this is just to discourage people from flashing custom ROMs to their devices rather than an actual physical limitation.

P650SE said:
^^^Ah, that's cool. So P996A03_N is basically just further identification for the device to indicate it is the Chinese A2017 version.
At the moment i'm having problems with the ZIP for rolling back to Marshmallow. It came packaged in an archive called 20170320111600705.zip which I extracted using WinRAR on my laptop. I copied the update.zip file to the root of my internal storage and to the root of the SD card, but neither are recognised when entering the 'System Update' screen. Is it possible that the reseller on AliExpress blocked the ability to update the ROM? I don't know whether to try running the update directly from the bootloader instead.
On the AliExpress listing for the phone is has a warning which says 'Please do not try to flash the phone by yourself. Otherwise your phone will be blocked and lose the network'. I assume this is just to discourage people from flashing custom ROMs to their devices rather than an actual physical limitation.
Click to expand...
Click to collapse
Okay, then you'll have to use the recovery. Put the zip on the SD card (I guess you already have it there), turn it off and hold power + vol up. Select the option that says sd and select the zip.
I guess it doesn't work because it detected that the zip was for an A2017 and it thinks it's a G

Choose an username... said:
Okay, then you'll have to use the recovery. Put the zip on the SD card (I guess you already have it there), turn it off and hold power + vol up. Select the option that says sd and select the zip.
I guess it doesn't work because it detected that the zip was for an A2017 and it thinks it's a G
Click to expand...
Click to collapse
Ah. Good thinking about the reason it wasn't working! Although, I tried that and underneath where it says Supported API: 3, it shows a message which says 'Sorry, you can't sdcard upgrade'.
EDIT: Oh, wait a second. I remember reading something which said you should enable OEM unlocking before trying to flash the ZIP. Maybe that would work!
EDIT 2: Well, that seems to have worked. I was so scared! But the ZIP flashed successfully and it has rebooted into A2017V1.0.0B13 MiFavor UI v4.0 (Android 6.0.1) I noticed the bootloader screen is now slightly different as it now shows the Chinese symbol next to the ZTE text. It is now showing an OTA update to V1.0.0B15, so i'll start by doing that and work through all the other OTA's until I reach the latest version!

Check the edit to my previous post. I managed to get the phone onto A2017V1.0.0B13 and then OTA updated to A2017V1.0.0B15, but unfortunately there are no further OTA updates available from this point. So with this in mind, the next step would probably be to download the A2017V1.1.0B17 archive from the same source and flash that using the same method, via the bootloader? Then hopefully that should bump me back up to Nougat and allow me to OTA to the latest version of MiFavor. (v5.0)
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78

P650SE said:
Check the edit to my previous post. I managed to get the phone onto A2017V1.0.0B13 and then OTA updated to A2017V1.0.0B15, but unfortunately there are no further OTA updates available from this point. So with this in mind, the next step would probably be to download the A2017V1.1.0B17 archive from the same source and flash that using the same method, via the bootloader? Then hopefully that should bump me back up to Nougat and allow me to OTA to the latest version of MiFavor. (v5.0)
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
Click to expand...
Click to collapse
Nah, I think you already can use the inbuilt update function. Now that you are on A2017 firmware it should find the zip easily.
The 'bootloader mode' you are referring to is actually the recovery. The bootloader mode is the one on the picture. You can access to it by using adb, and issuing 'adb reboot bootloader', but you might not have it (in which case the phone will just boot to system)
To unlock the bootloader you need to get fastboot on the phone AFAIK, so that's what the axon7toolkit does, it flashes stuff through MiFlash to get fastboot operational. Google it, it's pretty good; if you ever want to unlock, I think it's the way to go.
Just to get everything clear.

Choose an username... said:
Nah, I think you already can use the inbuilt update function. Now that you are on A2017 firmware it should find the zip easily.
The 'bootloader mode' you are referring to is actually the recovery. The bootloader mode is the one on the picture. You can access to it by using adb, and issuing 'adb reboot bootloader', but you might not have it (in which case the phone will just boot to system)
To unlock the bootloader you need to get fastboot on the phone AFAIK, so that's what the axon7toolkit does, it flashes stuff through MiFlash to get fastboot operational. Google it, it's pretty good; if you ever want to unlock, I think it's the way to go.
Just to get everything clear.
Click to expand...
Click to collapse
Whoops! I have no idea why I kept referring to it as the bootloader, maybe because i've become so used to using TWRP on my ZUK Z2 for almost a year and ended up forgetting what a manufacturers stock recovery looked like! That was a very silly mistake. :laugh:
I haven't been able to get an update to Nougat to appear via OTA in the 'System Update' menu, so instead I will download the update package from the ZTE website and see whether that works. I believe once I have updated to V1.1.0B17 via ZIP it should allow me to OTA to the latest version of MiFavor. Thanks for the tips regarding Axon7Toolkit, I already had it installed on my laptop but didn't know about possibly having to enable the bootloader with MiFlash. That is very interesting!

P650SE said:
Whoops! I have no idea why I kept referring to it as the bootloader, maybe because i've become so used to using TWRP on my ZUK Z2 for almost a year and ended up forgetting what a manufacturers stock recovery looked like! That was a very silly mistake. :laugh:
I haven't been able to get an update to Nougat to appear via OTA in the 'System Update' menu, so instead I will download the update package from the ZTE website and see whether that works. I believe once I have updated to V1.1.0B17 via ZIP it should allow me to OTA to the latest version of MiFavor. Thanks for the tips regarding Axon7Toolkit, I already had it installed on my laptop but didn't know about possibly having to enable the bootloader with MiFlash. That is very interesting!
Click to expand...
Click to collapse
Literally you have to get B17 update through OTA when you're on B15. I did, but the reasons you're not is that you or your reseller have converted it to G model. My friend who also had a Chinese Axon 7 and converted it to G had this problem too. And I don't know what to do about it.
---------- Post added at 03:09 AM ---------- Previous post was at 03:06 AM ----------
And I also think that you had to flash B13 upgrade package(second downloadable zip on ZTE website) because B11 was the same B13 but the rollback version meaning for somebody who is already on Nougat and wants to go back to Marshmallow.

X720, X722 and X727 uses the same ROM?

hi guys, i have the X722, i can use ROMs of X727 and X720?

No the x722 has no custom ROMs. You'll soft brick the phone if you try to load any ROMs from other variants onto it, to my knowledge.

:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:

I also soft bricked my Le Eco Pro 3
vsrocha said:
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
Click to expand...
Click to collapse
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
For anyone else reading this post : don't trust every comment here. Some people will give incorrect or incomplete info, such as advice to wipe the system to get around encryption.
* That's what I did and after successfully unlocking the boot-loader, I find that my system was somehow encrypted.. I did not encrypt my phone so I am not sure how this happened. In my haste, I did not create a recovery, I thought that is what the official Leeco twrp was for?
Options?
I too read about the Qfil tool, at the time I was having trouble downloading the files so I attempted to wing it... and failed.
I see now that I did not spend enough time on this complex option.
Update:
here is the exact instructions for using the Qfil method. ( this link provides step by step, and is tedious, but appears to work.
Sigh! I attempted to post a link and could not, due to being new on this site.
No doubt, I found the best instructions that I have seen yet on the Qfil Process.
Its on the unoffical Leeco Repair site : tora33 #comment-15320 this post is much more extensive than some other posts by Tora33 linked from XDA
Again, I can't post the actual link here! Just search for : unoffical Leeco Repair site : tora33 #comment-15320
Potential other options
J tag brick repair service website : brickedmyphone they charge $45 to repair a bricked phone.[/U
[*] This video seems very promising! Unfortunately, I wasn't able to find this video before now.
Since I am new here I am not allowed to help you by posting links!
search YouTube for How to unbrick any bricked letv phone without loosing data ( easiest way ) in Hindi.
Yes its in Hindi, but you will still understand because he used some English and it seems that he has built a fairly useful tool. Although, its still easy to get the gist of what he is telling us and he apparently built a program to repair a bricked Leeco phones, and he has other videos
[*] Finally Google : LeEco X820 Max 2 Super Unbrick Guide ( gizmochina. website) seems to be another complete solution.
I hope this helps you!

How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
https://www.youtube.com/watch?v=m0o4QtNXljg
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
tsongming said:
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
Click to expand...
Click to collapse
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.

sk8223 said:
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
Click to expand...
Click to collapse
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.

tsongming said:
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
Click to expand...
Click to collapse
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.

sk8223 said:
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
Click to expand...
Click to collapse
Thank you for you very good detailed advice. Its truly appreciated.

I was decrying the shop ROM a lot but it's okay. I thought it'd be a lot worse than it is, but at least it lets me play the games I want to play on it without issue (so far...). I'm debloating it soon. Gonna remove all the LeEco apps. I hope kernel sources get released for the x722 but I ain't holding my breath.

OK, this is a loooong story. Can someone save my xperiac4?PLS...........

I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..

no one?..
No one here know hot to save my smartphone?

update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..

asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs

thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..

asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs

in the other thread they said to me to roll back to 5.1 i am doing it now

nvm i got hard brick, the phone is dead and i can't enter in download mode....

asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs

Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...

RIP