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.
Related
Hey guys! I'm trying to understand on which stock ROM you have flashed a Nougat custom ROM.
Personally, I'm on the latest RETEU 6.0.1 MPDS24.107-52-5 + January security patch (I don't remember, maybe 107-70) and I run AospExtended 4.3 with Optimus kernel r21.
So... what's your base firmware? Is it all ok?
I am using the combination you read in my signature. I have to disable HW overlays after every restart in order to have full screen video and stock camera working right. Except those, the device is faster and i love it.
melodystyle2003 said:
I am using the combination you read in my signature. I have to disable HW overlays after every restart in order to have full screen video and stock camera working right. Except those, the device is faster and i love it.
Click to expand...
Click to collapse
And what is the stock ROM you have on the base?
Hm, didn't notice that part of your question from my tablet. If it may be of any help, i was using stock mm 6.0.1 but i erased system, data, cache and dalvik (clean installation) prior flasing the AOSiP 6.0.
melodystyle2003 said:
Hm, didn't notice that part of your question from my tablet. If it may be of any help, i was using stock mm 6.0.1 but i erased system, data, cache and dalvik (clean installation) prior flasing the AOSiP 6.0.
Click to expand...
Click to collapse
The latest? And which version? European, Asian...
This one: XT1562_LUX_RETASIA_DS_6.0.1_MPDS24.107-52-5_cid7_subsidy-DEFAULT_CFC (which i used to convert it from single sim to dual sim). There is also a newer one, you can find it here.
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
+1
ajeteja said:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
Click to expand...
Click to collapse
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
NZedPred said:
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Click to expand...
Click to collapse
Yes I was on soak test. Pls help Moto g5s plus
@NZedPred Can you pls help? I am also facing the same issue.
#shubham Bane/- said:
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Yes I was on soak test. Pls help Moto g5s plus
Click to expand...
Click to collapse
kiranbala003 said:
@NZedPred Can you pls help? I am also facing the same issue.
Click to expand...
Click to collapse
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
@NZedPred thanks man. It worked
kiranbala003 said:
@NZedPred thanks man. It worked
Click to expand...
Click to collapse
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
ugander1989 said:
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
Click to expand...
Click to collapse
Step by step instructions are in my post above... Do you have a more specific question?
Does this work with moto G5s plus [sanders]
Will the above method work with moto g5s plus sanders
sarath6622 said:
Will the above method work with moto g5s plus sanders
Click to expand...
Click to collapse
Yes, if you did the same thing, i.e. flashed stock Oreo and then went to an Oreo custom rom, then yes the same approach will work. I have a flashable build and persist fix for sanders here:
https://www.androidfilehost.com/?w=files&flid=280579
Clean flash/Dirty flash?
@NZedPred I am facing the same problem. I own the Indian Moto G5 Plus (retin)
Here's what I did -
1. I unlocked my bootloader
2. I updated to Oreo (soak test) using the OTA capture.
2. I somehow rooted my phone after flashing TWRP.
3. Just after I flashed TWRP i.e. before rooting, I took a complete backup including the persist and EFS partitions.
4. After rooting, I clean installed MSM-Xtended ROM (8.1.0)
5. Everything is fine, but the fingerprint feature doesn't work/appear anywhere. Even the gesture support is gone.
What do I need to do?
If I follow your steps mentioned above i.e. flashing the persist-fix first, flashing the Nougat ROM you provided and then flashing any custom ROM, how should I proceed?
I am really confused whether I should clean flash (Wipe Data, System, Cache) after every step or dirty flash everything.
Please guide me.
Before you go back to custom ROM from stock Oreo ROM you have to flash stock nouget ROM if not fingerprint , NFC will not work.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
@sinchan_nohara
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
U wrongly flashed firmware, try Oreo custom rom
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
dhinesh_cool said:
U wrongly flashed firmware, try Oreo custom rom
Click to expand...
Click to collapse
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
navinsingh said:
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
Click to expand...
Click to collapse
ask in telegram grp
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.
Are there any custom Oreo based ROMs that can be flashed directly over stock Oreo without issues like missing fingerprint functionality?
Thanks.
Every Oreo based ROM can be flashed over stock ROM, however it will end-up with unprecedented errors, and possibilities of soft-brick/hard-brick can not be avoided.
However, if you are looking for a custom ROM closed to stock, try flashing LOS, for which you need the bootloadwe to be unlocked.
checksamir said:
Every Oreo based ROM can be flashed over stock ROM, however it will end-up with unprecedented errors, and possibilities of soft-brick/hard-brick can not be avoided.
However, if you are looking for a custom ROM closed to stock, try flashing LOS, for which you need the bootloadwe to be unlocked.
Click to expand...
Click to collapse
Thank you. I tried that one and it needs blobs from Nougat apparently. When flashing LOS 15.1 over stock oreo, the fingerprint sensor doesn't work.
badtlc said:
Thank you. I tried that one and it needs blobs from Nougat apparently. When flashing LOS 15.1 over stock oreo, the fingerprint sensor doesn't work.
Click to expand...
Click to collapse
Some ROMs (mostly pie) need Oreo as base but a lot of Oreo ROMs need Nougat because stock Oreo wasn't released that time, that's also the reason why many Oreo custom ROMs are a bit unstable. Ask the developer what base is needed to be on the safe side.
In your case I recommend flashing a twrp stock nougat ROM:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
After that reflash your preferred Oreo ROM.
If you haven't done it yet make a backup of EFS and persist with the latest TWRP 3.2.3.1 to avoid losing your IMEI and/or 4g.
Read the OP of the above thread:
An important note for those who have flashed custom Oreo roms
It is a frequent issue regarding Oreo roms that the device's IMEI is set to 0 in certain conditions. It is possible that these roms (or something used with them) are tampering with the persist partition of the devices. When this occurs, if the EFS is erased, it is not reconstructed correctly.
Click to expand...
Click to collapse
Wolfcity said:
Some ROMs (mostly pie) need Oreo as base but a lot of Oreo ROMs need Nougat because stock Oreo wasn't released that time, that's also the reason why many Oreo custom ROMs are a bit unstable. Ask the developer what base is needed to be on the safe side.
In your case I recommend flashing a twrp stock nougat ROM:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
After that reflash your preferred Oreo ROM.
If you haven't done it yet make a backup of EFS and persist with the latest TWRP 3.2.3.1 to avoid losing your IMEI and/or 4g.
Read the OP of the above thread:
Click to expand...
Click to collapse
I tried doing the backup in TWRP. Not sure I got it backed up right. I have the following files in my TWRP backup folder my external SDcard:
- efs1.emmc.win
-efs1.emmc.win.sha2
- efs2.emmc.win
- persist.ext4.win
- persist.ext4.win.sha2
- persist.info
- recovery.log
Does that look like the correct number and type of files to have for backup? Thanks.
badtlc said:
I tried doing the backup in TWRP. Not sure I got it backed up right. I have the following files in my TWRP backup folder my external SDcard:
- efs1.emmc.win
-efs1.emmc.win.sha2
- efs2.emmc.win
- persist.ext4.win
- persist.ext4.win.sha2
- persist.info
- recovery.log
Does that look like the correct number and type of files to have for backup? Thanks.
Click to expand...
Click to collapse
Looks good.
I have a lot of problems with this device.
After installing Lineage OS 17, everything works, except the wifi. Then i installed the 17.1 version.
The wifi was fixed, but then, i lose every sound. the phone is literally muted.
Can you help me?
RazorNitro74717 said:
I have a lot of problems with this device.
After installing Lineage OS 17, everything works, except the wifi. Then i installed the 17.1 version.
The wifi was fixed, but then, i lose every sound. the phone is literally muted.
Can you help me?
Click to expand...
Click to collapse
when you installed it did you have the firmware of miui 10.2.5? The same thing happened to me with all the roms until I discovered that was why, install that version with xiaomi flash tool, then flash the recovery and install it
neo.alarrode said:
when you installed it did you have the firmware of miui 10.2.5? The same thing happened to me with all the roms until I discovered that was why, install that version with xiaomi flash tool, then flash the recovery and install it
Click to expand...
Click to collapse
try dirty flashing the rom, or go ahead and go back to stock rom and re flash LOS.
mightLy said:
try dirty flashing the rom, or go ahead and go back to stock rom and re flash LOS.
Click to expand...
Click to collapse
he needs firmware version 10.2.5, so he has to do it by flashing the original phone fimware from the computer
RazorNitro74717 said:
I have a lot of problems with this device.
After installing Lineage OS 17, everything works, except the wifi. Then i installed the 17.1 version.
The wifi was fixed, but then, i lose every sound. the phone is literally muted.
Can you help me?
Click to expand...
Click to collapse
I have also that problem. No sound even when i back to previously build MIUI 10 and flash Lineage.
Also on MK rom (23.03.2020).