Database Users

5.0.1 (LRX22C) Factory image just posted for Nexus 7 2013 and a few others

https://developers.google.com/android/nexus/images#razorlrx22c
Nexus 9 and 10 images posted as well.

If you flashed it already Any obvious improvements guys ?

I hate the fact that they still bundle the old launcher and not the Google Now launcher as default. Just formatted my device and installed this new image from scratch. Seems snappy as before. No obvious changes that I can see. Will provide more feedback once I get all my apps installed and once the device has time to settle in.

Downloaded the image.
Unpacked it
Edited the flash-all.bat to remove the -w (preserves userdata)
Ran flash-all.bat
Let it boot up after flashing
Flashed twrp to recovery
Ran CF autoroot
Updated SuperSU
Re-enabled AdAway
All good so far, no problems, no errors.

What are the main changes we should expect? I searched and couldn't find much information except about increasing battery usage efficiency of android wearables.

aberchonbie said:
What are the main changes we should expect? I searched and couldn't find much information except about increasing battery usage efficiency of android wearables.
Click to expand...
Click to collapse
One of things reported fixed are the video issues.

just lou said:
One of things reported fixed are the video issues.
Click to expand...
Click to collapse
Wonderful, hate that I haven't been able to use youtube for a month!

Just Flashed...
Just flashed a clean install of this, and so far i seem to be faster, more responsive, using less ram, more stable and all my video playback issues are gone.

Sadly Minion Rush and Dead Trigger 2 still work like I have a 2009 device and a lot of other apps don't work. Hope they update soon so I can switch to Lollipop and keep it as a daily driver. It's been almost a month since Lollipop came out and some devs still haven't updated their apps.

Any OTA zip?

How about gaming performance? Is it any better in this build?

idCyber said:
Sadly Minion Rush and Dead Trigger 2 still work like I have a 2009 device and a lot of other apps don't work. Hope they update soon so I can switch to Lollipop and keep it as a daily driver. It's been almost a month since Lollipop came out and some devs still haven't updated their apps.
Click to expand...
Click to collapse
shism said:
How about gaming performance? Is it any better in this build?
Click to expand...
Click to collapse
Not sure if the issues are related, especially as I'm about to talk about a very different device in the wrong forum, but(!) I had initially experienced an extremely low 'slow motion-esque' frame rate on my N5 while attempting to play Blitz Brigade, after clean flashing the 5.0 factory images. Other games like Riptide played just fine. After a week or so, Gameloft finally released an update and everything was back to normal. I'm thinking, perhaps, your games (vs. L) are in need of a similar update. I'd advise you mail the relevant developers, as I did, and hopefully you'll get some confirmation, rather than a robot.

I seem to have an issue signing into Netflix. Anyone else experience this issue? Fresh install from fastboot flash-all . bat.
Sent from my Nexus 5 using Tapatalk

Steve-x said:
Downloaded the image.
Unpacked it
Edited the flash-all.bat to remove the -w (preserves userdata)
Ran flash-all.bat
Let it boot up after flashing
Flashed twrp to recovery
Ran CF autoroot
Updated SuperSU
Re-enabled AdAway
All good so far, no problems, no errors.
Click to expand...
Click to collapse
Did you use the same CF-autoroot as 5.0?

chrisinsocalif said:
I seem to have an issue signing into Netflix. Anyone else experience this issue? Fresh install from fastboot flash-all . bat.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Might not be the ROM/phones/tablets fault. For two days now I've had issues signing in to Netflix on the same 2 TVs we always use. It did work properly on one this AM, not the other.

dunjamon said:
Did you use the same CF-autoroot as 5.0?
Click to expand...
Click to collapse
Yes, the same CF-autoroot and same recovery as used in 5.0.

Can someone tell me what I am doing wrong?
I am downloading the 5.0.1 file from the google site and when it is down I have a .tar file
I use winrar to extract and have a the file razor but no extention
When I rename to add .zip and extract I have a couple of .img but no flash -all file
What am I doing wrong?

obionenairobi said:
Can someone tell me what I am doing wrong?
I am downloading the 5.0.1 file from the google site and when it is down I have a .tar file
I use winrar to extract and have a the file razor but no extention
When I rename to add .zip and extract I have a couple of .img but no flash -all file
What am I doing wrong?
Click to expand...
Click to collapse
extract the image with winrar and extract again, for some weird reason Google double zip it

When you extract the .tgz file, you should get a .tar file. Extract the .tar file and you get a folder with all your files.

I just got my Nexus 7 delivered today. I'm loving it so far!
I couldn't wait so I flashed the factory 5.0.1 and rooted with chainfire. No issues at all.

[D5503][Stock][PreRooted][DualRecovery] 14.6.A.1.216 Customized CE5 (Central Europe)

Hi guys,
I've downloaded with XperiFirm the latest available firmware customized for Central Europe and created a prerooted .zip with PRFCreator.
Some details about the used FTF file:
Code:
Device: Xperia Z1 Compact (D5503)
CDA: 1280-7870
Market: Central Europe 5
Operator: Customized CE5
Network: EURO-LTE
Release: 14.6.A.1.216 / R1D
What is included in the package:
Code:
D5503_14.6.A.1.216_Customized CE5
UPDATE-SuperSU-v2.46.zip
Z1C-lockeddualrecovery2.8.21-RELEASE.flashable.zip
XZDR-2.8.21_Patch.zip
You need to have custom recovery to flash it, and please remember to backup your device.
You use the file at your own risk!
Get it while it's still hot! Download link: http://bit.ly/Xperia_Z1C
WARNING for Xposed users: Your phone WILL BOOTLOOP if you upgrade from a ROM with installed Xposed v74 or older.
You need Xposed v75, this works OK, I have it installed on my phone and works flawlessly.
If you have v74 or older installed now, first you need to uninstall it from within Xposed Installer -> Framework, and only then you should perform update. Don't forget to make a backup before you start
Newest version of Xposed can be found here
No changelog available but this is what we have observed so far:
+ Not vulnerable to Stagefright (including CVE-2015-6602)
+ MX Player + Hardware decoder bug - fixed
+ possible better battery life (subjective opinions of few users)
- some users experienced problems with root / recovery after update, trying to pinpoint the cause of this with a poll...
Enjoy!

Any new features with this version? Is stagefright 2.0 fixed?

I believe it's mostly bugfixes and optimizations - I am just using this for a few hours but initial impressions are positive - system is very responsive and I did not have any issues so far.
No stagefright vunerabilites as far as I can tell (check attached printscreen).
Changelog is nowhere to be found I'm afraid, didn't notice anything in particular in terms of new features or apps between this version and 14.6.A.0.368.

szturchen_pl said:
I believe it's mostly bugfixes and optimizations - I am just using this for a few hours but initial impressions are positive - system is very responsive and I did not have any issues so far.
No stagefright vunerabilites as far as I can tell (check attached printscreen).
Changelog is nowhere to be found I'm afraid, didn't notice anything in particular in terms of new features or apps between this version and 14.6.A.0.368.
Click to expand...
Click to collapse
Thank you very much for your work.
You can record at 60fps in this update??

Is hw+ freeze bug on MX Player fixed?

I got a bootloop when installing xposed v74 on this rom. everything else was working fine!

Can confirm bootloop after flashing xposed v74. So it is no option for me. Pity that.
Gesendet von meinem D5503 mit Tapatalk

@suprememaster, @kislack you are right, IT WILL BOOTLOOP i forgot to mention that, I will update first post right away - you need Xposed v75 if you want to use it. It works OK, I have it installed on my phone and works flawlessly.
If you have v74 or older installed now, first you need to uninstall it from within Xposed Installer -> Framework, and only then you should perform update. Don't forget to make a backup before you start
Newest version of Xposed can be found here
@oviseven666 i haven't used this feature before, but I couldn't find it in camera app so I think you can't record 60 fps - at least not with the default camera app installed.
@bumjrah I do not use MX Player so can't help you there, you will have to try it yourself or maybe someone else who is using the app will.

bumjrah said:
Is hw+ freeze bug on MX Player fixed?
Click to expand...
Click to collapse
I got no freezes yet with mx player and HW+ decoder. scrolling through the video is working fine.
Xposed is also working fine with v75 sdk22

Thinking of upgrading from 14.5.A.0.270, but i read i another thread that someone had problems when upgrading with an unlocked bootloader. That seemed very strange. Should i be concerned or just flash it like a man?

szturchen_pl said:
No stagefright vunerabilites as far as I can tell (check attached printscreen).
Click to expand...
Click to collapse
This could be the changelog for this update.
14.6.A.0.368 is vulnerable to CVE-2015-6602.

I think this update also fixes the charging bug with the magnetic cable. My phone finally charges to 100%. But the led started flashing when it was at 75% till it was fully charged. It has been a long time since kitkat

No Root
Hi, I installed the zip but the recovery said that the SuperSU could not be applied. So I don't have root now.
How do I get into recovery now? Switching device of, than on and pressing Vol+ does not work :crying:
What can I do now?

suprememaster said:
I think this update also fixes the charging bug with the magnetic cable. My phone finally charges to 100%. But the led started flashing when it was at 75% till it was fully charged. It has been a long time since kitkat
Click to expand...
Click to collapse
Unfortunately not, my phone was charged to 93% with magnetic charger.

skochxxl said:
Hi, I installed the zip but the recovery said that the SuperSU could not be applied. So I don't have root now.
How do I get into recovery now? Switching device of, than on and pressing Vol+ does not work :crying:
What can I do now?
Click to expand...
Click to collapse
Hi, i had the exact same problem and know the solution.
The reason it did not work is, you need to install lockeddualrecovery (Z1C-lockeddualrecovery2.8.21-RELEASE.installer.zip at http://nut.xperia-files.com/ unzip it and run the .bat on your pc)
And THEN you reboot with the volume keys pressing pulsing. and load the zip file. After it is finished, i also selected wipe cache+darvin or whatever it is called. It installs without problems and with SuperSU.
So now that you know how to do it, you need to find a way to get back to your rooted 4.4.4 and then start from the steps.
(i did just select 4.4.4 .108 in flashtool, selected both wipe checkboxes, and installed that. and then started newroot program and rooted it, and then steps as above)
Hope I could help! I am very sure it will work

skochxxl said:
Hi, I installed the zip but the recovery said that the SuperSU could not be applied. So I don't have root now.
How do I get into recovery now? Switching device of, than on and pressing Vol+ does not work :crying:
What can I do now?
Click to expand...
Click to collapse
I had a similar problem and lost root too (perhaps installing Dualrecovery .22 over .21 without removing the older one was the culprit).
After long searching and trying this did help me:
http://forum.xda-developers.com/crossdevice-dev/sony/root-how-to-root-5-0-lollipop-t3212108
You need only first flash this firmware 14.5.A.0.270
KingRoot and other similar software did not help.

Unlocked Bootloader - No Root after update
Thanks for the hints! - Now I have 5.1.1 (.216) running with root. What I did:
1. Flashed .108 with Flashtool (.108 is easy rootable and I still had it in my download folder )
2. Rooted with EasyRootTool
3. Installed SuperSU
4. Installed DualRecovery
5. In TWRP (Vol- when starting) I installed this prerooted zip (.216)
Before that I tried the same procedure but used PhilZ Touch to install this zip (5.) and got the same error as mentioned some posts before. So I think the problem could also depend on the recovery and flashing this zip only works with TWRP.
Thanks for your effort!

Installation on a rooted/unlocked phone with xposed v75 via TWRP worked fine. Thank you very much!

Yes,i can confirme the bug with the preerooted zip file posted above also.I was flashing the preerooted zip and lost root.My way was the same.Downgrade to 4.4.4,root with newroot tool and flash my own preerooted zip, but now with TWRP. All work fine now.Its definitly a problem with Philz Touch....

Hi Szturchen_pl , I have xposed 74 , but in Framework , I can not perform uninstall , how can I uninstall please ????
Thanks

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.

Please Recommend Me The Top 2/3 Most Stable Slim Roms - New Axon 7 User!

I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264

kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !

raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:

kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:

raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!

kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.

raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.

kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)

kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me

raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!

@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.

If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013

kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:

raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!

Confirmed G version received.

kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.

raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED

kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?

raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.

kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?

Issues Downgrading

Has anyone else had issues downgrading from the latest P preview to 8.1? It fails everytime for me and now I'm stuck on P preview which is still not playing nice with Nova Launcher.

blaze0303 said:
Has anyone else had issues downgrading from the latest P preview to 8.1? It fails everytime for me and now I'm stuck on P preview which is still not playing nice with Nova Launcher.
Click to expand...
Click to collapse
I'm sure you're following the appropriate directions?
Uninstall the Android P Beta
Uninstalling the Beta from your Essential Phone before the end of the program requires a full reset of your device. This will wipe all user data on your device.
If you've flashed your Essential Phone with the Android P Beta, but want to remove it and go back to Android 8.1 Oreo, download the relevant Fastboot file from our Current Builds page, then follow the instructions to manually flash it to your device.
CAUTION: If you're trying to downgrade to a lower OS version, you need to download the Fastboot file and follow the How to Flash instructions. OTA will not work for downgrading.

blaze0303 said:
Has anyone else had issues downgrading from the latest P preview to 8.1? It fails everytime for me and now I'm stuck on P preview which is still not playing nice with Nova Launcher.
Click to expand...
Click to collapse
What's wrong with Nova? It's running fine for me.

cappysw10 said:
I'm sure you're following the appropriate directions?
Uninstall the Android P Beta
Uninstalling the Beta from your Essential Phone before the end of the program requires a full reset of your device. This will wipe all user data on your device.
If you've flashed your Essential Phone with the Android P Beta, but want to remove it and go back to Android 8.1 Oreo, download the relevant Fastboot file from our Current Builds page, then follow the instructions to manually flash it to your device.
CAUTION: If you're trying to downgrade to a lower OS version, you need to download the Fastboot file and follow the How to Flash instructions. OTA will not work for downgrading.
Click to expand...
Click to collapse
Yup, I've done it before on the previous P build with no issues.
spotmark said:
What's wrong with Nova? It's running fine for me.
Click to expand...
Click to collapse
For some reason the stock launcher is showing up behind Nova and I'm getting weird home screen issues.

blaze0303 said:
Yup, I've done it before on the previous P build with no issues.
For some reason the stock launcher is showing up behind Nova and I'm getting weird home screen issues.
Click to expand...
Click to collapse
Just disable the gestures, then no issues whatsoever

crixley said:
Just disable the gestures, then no issues whatsoever
Click to expand...
Click to collapse
Awesome will try. :good:

blaze0303 said:
Has anyone else had issues downgrading from the latest P preview to 8.1? It fails everytime for me and now I'm stuck on P preview which is still not playing nice with Nova Launcher.
Click to expand...
Click to collapse
I'm also unable to downgrade. command window closes and phone restarts. Fails every time. Hate to be stuck.

Try copy the *.dll files with fastboot.exe to your extracted firmware folder and run flashall.bat or try lower version of fastboot.
This maybe help.
Don't use flashall.bat in this file, use the one include in fastboot rom you download from essential website.

On a tangential note using the instructions and files provided on the Essential web site allowed me to downgrade from Oreo to 7 without issue, apart from re-installing all the apps and data again etc.
(Needed to downgrade to demonstrate that Oreo has broken USB-C to HDMI output in some fundamental manner preventing at least some 3rd party hubs working)