Hello,
I can buy Axon7 on Aliexpress for around 330USD. Currently I'm using OPO and it is running just fine. I've got a few questions to you guys:
1. Are custom ROMs stable ( no bugs, battery drains, camera and sound is working like on stock )?
2. How far is Stock ROM from AOSP (recents, QS, settings) ?
3. Would you switch if you had OPO ?
4. Are there any news of update to Android O being planned ?
Thanks for the replies!
If you want front facing speakers, yes. If you like the huge amount of roms available for bacon, stay with that. I was on the opo and if it was not for the speakers on the a7 I would switch back.
There are still enough roms available, just not like for op5. Roms are stable
FunkyRasta said:
Hello,
I can buy Axon7 on Aliexpress for around 330USD. Currently I'm using OPO and it is running just fine. I've got a few questions to you guys:
1. Are custom ROMs stable ( no bugs, battery drains, camera and sound is working like on stock )?
2. How far is Stock ROM from AOSP (recents, QS, settings) ?
3. Would you switch if you had OPO ?
4. Are there any news of update to Android O being planned ?
Thanks for the replies!
Click to expand...
Click to collapse
Most ROMs are somewhat stable, but all of them have a couple of bugs like mic broken until you turn on and off the loudspeaker (you can fix that with macrodroid). And the stock ROM works better than the custom ROMs no doubt. But I found out that (if you care more about MP3 music than FLAC lossless) V4A is better on custom ROMs than stock. and you can get more than 7 hours SOT on custom ROMs if done right (normally people get 5 on the stock ROM)
The stock ROM is totally different than AOSP. The stock launcher has no dock just like Apple stuff but it also comes with an alternative with dock. The icons are crappy though. If you install Lawnchair from XDA you get a launcher better than Pixel and stock icons for almost all of the apps. Recents is just like AOSP but with a Clear all button and a lock to avoid you closing the app by swiping or via the button. pretty handy!
Now, I had something weird happen to me: When I got my Moto G 2 I used the stock ROM for like 3 days and switched to customs. I never even thought about going back to stock for all the poor phone's life (like 1.5 years). now with this one, I try a couple of ROMs for a month or two, get bored and return to stock. Always happens. Many people say the same, that they started liking the stock ROM even though it strays from AOSP a lot. But it has its fair share of good things, like auto power-on some minutes before your alarm goes off, scheduled on and off, a Dolby Atmos QS tile... It's not bad because it doesn't look like AOSP. not at all.
Besides, MiFavor 5.0 was released for the Chinese and it looks very good!
The phone has hardware keys but the Chinese version hasn't, hence the on screen keys on the screenshot.
Update to O: No news yet, though if it comes, expect the first 2 or 3 builds to be riddled with bugs. ZTE's devs barely know how to use a keyboard. Up to B04 Nougat they broke the Play store then fixed it, broke exFAT for SD cards, then fixed it... People made petitions (basically spamming "We want Android O" on a petition thread on the German forums) but nobody said anything close to a confirmation.
Would I switch from a OnePlus One? 2K AMOLED screen, SD820, speakers better than Samsung's $800 phones come with, QC3.0, for 330 dollars? definitely
The screenshots I attached are from the Chinese MiFavor 5.0 because that's what I'm using right now. You can install it via TWRP if you want.
one thing though: If you can get an A2017U (US version) instead of an A2017 (Chinese Aliexpress version) you're gonna thank me. The U version has so much more development than the G or Chinese... Even people say that sound is better on it. It costs 330 dollars on the US too.
This phone is easy to brick, be REALLY careful and read everything twice before doing stuff or you can end up with a DFU brick which is the most hardcore brick of them all.
Choose an username... said:
Most ROMs are somewhat stable, but all of them have a couple of bugs like mic broken until you turn on and off the loudspeaker (you can fix that with macrodroid). And the stock ROM works better than the custom ROMs no doubt. But I found out that (if you care more about MP3 music than FLAC lossless) V4A is better on custom ROMs than stock. and you can get more than 7 hours SOT on custom ROMs if done right (normally people get 5 on the stock ROM)
The stock ROM is totally different than AOSP. The stock launcher has no dock just like Apple stuff but it also comes with an alternative with dock. The icons are crappy though. If you install Lawnchair from XDA you get a launcher better than Pixel and stock icons for almost all of the apps. Recents is just like AOSP but with a Clear all button and a lock to avoid you closing the app by swiping or via the button. pretty handy!
Now, I had something weird happen to me: When I got my Moto G 2 I used the stock ROM for like 3 days and switched to customs. I never even thought about going back to stock for all the poor phone's life (like 1.5 years). now with this one, I try a couple of ROMs for a month or two, get bored and return to stock. Always happens. Many people say the same, that they started liking the stock ROM even though it strays from AOSP a lot. But it has its fair share of good things, like auto power-on some minutes before your alarm goes off, scheduled on and off, a Dolby Atmos QS tile... It's not bad because it doesn't look like AOSP. not at all.
Besides, MiFavor 5.0 was released for the Chinese and it looks very good!
The phone has hardware keys but the Chinese version hasn't, hence the on screen keys on the screenshot.
Update to O: No news yet, though if it comes, expect the first 2 or 3 builds to be riddled with bugs. ZTE's devs barely know how to use a keyboard. Up to B04 Nougat they broke the Play store then fixed it, broke exFAT for SD cards, then fixed it... People made petitions (basically spamming "We want Android O" on a petition thread on the German forums) but nobody said anything close to a confirmation.
Would I switch from a OnePlus One? 2K AMOLED screen, SD820, speakers better than Samsung's $800 phones come with, QC3.0, for 330 dollars? definitely
The screenshots I attached are from the Chinese MiFavor 5.0 because that's what I'm using right now. You can install it via TWRP if you want.
one thing though: If you can get an A2017U (US version) instead of an A2017 (Chinese Aliexpress version) you're gonna thank me. The U version has so much more development than the G or Chinese... Even people say that sound is better on it. It costs 330 dollars on the US too.
This phone is easy to brick, be REALLY careful and read everything twice before doing stuff or you can end up with a DFU brick which is the most hardcore brick of them all.
Click to expand...
Click to collapse
Wow, that's why I love XDA, thank you for this very helpful reply !
So on official LOS for example microphone during call doesn't work until I toggle loudspeaker ? That's is... Weird . So even if you are running custom ROMs you are coming back to stock because of bugs and features :/
I noticed on videos that launcher and icons sucks. Can I just install nova launcher on stock and use it without any problem ?
About Chinese and American versions. The ROMs doesn't work on all version, the a2017, U and G ? I did some reading and I know there are different bootstacks and stuff but I though the custom ROMs are compatible with all regions.
Is this brick recoverable ? Is there a flashtool that will always rescue me ?
Thanks again !
Yes you can flash nova launcher. It is an app! There is a flashtool for flashing and recovering from soft/hard bricks. The phone just rocks...
FunkyRasta said:
Wow, that's why I love XDA, thank you for this very helpful reply !
So on official LOS for example microphone during call doesn't work until I toggle loudspeaker ? That's is... Weird . So even if you are running custom ROMs you are coming back to stock because of bugs and features :/
I noticed on videos that launcher and icons sucks. Can I just install nova launcher on stock and use it without any problem ?
About Chinese and American versions. The ROMs doesn't work on all version, the a2017, U and G ? I did some reading and I know there are different bootstacks and stuff but I though the custom ROMs are compatible with all regions.
Is this brick recoverable ? Is there a flashtool that will always rescue me ?
Thanks again !
Click to expand...
Click to collapse
It's more complicated than that.
First of all: The modes on this phone are (were):
-EDL (Looks like it's completely off, it's not. You can flash special folder packages with MiFlash when you are in this mode)
-Bootloader mode (Fastboot. On A2017G and U they got rid of it. You can get it back by flashing a zip through TWRP, but if you update the stock ROM officially you'll lose it and will have to flash it again)
-Recovery. You can use axon7toolkit to unlock and install this. One-click tool like the one on Nexus 6 thread.
After you flash the Universal bootloader (for custom ROMs), your TWRP will get overwritten with an older one. Just keep a 3.1.1-0 img file and flash it in this crappy TWRP with Install -> Install image
-FTM. Seems that you get ADB when you are in this mode. Handy when you brick it horribly (no recovery) and can't access EDL. You just issue adb reboot edl and you should get to edl.
And last: DFU mode. Be REALLY careful with EVERYTHING, for example if you flash a system zip and TWRP says that you have no system installed, restore a backup, DON'T reboot! I had a DFU brick once and the two ways to recover from a DFU brick (No EDL, no fastboot, no recovery, very rarely FTM) are to discharge the phone completely and try to get into FTM, or take the phone apart and do the 4th category brick repair manual. I did the latter
But as of now no brick is unrecoverable. With A2017G's and U's you get a pretty overkill warranty, and you can return it claiming that it stopped working all of a sudden for example.
About the launcher: yeah, you can install whatever you like. I use Lawnchair.
And the ROM's work on all 3 phones, but it's the kernels that don't. Kernels work on the G and U on custom ROMs, but there is only one kernel that works for the U on stock, and none for the G. On the G the camera breaks on stock when you use a custom kernel. That's why I recommend you to get a U even if it's a little bit more expensive.
Is there a tool that will always save you from a brick? well there are many, but they will help you like 90% of the time. axon7tool is used to flash stuff to recovery or boot from EDL (you can flash TWRP for ex.), axon7toolkit can do some basic fastboot stuff, and MiFlash is the most useful, cause you can flash a full system directly from EDL and leave your phone in a functional state.So if, say, your digitizer breaks and you are on a custom ROM (and have an A2017G or A2017U, which have warranty) you can simply flash a working system and send it to fix.
If ZTE finds out that the phone has been tampered with (unlocked, opened, etc) they will charge you $80 but they'll fix it. If the phone doesn't even boot and it's a G they'll change it free of charge because of European laws
one more thing: you'll hate the quick settings thingy on stock. Try MiFavor 5.0 if you decide to stay stock, it's a Chinese ROM but with a bunch of work it can get pretty nice. I sent you a couple of screenies there
RUNNERX said:
If you want front facing speakers, yes. If you like the huge amount of roms available for bacon, stay with that. I was on the opo and if it was not for the speakers on the a7 I would switch back.
Click to expand...
Click to collapse
I would go for it because the newer LTE modems are so much better than any of the SD820 especially how poor both the Axon 7 and OP3 signals are compared to the SD821 and SD835. It is night and day in terms of connectivity. Performance wise it's also worth it.
You don't need to flash Nova launcher, I am with the Stock rom and use Nova as it. Just install it and use it as default launcher.
Envoyé de mon ZTE A2017G en utilisant Tapatalk
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
Edit: A solution which can pass Safetynet is HIGHLY preferred
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
xdafan15 said:
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
Click to expand...
Click to collapse
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
I tried stock 7.0 for a few days but went back to Lineage OS. I missed the long press on icons to get actions menu that isn't in 7.0 (among other things).
Spencervb256 said:
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
Click to expand...
Click to collapse
ptn107 said:
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
Click to expand...
Click to collapse
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
xdafan15 said:
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
Click to expand...
Click to collapse
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Spencervb256 said:
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Click to expand...
Click to collapse
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
xdafan15 said:
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
Click to expand...
Click to collapse
No haha it's hard to explain. But until about a month ago, no custom roms could be flashed if users were running stock 7.0 from Moto. Now there are a couple builds of roms which can be flashed over stock 7.0, with no bootloops. This is because Motorola upgraded the modem firmware in stock 7.0, so the custom roms did not work with it.
You can 100% mix the two, so if you are in stock 6.0, you can install any rom you like, as they are made to work with the 6.0 firmware. Even though they are nougat roms.
When stock 7.0 was released, people had issues with installing custom roms over that, because of the modem upgrade, but now there are a couple builds that will install over this firmware and not result in a bootloop.
I will try and find a few links for you which can explain some things, this is all from my mediocre memory haha
If that confused you even more then just stay tuned, I'll send you a pm soon with links to some reading in different threads which explain it much better than I can!
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
Pretty much...
xantanion said:
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
Click to expand...
Click to collapse
aybarrap1 said:
Pretty much...
Click to expand...
Click to collapse
My rule of thumb is simply wait for the official supported OS version. This means everything (including modem) will work - the community will then hack and modify from there.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
That's exactly it! You nailed it. Explained it better than I could, so yeah, you got it!!
I know this is a mostly dead platform, but figured it was worth a shot to ask. My Trek 2 stopped auto-rotating the screen awhile back while it was stock. I had not updated in awhile, so I tossed in an AT&T sim to get it up to date. I did not notice it at first (I use the tablet intermittently) but I am almost certain that update coincided with the screen no longer rotating.
After several months and being tired of manually rotating the screen I took the time to put AOKP on it. Part of my desire was hoping to resolve the screen rotation. It did not. But, I did see a comment in one of the ROM threads where it looked liked someone had the identical issue and it might be related to the software or a minor difference in hardware. Does anyone have any ideas?
Some K88 tablets' auto-rotating only works with MM, not Nougat. Check your current firmware. It will be 7.0.1 or something above 7.0.0, not 6.X.X
The only solution is by flashing K88 back to MM. Sometimes, directly flashing B33 still may not work. So I recommend to flash B31, and then upgrade to B33, but not again to Nougat. Once update to Nougat, then the auto-rotating will not work again. I tried all custom firmware(nougat + oreo), but my K88 auto-rotating is not working with them.
To flash back to B31, you need to install TWRP using jasminetool. And then directly flash B31 stock firmware.
seungbaekm said:
Some K88 tablets' auto-rotating only works with MM, not Nougat. Check your current firmware. It will be 7.0.1 or something above 7.0.0, not 6.X.X
The only solution is by flashing K88 back to MM. Sometimes, directly flashing B33 still may not work. So I recommend to flash B31, and then upgrade to B33, but not again to Nougat. Once update to Nougat, then the auto-rotating will not work again. I tried all custom firmware(nougat + oreo), but my K88 auto-rotating is not working with them.
To flash back to B31, you need to install TWRP using jasminetool. And then directly flash B31 stock firmware.
Click to expand...
Click to collapse
Thanks for chiming in! Any idea what the limitation is? I have LineageOS installed right now, it runs great other than the rotation issue. It looks like all of the custom ROMs are Nougat based, is my only option to go back to stock to get auto-rotation back?