Good morning on this first christmas day,
I've tried to revert back to nougat after I found out the oreo update is a big, buggy mess.
But when I flash the official revert zip (the one from ob2) my wifi doesn't work until I flash the oreo rom again. The flash goes accompanied by a full wipe in the original op recovery.
Does someone know how to properly revert back to stable nougat from OOS5.0 oreo without wifi malfunctioning?
Thanks for your help and have a blessed christmas.
You call the latest Oreo a big and buggy mess when you can't even find your way around to revert to Stable N?
Believe me, when you follow the rules and search, things get easier. Latest Oreo is rock solid and with good battery life as well. Talking about battery life, I have lost only 4% overnight with mobile data on.
Don't call people's hard work a mess when you mess around yourself.
Back up data on pc , format data then flash official 4.5.15
kaaseter said:
Good morning on this first christmas day,
I've tried to revert back to nougat after I found out the oreo update is a big, buggy mess.
But when I flash the official revert zip (the one from ob2) my wifi doesn't work until I flash the oreo rom again. The flash goes accompanied by a full wipe in the original op recovery.
Does someone know how to properly revert back to stable nougat from OOS5.0 oreo without wifi malfunctioning?
Thanks for your help and have a blessed christmas.
Click to expand...
Click to collapse
I don't know what bugs you are talking about. I have Oreo stable and there are no bugs for me. I recommend going to the ROM development forum for this phone and looking into xxx NoLimits ROM by xxx. It is quite stable imo.
However, if you really want to go back to Nougat, you are going to have to format your phone (system, data, internal storage, and both cache) and install the Nougat ROM through TWRP.
Yousvel said:
You call the latest Oreo a big and buggy mess when you can't even find your way around to revert to Stable N?
Believe me, when you follow the rules and search, things get easier. Latest Oreo is rock solid and with good battery life as well. Talking about battery life, I have lost only 4% overnight with mobile data on.
Don't call people's hard work a mess when you mess around yourself.
Click to expand...
Click to collapse
What does not being able to revert back to Nougat have to do with Oreo being buggy? Before you insult someone else, make sure you know what logic is.
kaaseter said:
Good morning on this first christmas day,
I've tried to revert back to nougat after I found out the oreo update is a big, buggy mess.
But when I flash the official revert zip (the one from ob2) my wifi doesn't work until I flash the oreo rom again. The flash goes accompanied by a full wipe in the original op recovery.
Does someone know how to properly revert back to stable nougat from OOS5.0 oreo without wifi malfunctioning?
Thanks for your help and have a blessed christmas.
Click to expand...
Click to collapse
first u need to flash ROLL Back Zip....search it on Oreo Public Beta release....that what happen when u revert to N from O
wifi show "saved/disabled"
Yousvel said:
You call the latest Oreo a big and buggy mess when you can't even find your way around to revert to Stable N?
Believe me, when you follow the rules and search, things get easier. Latest Oreo is rock solid and with good battery life as well. Talking about battery life, I have lost only 4% overnight with mobile data on.
Don't call people's hard work a mess when you mess around yourself.
Click to expand...
Click to collapse
Its not about just battery life. What about degraded camera performance, worse eis and screen casting issues. Not calling anyone's hard work, I know the team has worked hard but the update was not up to the expectation and looks like its still partially baked. It takes time. Remember how we got a stable N after a series of update. So there's no point i find to say the O a stable ROM as of now.
Download this one and Blu spark TWRP 8.61 then transfer those to your phone. After wiping dalvik cache, flash this stock rom and now do a factory reset from wipe menu by sliding the bar and format the data by typing yes. Now flash the 8.61 Blu TWRP again because it's gone. Reboot and that's all.
Related
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].
What you guys suggest!? I want to root my Phone but I am waiting for The Oreo Update
Should I wait Further or not!?
Personally I was wondering the same, but decided a week or so ago to unlock the bootloader and install lineage 14.1. Happy with my decision, it actually fixed a bug I had with NFC only working occasionally. Also good to be able to use my root apps again. I won't upgrade to Oreo until after the official Oreo release and developers have had a chance to fix the issues there seems to be with Bluetooth calling, votle, imei, etc.
So my answer would be sure go ahead, as long as you know what you're doing it for and understand the risks.
I agree with NZedPred, nothing wrong with rooting and installing custom rom, but I wouldn't install any Oreo rom until/if official Oreo for this device gets released. Just too many problems.
Same here waiting for Oreo before root
Rutambh said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post76427271
Click to expand...
Click to collapse
If you can fix the various common problems that may come with custom ROMs, go ahead. Otherwise, you could stay stock and wait for the update. It all depends on you if you want to have the latest Oreo (8.1 and the latest security patches).
If you just want to root, it's fine too but you'll still lose warranty.
Not sure, i have zero problems on ResurrectionRemix Oreo.
I was thinking the same and now i'm glad that i did it. RR working like a champ.
some custom rom are stable and u can use for daily driver
I'll wait. There's nothing revolutionary about Android 8, the custom roms are almost always buggy, and also all these reports of IMEI 0 are troublesome.
Has anyone tried dirty unicorn rom i looked through their official website but did find not anything about its features. My questions are
1. I have not unlocked my bootloader yet and i want to try only this rom. Is this stable enough as daily driver are there any bugs.
2. Does it support volte and how is call and audio quality these three are most important to me specifically audio quality and Volte.
Works great, volte & call quality are fine. Running 05.11 so can't speak for the latest 03.09. Camera is working 90% but that's to be said of all Oreo ROMs at the moment. Word of caution if you go from stock to Oreo be sure to back up your EFS partition because you'll lose volte if you go back to stock from Oreo. If you want to go back to stock from Oreo you have to first flash custom nougat then stock nougat. That's worked for me anyway, I'm sure I'll get corrected if that's not the case. Happy flashing ?
Xt1687
Metro/TMO
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.