Related
Are we expecting any updates soon or the 5.0.1/2 update to fix the bugs that were, presumably, introduced with 5.0?
For instance, the Pebble watch disconnecting constantly. Seems perfect on my M7 with 5.0.2.
Really hope this is done quickly, as it's pretty much unusable right now.
No one knows when 5.0.1 will come, but keeping in mind that 5.1 will be released later this month I guess there's chance that Sammy might go crazy and skip 5.0.1/2 altogether and jump directly to 5.1!
If you want this topic as some request kind then its better to create it in sammobile.
Thanks for the reply.
I just hope Samsung can push through some small bugfix update then in regards to the bluetooth then. It's a big shame I can't really use the Pebble anymore.
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
s1m4an said:
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
Click to expand...
Click to collapse
Hello
May I direct you here: http://forum.xda-developers.com/gal...-official-5-0-firmware-galaxy-t3029557/page79
dariox provided this workaround, which has been working very well for me and keeping my Pebble connected.
"Download BlueTooth auto connect (UniqTec developer)
Set:
"set last device" Flag
Profiles : select all
devices : select your device, and flag in the options "healt hdp" in case of smartband ecc...
Set flag on : Bluetooth on
Device Disconnected
Device Connected"
Unfortunately, it seems to come at the cost of a constant wakelock, and battery drain, but at the moment we don't really have any other choice apart from rolling back to kitkat, getting a new phone, or stop using the Pebble.
Hope this helps.
It's Lollipop's fault, I had the same problem when I upgraded, both the early version and the official version had the same result.
I downgraded back down to KitKat and it's fine now.
Hi,
My newly bought S7 edge is having problems. I noticed that after some time, it is not possible to make any calls or use data even though the range is shown as full in the status bar.
After thorough trial and error, found that the issue is coming only if 4G/LTE is enabled. Otherwise, if i switch to 3G, it works. This is the issue for both the sim slots :crying:
Anyone else who has had this issue . I'm running the latest October patch of Android 6.0.1. Is this a software bug or a hardware issue. Any help or suggestions would be much appreciated
U can try reflashing an old firmware to discard that the update caused the problem.
alehawk said:
U can try reflashing an old firmware to discard that the update caused the problem.
Click to expand...
Click to collapse
The problem is since, it is a new phone, I don't know whether it is the update which causes the problem. I upgraded the software immediately after receiving the phone. Is anyone with the latest october update having the same issue?
I checked online, and it seems like some people have had similar issues in past. Just not sure whether it is a software issue or a hardware. And I honestly dread doing the set up again, as unlike past times (i always root my phone, but because of knox tripping, haven't rooted yet), when titanium backup was there, this would mean lots of time on re-setup
MMMmmm I only had that problem on a phone that wasnt 4g capable but had that option enabled but was because I flashed a firm that wasnt supposed to use.
If its new you can go to warranty and exchange for a new one but my curiosity will remail if it was about the october patch...
I have the same issue... it might just be a bug that will be resolved in the next update
amritpal2489 said:
I have the same issue... it might just be a bug that will be resolved in the next update
Click to expand...
Click to collapse
Oh, that's a relief. So, this issue came after updating the software. Before that, it was working for you?
Hrithan2020 said:
Oh, that's a relief. So, this issue came after updating the software. Before that, it was working for you?
Click to expand...
Click to collapse
Yes
amritpal2489 said:
Yes
Click to expand...
Click to collapse
I was finally able to get the 4G mode also working. Not exactly sure what did the trick.
Here's what I did:
1. Flashed an older version (Aug version) which I found on samfirwmare -> Didn't work
2. Flashed an even older version (July version) -> Didn't work
and then updated the software -> started working
The funny thing is the software is the same as before (the same version as was earlier - October build)
Mods, please close the thread
Hrithan2020 said:
I was finally able to get the 4G mode also working. Not exactly sure what did the trick.
Here's what I did:
1. Flashed an older version (Aug version) which I found on samfirwmare -> Didn't work
2. Flashed an even older version (July version) -> Didn't work
and then updated the software -> started working
The funny thing is the software is the same as before (the same version as was earlier - October build)
Mods, please close the thread
Click to expand...
Click to collapse
Great to see your issue is resolved
Just for the purpose of tracking the rolling out process in the north America region, let's try collecting some date information when you receive the rollout. The process of this upgrade could become a helpful guideline for future upgrade events in the region! Models L04 and L14 might be involved. Let's also comment on your state, wireless service provider, if you are in the beta group and when you got the phone to see if anything is correlated. Please take a minute to fill out the form:https://docs.google.com/spreadsheets/d/1XULbGwxpO0s_RH9EzbvWjLP48MNCz7vkolbT0TiMf7s/edit?usp=sharing
Thank you!
Now, on the official Honor_USA social account, https://twitter.com/Honor_USA, N is coming on Feb 11th. Period.
Update: from Rox_honor, it's officially released on Feb 10th in the US. Some people have had this update already.
To force the update, you can check the method posted on Page 2, #16: https://forum.xda-developers.com/showpost.php?p=70992090&postcount=16.
Reserve for updating statistics, if possible. Again, the Google Spreadsheet to fill out is https://docs.google.com/spreadsheets/d/1XULbGwxpO0s_RH9EzbvWjLP48MNCz7vkolbT0TiMf7s/edit?usp=sharing
Feel free to add more columns if you think they are helpful.
So far it seems that only T-Mobile users are getting the update. Just tried to update my Mom's phone, we are on Cricket (AT&T) and there was no update for her. Tried putting it on airplane and restarting but still nothing. I'll probably try again tomorrow.
chris23445 said:
So far it seems that only T-Mobile users are getting the update. Just tried to update my Mom's phone, we are on Cricket (AT&T) and there was no update for her. Tried putting it on airplane and restarting but still nothing. I'll probably try again tomorrow.
Click to expand...
Click to collapse
There is one entry reporting received the update while on Straight Talk. We need to have more data in order to figure out the rollout sequence. GOOD LUCK!
i purchased the Unlocked Honor 8 from US (amazon). But I'm an indian user and I'm using it with an indian carrier . will i get the update as the other north american devices or do i have to wait longer
Did not get the update (FRD - L04)
But I forgot whether or not the L04 is international or US (i live in the US though)
yeah i havent gotten it either still says no updates available
I haven't received the update either on L04. I read on the other thread that it rolls out in small batches.
Edit: Here's the post: https://forum.xda-developers.com/showpost.php?p=70964112&postcount=392
Nothing on L04 AT&T yet. Purchased from NewEgg and first activated in December.
Got it 3 weeks ago. L04 from b&h.
Bought it unlocked at Frys a week ago and received the update yesterday. I just want to caution all rooted and unlocked users! I received the update yesterday and upgraded it like a fool. I cant get into twrp recovery and the stock recovery seems to be broken. I even installed a newer twrp thru fastboot but im still not able to go into recovery. Im looking through all the forums but no one seems to have this problems yet. Im still waiting on some help if anyone has a solution. So please be aware before updating. Hopefully Im the only one with this problem.
yomomsbigpimp said:
Bought it unlocked at Frys a week ago and received the update yesterday. I just want to caution all rooted and unlocked users! I received the update yesterday and upgraded it like a fool. I cant get into twrp recovery and the stock recovery seems to be broken. I even installed a newer twrp thru fastboot but im still not able to go into recovery. Im looking through all the forums but no one seems to have this problems yet. Im still waiting on some help if anyone has a solution. So please be aware before updating. Hopefully Im the only one with this problem.
Click to expand...
Click to collapse
Ahh, I was an idiot and had the same thing.
What happened is that I was rooted, and installed via Charles app, and it bugged out.
The reason for that is that TWRP can't install the stock ROM.
You need to get into fastboot, and reflash the stock recovery, and use it to dload the emui 4.1 file. Make sure you get the full package version.
After that it will be all wiped. You might run into a few errors but let the recovery do its thing.
You'll eventually be able to boot into the OS and then run the update normally.
I want to root my honor 8 on nougat, but I'm waiting for a patch from Huawei first because of all the bugs, just because of this.
Also I don't think rooting the honour 8 on nougat works that we'll yet, hopefully someone comes up with a method that doesn't suck so hard.
Hopefully they'll do it quickly.
Do you mind pointing me to the right direction to find those files? stock recovery and the 4.1.
Ive seen the rollback files... is that what you're talking about?
yomomsbigpimp said:
Do you mind pointing me to the right direction to find those files? stock recovery and the 4.1.
Ive seen the rollback files... is that what you're talking about?
Click to expand...
Click to collapse
I used the firmware finder tool for it. You can get it for Windows. It's somewhere around the forum, but you can probably Google it.
Once you get the full package you can extract the recovery.img from it.
Unlocked FRD-L04 bought from Amazon. Living in Argentina. Got update yesterday. Really happy with it.
Folks, if you are impatient, you can use the Firmware Finder to send the Firmware B360 (I am using the Jan 3 one) to your Updater for a full package update. More information can be found at https://forum.xda-developers.com/honor-8/how-to/news-huawei-firmware-finder-team-mt-t3550882
A few notes here from my personal experience:
1. Once you set up the proxy from the Finder's proxy app which should be downloaded after you enabled the "send firmware to updater" (check notification afterward), you then click on the latest firmware # and "send firmware to updater".
2. On the Setting/Updater, click the menu and use "Download full update package", which should direct you to a 2.27Gb package (not the 1.28Gb package, or you will not be able to login!) and click on the "Quick update" button. You may need to wait for a while to see this option. Up to now, you may not be able to download anything yet.
3. Go back to the wifi setting and turn on proxy setting to "None" again and reconnect with the wifi network. Now you should pause the Updater and then resume it. You should now be able to download the full package and install it.
4. After all the update process, it could be helpful to charge your phone without the screen turning on. This is told to be useful to optimize the battery performance immediately after the update. The phone might be slow in a couple of hours as optimizations are going on in the background. But everything will become normal afterward
Good luck!
bought L04 from newegg using it in Pakistan no update for me as of yet
This is all bulls*it. Same update we got in january, and by the way, it's buggy.
L04 here, bought from Amazon about a month ago. Running on T-Mobile US. Still no update yet.
Is there any way to change the white notification background? I prefer the old color scheme, Mich easier on the eyes at night.
Sent from my BTV-W09 using Tapatalk
Edit: Received update on US single SIM L04 on Straight Talk, ATT towers.
My Moto G5 Plus is telling me that my software is up to date, yet it's still running Android 7.0, but more importantly the security patch level is 1/1/17. I don't know about major OS updates, but there MUST be at least some updates out there that I'm not getting. Can someone link me to somewhere where I can find a .zip files for all OTA updates, so I can just flash the update and then flash Magisk again to retain root? Thanks!
You are probably not receiving OTA updates since you've rooted your phone, right? There was no major updates but there was few security patches this year. Which model exactly you have? That's gonna help in providing you correct links...
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
nlinecomputers said:
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
Click to expand...
Click to collapse
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
acejavelin said:
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
Click to expand...
Click to collapse
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
nlinecomputers said:
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
Click to expand...
Click to collapse
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
acejavelin said:
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
Click to expand...
Click to collapse
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
nlinecomputers said:
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
Click to expand...
Click to collapse
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
FamilyGuy0395 said:
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
Click to expand...
Click to collapse
Sort of... OTA files can only be flashed on a pure stock system, no root, no TWRP, no Xposed, nothing changed in system, no removed packages, etc. If the OTA script even detects that /system was ever mounted R/W it can fail (I don't know if Moto goes that far).
To flash an OTA you must restore your stock ROM completely (/system, /boot, and any other system level partitions), and restore stock recovery, and all versions must match or the OTA script will crap out with an error.
The OTA files are out there, on this forum in various threads... you can find them along with instructions on how to apply them to rooted and stock systems.
acejavelin said:
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
Click to expand...
Click to collapse
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
nlinecomputers said:
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
Click to expand...
Click to collapse
Oh yeah... Moto's level of doing what the carriers "recommend" or whatever you want to call it, is ridiculous lately.
Good example is Nougat for the Moto X Pure Edition, if you are on Sprint or US Cellular you got it 2 months ago, but Verizon, AT&T, and T-Mobile users still haven't seen it. Except many users have figured it out, pop in a Boost Mobile SIM (not even activated) and it will grab the update almost immediately, let it apply, then swap your original SIM back in and enjoy some Nougat goodness. However that device never had a specific version for a certain carrier. Still today probably 80% of users of that FLAGSHIP device still haven't gotten an update that we know was completed in June/July, due to "partner approvals" or some such BS.
All these updates still come directly from Moto and their servers, but they are doing what the carriers tell them and only allowing it to certain devices... This has vaguely been admitted to by the mods on the official Lenovo support forums.
Honestly, many smaller brands with a history of poor update frequency get better update support than Moto's these days... My son's Axon 7 Mini already has 7.1.1 with the September update for BlueBourne, he got it the third week of September, and gets on every 3 months like clockwork. My faith in Moto is diminishing quickly, I gave them the benefit of the doubt on my last two (Moto X Pure Edition and Moto G 2015) because they were kind of transitional device during the Google-Lenovo switch over, and although my Moto G5 Plus is supported a little better I believe it is just because it is newer and not because Moto got better.
Chances this will be last Moto device? Let's just say this could be my last Moto device, and I have been a big Motorola fan for many years.
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Can anyone link me where to find OTA updates for Moto G5 Plus and, if necessary, instructions? I don't see why the instructions would be any different from the OnePlus 5, other than Motorola making it harder on purpose.
FamilyGuy0395 said:
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Click to expand...
Click to collapse
Never said it was true for every phone or manufacturer, but that is the way it is with Moto devices... You cannot flash an OTA with TWRP, the script checks (among other things) the recovery and will fail if it doesn't have the correct signature, same with the modems, bootloader, partition table, and things in /system. Moto OTA updates are VERY picky and will fail at the drop of a hat on a device that is not purely stock.
The only work around, that works in SOME cases with Moto devices, is using FlashFire by Chainfire, but that is hit and miss, depends on what is updated.
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Karlinski said:
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Click to expand...
Click to collapse
Do you have a link to this thread? I am curious how the modems, partition table, and bootloader updates are handled since TWRP doesn't have the correct signature to write to these partitions. I can see where it could maybe update the boot and system partitions if they were extracted from the ROM, even if they are differential deltas, but my guess is that a "TWRP flashable" OTA is mearly an extract of a blank device's boot and system partition or just he changes, and packed into an OpenRecovery script, and not the "real" OTA file.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Karlinski said:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Q9Nap said:
Do NOT attempt to apply standard OTAs over these builds; they will fail.
Click to expand...
Click to collapse
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
acejavelin said:
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
Click to expand...
Click to collapse
The TWRP flashable stock builds DO upgrade the modem.
As stated in the OP, the only partitions NOT upgraded are gpt and bootloader.
I didn't omit these partitions because they can't be written; I omitted them to prevent potential issues for people who really don't know what they're doing.
Disabling dm-verity is required due to some partitions unavoidably losing their oem signatures during the conversion process.
Disabling force encryption is practically required, as TWRP seems buggy with it enabled.
The intended purpose of these builds is to provide a dead simple (and safe) way for users to return to stock.
I have linked useful tools at the bottom of the OP for those interested in making their own modifications to these stock builds.
Hope this helps :good:
Q9Nap said:
Hope this helps :good:
Click to expand...
Click to collapse
It does actually, thank you... Obviously I have a lot to learn about the differences between current devices and older Moto devices I am used to working.
Hi All
can i flash the following firmware on my ZTE Axon Mini - It was purchased from Gearbest
https://www.ztemobile.de/support/downloads/?product_id=2344
current version is 6.0
many thanks
if yours Mini is G version and you live in europe - then yes.
Tommixoft said:
if yours Mini is G version and you live in europe - then yes.
Click to expand...
Click to collapse
done with the gearbest B2017G, update to 7,1,1 , but I can't go in bootloader mode to root
Diomorgan said:
done with the gearbest B2017G, update to 7,1,1 , but I can't go in bootloader mode to root
Click to expand...
Click to collapse
Next time read before doing With 7.1 there is no longer bootloader mode. Downgrade to 6. Also you dont need to unlock it, there is no better ROMs for this rom. Official one is best. I tried them, so you can save time and use official one.
ALso root not working well with it. I had root but somehow i couldn't delete system apps.
Tommixoft said:
if yours Mini is G version and you live in europe - then yes.
Click to expand...
Click to collapse
Sorry if I'm hijacking this thread, if so, I can start another.
I recently purchased this phone (B2017G) from Gearbest as well.
It is still on 6.0.1 Marshmallow.
I have been searching for the right update file, starting with the US version, since that is where I live, but no go. The bootloader says
"E footer is wrong
"E:signature verification failed
"E: open file /cache/fota/error_code error erno = 2
'Installation aborted'
Am I right in thinking I need to find the update with the right signature? I have tried US, Austrian and Russian official ZTE updates with no success so far.. Am I on the right track?
US ZTE Support was as helpful as they could be, but were not familiar with the GearBest global variant. They sent me to the global support site, which won't let me use it, since I'm from the US, lol
Any suggestions? I'm going to try the German update from earlier in this thread after I get home tonight, by the way...
I also purchased mine from Gearbest (B2017G). I believe the phone is for the European market as it comes with a EU plug in the sealed box, but not sure for which country. I tried the firmware for the Spanish model http://www.ztedevice.com/support/detail?id=D4454D33442F45E192A95718509F4586. The update failed.
I just flashed the Nougat 7.1.1 an hour ago from here:
https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13.
It already looks promising - the phone is very cool after update. Previously the phone is always warm, even in standby. I hope the battery life is a big improvement.
If you intend to flash this zip file, make sure your phone is a European model B2017G. As posted before I got this phone from Gearbest as many others.
Hi,
Updated to 7.1.1 by OTA 3 weeks ago when i bought the phone from Amazon.
It seems that we'll get Oréo later...amazing ! thks ZTE !
It is not official that Axon 7 Mini (B2017G) will get Android 8 aka Oreo. ZTE should do the update to Oreo as this is one popular phone still.
reticuli said:
It is not official that Axon 7 Mini (B2017G) will get Android 8 aka Oreo. ZTE should do the update to Oreo as this is one popular phone still.
Click to expand...
Click to collapse
In a chat with ZTE USA assistance last week, the tech mentioned that Oreo will be rolling out for the Axon 7 Mini in the US.
afigienas said:
Next time read before doing With 7.1 there is no longer bootloader mode. Downgrade to 6. Also you dont need to unlock it, there is no better ROMs for this rom. Official one is best. I tried them, so you can save time and use official one.
ALso root not working well with it. I had root but somehow i couldn't delete system apps.
Click to expand...
Click to collapse
Once you downgraded and rooted can you upgrade back and keep the root?
Root is needed for this phone because it doesn't allow to move ANY app to SD.I sort of recovered the backup of my apps and data with Helium without root, but I need more internal space: with root you can even enable adoptable storage.
If only we can get access bootloader and flash modified boot.bin with magisk...
At the moment I can only use it as backup phone, my everyday phone LG G5 has 7gigs of whatsapp stuff that can only be internal, but most part of the 130+ apps I got are shared in the SD card.
I don't even need TWRP actually, just root to move apps to SD (or a firmware that allows it, since it's a firmware option...ZTE decision)
Flashing nougat 7.1.1 is the best thing I've done - it basically fixed the battery drain. I had to charge 3 times a day before the update. Last night the battery was only down 3%. This morning I recharged it to 93% before I left for work. At 5pm after a days normal use, it still had 55% left. It's just amazing. I think the update flashed out all the nastiest including the suspicious apps that come with the phone. I have no idea what they are - 99003, 99033, 99035 and more. I suspect they are malware although I cant be sure. They consume battery and keep the phone awake. The phone was warm even in standby.
priority1 said:
Flashing nougat 7.1.1 is the best thing I've done - it basically fixed the battery drain. I had to charge 3 times a day before the update. Last night the battery was only down 3%. This morning I recharged it to 93% before I left for work. At 5pm after a days normal use, it still had 55% left. It's just amazing. I think the update flashed out all the nastiest including the suspicious apps that come with the phone. I have no idea what they are - 99003, 99033, 99035 and more. I suspect they are malware although I cant be sure. They consume battery and keep the phone awake. The phone was warm even in standby.
Click to expand...
Click to collapse
you mean the stock one or a custom 7.1.1 ?
Diomorgan said:
you mean the stock one or a custom 7.1.1 ?
Click to expand...
Click to collapse
Stock one
Got the 7.1.1 update...
... in a round-about way. Went here http://www.ztedevice.com/support/detail?id=6CCC18CC9451416C8A01BED5174B5762#software and it downgraded my phone to a December 2016 security update.
Flashed the Russian 6.0.1, (had to use the bootloader method for both), then was able to run the Spanish update from ZTE, directly from the System updates menu after extracting the 'update.zip' file from the package and placing it in the root of the SD.
Now running 7.1.1 and happy. I can still access AT&T's US network perfectly, so I didn't destroy the usefulness of my new phone as a phone.
I may eventually put a second T-Mobile sim in it if I think I can live without the SD card's storage...
Edit: I am running a GearBest-purchased phone with 'global' firmware, meaning no official updates available. It is possible that I could have tried to use the Spanish 7.1.1 directly, but I didn't try that before taking the route I did. Just happy *something* worked!
Still no root? Even a firmware where I can patch boot.img with magisk and repack and flash?
I did it with Ulefone S8Pro, but because someone here posted the firmware and it was editable and flashable without getting errors! No TWRP, but who cares, I have adoptable storage and Is essential with those "low" internal memory phones....
A ZTE moderator on the official US site has disconfirmed my report of Oreo on Axon 7 Mini:
"sshasan Z-Community Moderator New YorkPosts: 3,409Z › admin
April 2, 2018 5:40PM
No announcements have been made at this time. If a representative has stated this, they have misspoken."
Click to expand...
Click to collapse
Please disregard my earlier reporting. Although my report was accurate as far as what I had heard, the rep I chatted with was likely mistaken.