Related
Scanning the forum today, I came across this:
[ROM] Z.A.D.Mix7 -Stock Base Rom-
Click to expand...
Click to collapse
It looks like it would solve all the issues I'm having with my A7:
Enable multi-user mode
Enable on-screen buttons
Replace ZTE's built-in apps.
Is this a safer route to go in general than installing Cyanogenmod (when it's ready)? I've got CM on my Nexus 4, and yes, there's nice stuff there that's probably not here, but is a de-bloated stock ROM more likely to be bug-free? More likely for the camera and sound system to work fully? Also, will a debloated ROM allow for OTA updates - or allow for them to be sideloaded? I guess I'm asking, if I were to install this, what would be the procedure to get Nougat once ZTE comes out with it? Wipe and re-flash? Or wait for a de-bloated ZTE nougat ROM and flash that?
In order to flash a ROM on your axon 7 you need to unlock your bootloader which causes your warranty to be void and you can no longer receive OTA updates. Also if you are running a custom ROM you will have to wipe your phone before flashing an OTA update. However if you are running the stock rom you will probably only need to flash the update. I've tried both CyanogenMod and Z.A.DMix7 and honestly Z.A.DMix7 is definitely the way to go. In my experience using Z.A.DMix7 it seemed to be as stable as the stock rim and didn't have any major bugs. The only problem I had with it is that since it it rooted there is no way to log into Snapchat. How ever if you don't want root I think there may be an way to remove root from the ROM however I haven't tried it so I'm not sure if it'll work.
I use the debloated rom with android n-ify, xStana, and gravitybox and it is much better than the stock rom. I haven't tried the cm rom. You would have to flash the stock rom and recovery to get OTA updates.
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
I'll get to the point:
1) What is currently the best ROM for stability, performance and battery life?
2) From the research I've done myself, Pixel Experience seems to be the best for that, but is 9.0 stable enough to be used as a daily driver or should I stick with 8.1?
3) Do ROMs get OTA updates? As in, if theres a new version of Pixel Experience for example, I can get the update just like any stock update? Would I lose root?
4) If I wanted to go back to stock and start completely from scratch (no root and stuff), all I would need to do is flash a stock image with Mi Flash Tools, right?
5) What is slot A and slot B? Do they matter when I flash a ROM?
6) What permanent TWRP Recovery should I use for ROMs? ComicDan's seems to be the only one for 8.1 that is permanent, but I dont wanna mess with Treble. It also seems that his TWRP cant flash Lineage-based ROMs, but I dont care about Lineage so thats a non-issue
Thanks
Reacerbytes said:
I'll get to the point:
1) What is currently the best ROM for stability, performance and battery life?
2) From the research I've done myself, Pixel Experience seems to be the best for that, but is 9.0 stable enough to be used as a daily driver or should I stick with 8.1?
3) Do ROMs get OTA updates? As in, if theres a new version of Pixel Experience for example, I can get the update just like any stock update? Would I lose root?
4) If I wanted to go back to stock and start completely from scratch (no root and stuff), all I would need to do is flash a stock image with Mi Flash Tools, right?
5) What is slot A and slot B? Do they matter when I flash a ROM?
6) What permanent TWRP Recovery should I use for ROMs? ComicDan's seems to be the only one for 8.1 that is permanent, but I dont wanna mess with Treble. It also seems that his TWRP cant flash Lineage-based ROMs, but I dont care about Lineage so thats a non-issue
Thanks
Click to expand...
Click to collapse
1. It's all about your preferences, preferably go with official roms.
2. Same answer as 1.
3. Only official builds get ota updates, with unofficial builds you have to flash the "ota" via twrp (besides lineage os, unofficial builds also get ota).
4. Correct, you can't restore using twrp because stock image/data are encrypted, you'll end up in a boot loop (found that the hard way ).
5. They do matter, follow the instructions and ONLY the instructions say. Idk what they mean, but newer devices have them.
6. Depending on the rom (from my knowledge), you have to install twrp installer zip everytime you flash a rom.
Hope I cleared that up for you.
I'm on stock 8.1 by the way. I used to use liquid remix 10.
If you ask me what's my favourite rom(s), here is my list in order :
1. Lineage os
2. Pixel experience
3. Dot os
4. Resurrection Remix
When I am flashing any 9.0 custom rom, it installs properly but always there are two camera apps both of which do not work and when I call or receive call the volte icon in status bar disappears and the call drops. The same roms when flashed on my friends mi A1 they work fine. I am not able to understand what the problem is. I have already tried clean flashing stock rom with flashtool. Also Camera was not working in 8.1 custom roms.
ramitzoro said:
When I am flashing any 9.0 custom rom, it installs properly but always there are two camera apps both of which do not work and when I call or receive call the volte icon in status bar disappears and the call drops. The same roms when flashed on my friends mi A1 they work fine. I am not able to understand what the problem is. I have already tried clean flashing stock rom with flashtool. Also Camera was not working in 8.1 custom roms.
Click to expand...
Click to collapse
Which ROM are u flashing exactly? Are you using stock gapps? Stock gapps seem to mess with camera provided by ROM. So try lower version preferbly micro/nano/pico..
WhatzIt2Ya said:
1. It's all about your preferences, preferably go with official roms.
2. Same answer as 1.
3. Only official builds get ota updates, with unofficial builds you have to flash the "ota" via twrp (besides lineage os, unofficial builds also get ota).
4. Correct, you can't restore using twrp because stock image/data are encrypted, you'll end up in a boot loop (found that the hard way ).
5. They do matter, follow the instructions and ONLY the instructions say. Idk what they mean, but newer devices have them.
6. Depending on the rom (from my knowledge), you have to install twrp installer zip everytime you flash a rom.
Hope I cleared that up for you.
I'm on stock 8.1 by the way. I used to use liquid remix 10.
If you ask me what's my favourite rom(s), here is my list in order :
1. Lineage os
2. Pixel experience
3. Dot os
4. Resurrection Remix
Click to expand...
Click to collapse
What made you leave liquid remix? Just asking
---------- Post added at 01:21 PM ---------- Previous post was at 01:16 PM ----------
Reacerbytes said:
I'll get to the point:
1) What is currently the best ROM for stability, performance and battery life?
2) From the research I've done myself, Pixel Experience seems to be the best for that, but is 9.0 stable enough to be used as a daily driver or should I stick with 8.1?
3) Do ROMs get OTA updates? As in, if theres a new version of Pixel Experience for example, I can get the update just like any stock update? Would I lose root?
4) If I wanted to go back to stock and start completely from scratch (no root and stuff), all I would need to do is flash a stock image with Mi Flash Tools, right?
5) What is slot A and slot B? Do they matter when I flash a ROM?
6) What permanent TWRP Recovery should I use for ROMs? ComicDan's seems to be the only one for 8.1 that is permanent, but I dont wanna mess with Treble. It also seems that his TWRP cant flash Lineage-based ROMs, but I dont care about Lineage so thats a non-issue
Thanks
Click to expand...
Click to collapse
1. I dont really know but rn I use liquid remix and it checks all those boxes
2. If you hear the rom is stable it means its stable. No matter the android version. I use liquid remix and its pretty stable and I think pixel experience is even stabler
3. Some roms offer ota through a button in the phone. But most of the roms you will need to reflash the new update through twrp
4. Yes. I don't know what the other guy was talking about but I did that multiple times and it worked fine
5. Not really
6. Use it. Its treble compatible but you dont require to have treble to use it (and again I dont know what the other guy is talking about. Cosmicdan twrp reinstalls itself)
YayJohn said:
What made you leave liquid remix? Just asking
---------- Post added at 01:21 PM ---------- Previous post was at 01:16 PM ----------
1. I dont really know but rn I use liquid remix and it checks all those boxes
2. If you hear the rom is stable it means its stable. No matter the android version. I use liquid remix and its pretty stable and I think pixel experience is even stabler
3. Some roms offer ota through a button in the phone. But most of the roms you will need to reflash the new update through twrp
4. Yes. I don't know what the other guy was talking about but I did that multiple times and it worked fine
5. Not really
6. Use it. Its treble compatible but you dont require to have treble to use it (and again I dont know what the other guy is talking about. Cosmicdan twrp reinstalls itself)
Click to expand...
Click to collapse
I flashed extreme kernel and it won't detect my sim, and the rom became unusable..
I was using Xtended Custom ROM (Oreo) with a rooted device and then i was just trying to unroot the phone and flashing Stock ROM but it didnt worked so i rolled back to Custom ROM and then my fingerprint sensors are not getting detected in any Oreo ROM.. please help!
If you really want to stay on an Oreo custom rom, you have to downgrade to stock nougat first. Easiest way to do that is use the latest nougat twrp flashable stock rom
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Other option is to just go to a pie custom rom.
Edit - just remembered the is another thing you can flash that will just get back the fingerprint, but if you use NFC that won't be fixed. Maybe someone else has the link.
I got my fingerprint sensor back but lost VolTe now!
NZedPred said:
If you really want to stay on an Oreo custom rom, you have to downgrade to stock nougat first. Easiest way to do that is use the latest nougat twrp flashable stock rom
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Other option is to just go to a pie custom rom.
Edit - just remembered the is another thing you can flash that will just get back the fingerprint, but if you use NFC that won't be fixed. Maybe someone else has the link.
Click to expand...
Click to collapse
I got my fingerprint sensor back by flashing "potter-twrp-flashable-NPNS25.137-92-14-a" image but lost Volte support! I am currently using PixelExperience Custom ROM! Oreo based! I am gonna try shifting to a new custom ROM to see if i can get Volte working! If any suggestions please let me know!
If u had nougat and the u flashed PE 9.0 then volte will have issues. PE moved to oreo base long time back. Its better u flash stock oreo first and then move to any Pie Rom. There are some guides around to get volte back might wanna look around. Did you not make a backup of the stock image?
RascalMonk said:
I got my fingerprint sensor back by flashing "potter-twrp-flashable-NPNS25.137-92-14-a" image but lost Volte support! I am currently using PixelExperience Custom ROM! Oreo based! I am gonna try shifting to a new custom ROM to see if i can get Volte working! If any suggestions please let me know!
Click to expand...
Click to collapse
Did you boot into stock nougat before flashing the custom Oreo rom? If not, it is probably necessary. (When you had -a at the end of that filename, I assume you mean aroma? If so, then that one applies a fix to your persist which is needed going back to stock nougat, so that's all good.)
If you did, then it may just be a case of needing to go onto stock Oreo then a pie custom rom. Some things about the stock nougat just don't work properly after being on Oreo...
NZedPred said:
Did you boot into stock nougat before flashing the custom Oreo rom? If not, it is probably necessary. (When you had -a at the end of that filename, I assume you mean aroma? If so, then that one applies a fix to your persist which is needed going back to stock nougat, so that's all good.)
If you did, then it may just be a case of needing to go onto stock Oreo then a pie custom rom. Some things about the stock nougat just don't work properly after being on Oreo...
Click to expand...
Click to collapse
I was originally trying to unroot the phone and getting into stock nougat so that i can get basic updates from moto itself and then i can get into stock oreo but it didnt happen as i wished! now i am stuck in custom oreo with no volte working and way too irritated! since im using volte support sim card i am not able to call anyone or get any incoming calls! please help me what should i do now? i have flashed that persist file with twrp but using custom oreo now! guide me please! need it most!
RascalMonk said:
I was originally trying to unroot the phone and getting into stock nougat so that i can get basic updates from moto itself and then i can get into stock oreo but it didnt happen as i wished! now i am stuck in custom oreo with no volte working and way too irritated! since im using volte support sim card i am not able to call anyone or get any incoming calls! please help me what should i do now? i have flashed that persist file with twrp but using custom oreo now! guide me please! need it most!
Click to expand...
Click to collapse
Ok, so you flashed some persist file? Was it my persist fix zip, or someone else's persist backup, in which case you're kinda screwed.
debdeep98 said:
If u had nougat and the u flashed PE 9.0 then volte will have issues. PE moved to oreo base long time back. Its better u flash stock oreo first and then move to any Pie Rom. There are some guides around to get volte back might wanna look around. Did you not make a backup of the stock image?
Click to expand...
Click to collapse
i am newbie in this so i havent made backup! big mistake!
Got back everything!
NZedPred said:
Ok, so you flashed some persist file? Was it my persist fix zip, or someone else's persist backup, in which case you're kinda screwed.
Click to expand...
Click to collapse
I flashed the "potter-twrp-flashable-NPNS25.137-92-14-aroma" file and got into stock nougat successfully but after i chose to install OTA updates which i got for my device it got stuck in TWRP only! can you help me out here please????
RascalMonk said:
I flashed the "potter-twrp-flashable-NPNS25.137-92-14-aroma" file and got into stock nougat successfully but after i chose to install OTA updates which i got for my device it got stuck in TWRP only! can you help me out here please????
Click to expand...
Click to collapse
Try clearing cache within twrp. You shouldn't take any OTAs from the twrp flashable. If it was the OTA for Oreo, then might be easier to do a wipe, as I can't remember where the OTA gets saved.
I'm assuming that your device is trying to go to recovery all the time as it knows the OTA is there to be installed.
Worst case, total clean flash and install again.
RascalMonk said:
I flashed the "potter-twrp-flashable-NPNS25.137-92-14-aroma" file and got into stock nougat successfully but after i chose to install OTA updates which i got for my device it got stuck in TWRP only! can you help me out here please????
Click to expand...
Click to collapse
Two basic rules:
- Make a backup. Every time before you flash anything. Every time.
- You only can apply and install OTA updates when on a signed and unmodified fastboot firmware.
Twrp flashable ROMs have a lot of advantages but they are not unmodified.
Agree with @NZedPred: Make a full wipe and install
a) a fastboot firmware if you need to take OTA updates, these are found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
b) a twrp flashable ROM if you won't take OTA updates, these are found here: https://forum.xda-developers.com/g5...flashable-stock-builds-coming-t3830482/page68
I have this same problem. I'm currently on stock Oreo and I'm not getting fingerprint option since I flashed PE 9.0. someone help.
Hi guys,
Everything was working great with LineageOS 15.1 (Android 8.1), but they have discontinued the support for this version and switched to 16.0, and a FOTA update of Lineage from 15 to 16 isn't possible, so I had to download the zip manually, and flashed it using TWRP, around the end of April. Since then the Wi-Fi does not work.
I should explain what this "does not work" mean: I turn it on (either from the pull-down curtain, or from the Settings -> Network -> Wi-Fi menu), it pretends to switch on for 1-2 seconds, and then the switch turns off by itself, so it doesn't even have time to scan the available networks.
I have tried to burn a newer image again, around the beginning of May, but it didn't fix the Wi-Fi problem. I was googling a lot, but seems like nobody reports such a problem.
Any ideas how to fix it, other than going back to Android 8.1? Preferably I'd like to stay with LOS, but if I have no choice, I can consider moving to RR, or AOSP Extended or whatever.
Thanks!
I think its a boot.img problem. I have seen this error in stock too. The wifi/bluetooth used to turn off immediately after i turned them on and the error was because i flashed the wrong boot.img . If i were you i would clean flash the rom again
What do you mean by "wrong boot.img"? I don't flash any boot.img separately, I just flash the whole LineageOS rom (and then Gapps) from TWRP. Should I flash anything else? I don't think so...
Well, in my case at least the Bluetooth works properly (with both headphones and smart watch).
SOLVED!
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
xdauseril said:
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
Click to expand...
Click to collapse
It would be safer to update to stock pie first then flash custom pie roms..
Jt380p said:
It would be safer to update to stock pie first then flash custom pie roms..
Click to expand...
Click to collapse
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
xdauseril said:
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
Click to expand...
Click to collapse
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
barrack1 said:
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
Click to expand...
Click to collapse
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
xdauseril said:
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
Click to expand...
Click to collapse
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
barrack1 said:
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
Click to expand...
Click to collapse
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
xdauseril said:
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
Click to expand...
Click to collapse
Some parts of the firmware might not be overwritten by LOS/stock depending on the version. The original LO16 used Oreo firmware iirc. The thread is not hard to find, just look for it.