I upgraded my firmware to the latest prior to loading the 5.0.2 roms. I tried the Rooted 5.0.2 and also my favorite, Bad Boyz 5.0.2 rom. In both cases after installing the rom I noticed that my WIFI would get DNS errors when trying to access websites or any wifi related sites. I have several other android and windows wifi devices on this router and none are experiencing the problems. When I turn the wifi off I can easily access sites again.
So then I decided to reload my previous rom from the twrp backup I created prior to loading any 5.0.2 roms and after the restore was complete I am still having the same DNS problems.
Now before I go further I need to decide if I RUU back to the previous firmware or is this a kernel problem? Does the kernel load with roms and twrp restores?
Hi. I am at a loss on how to fix my GPS on my device. When using Lineage 7.1.2 I can use Google Maps without issue and use navigation to get me places. When I try and use ANY Oreo ROM I can get a GPS lock only on my current location however I can not use navigation; the device stays locked to the start point and will not follow me. When Oreo first came out I was able to upgrade to Oreo and use Maps without issue. I am somewhat a flashaholic and like trying different ROMS to see how they work day to day so I have flashed GZOP, Cardinal, Omni, Lineage 15. I have tried all different Firmware updates by Lord Boeffla trying 4.1.7 (Which I am currently using and Lineage 7.1.2 navigation works) 4.5.0 and 4.5.1 to try and rectify this but it does not matter. No matter what firmware I try and use the results are the same. Lock but will not follow At one point I even tried downgrading to Stock 3.5.4 firmware and software to which I was able to flash but the system would not boot only would bootloop. At this point I am not able to flash any stock OOS ROMS and I must use a custom built ROM such as Lineage to get the phone to boot. I have tried many GPS fix apps such as AGPS to try and force clear GPS cache and reset they system but the results are the same. Lock and no follow. Any ideas on what else can be tried to resolve this? I fear I may have damaged the device throuh flashing the firmware so many times and I will be stuck with Nougat forever with the current phone.
All Oreo ROM's are in Alpha/Beta build stages. I've experienced similar results on many Oreo ROMs. The best course of action you can take is providing logs to the developers of the consecutive ROM, and let them work.
Different firmware versions don't make any difference to the GPS. ROM's are built on top of the firmware, and such. Flashing different firmware's will not fix the issue. Go back to Nougat if you want a stable system.
The issue here is you're complaining about bugs on Alpha/Beta ROM's.
I have been facing the same problem in Nougat Roms too. I think it has been introduced in 4.1.7
The only course of action would be to get it fixed in Beta OOS by providing the logs to the devs.
Here's a related thread :
https://forum.xda-developers.com/oneplus-3t/help/poor-gps-oos-4-1-7-t3664864
Had same issue, refresh latest beta firmware.
I've no issue using gmaps on ob 17 I use it daily.
Hello Friends:
This method is Only for MOTO G5S Montana XT-179x @XT-1799-2 i am not sure
please don't try at any Other Device and if you stuck anywhere ask anytime...
Here is tested fix for Fingerprint Sensor Activation in Custom Oreo 8.1 and PIE 9.0 ROMs Thanks to @JarlPenguin
Follow the steps Below:
For Oreo 8.1 Custom ROMs:
1: Flash your favorite Oreo 8.1 Custom ROM (Set Up Your ROM)
2: Download file from the Link here: https://mega.nz/#!Az5EBYxC!_fqx-2iHD9KiddRwTgd3yharQ61jINDOcYjNLJnE-d4
3: Extract the Folder anywhere in PC
4: Connect your Phone in Bootloader mode with PC
5: Open Extracted Folder and just Run "Flash downgrade.bat"
6: Wait to end process and than Start Phone with power Button.
Your Fingerprint Must show in Security and Location setting, add fingers and Enjoy (I have tested at XT-1794 with PE Oreo)
For PIE 9.0 Custom ROMs:
1: Flash your favorite Oreo 9.0 Custom ROM (Set Up Your ROM)
2: Download file from the Link here: https://mega.nz/#!w3xEBCBb!MXvDbcxWY7TeiHmnzHFJT61yIOIzJIPJ6wNI9JGFkGY
3: Extract the Folder anywhere in PC
4: Connect your Phone in Bootloader mode with PC
5: Open Extracted Folder and just Run "Flash downgrade.bat"
6: Wait to end process and than Start Phone with power Button.
Your Fingerprint Must show in Security and Location setting, add fingers and Enjoy (I have tested at XT-1794 with PE PIE
Hit Thanks if you find this Guide a comprehansive to Fix the Fingerprint at your Device, because many times i went to bootloop While using TWRO fix, but this fix work Flawless:
Credits: @JarlPenguin
Reserved for More Links and Updates:
You are the best.
Thanks.
felipe.090487 said:
You are the best.
Thanks.
Click to expand...
Click to collapse
Welcome.
Xt1799-2 will only be able to flash Oreo ROMs for fingerprint because it isn't updated to Oreo/Oreo firmware isn't in the mirrors so we can't access the fingerprint driver files
JarlPenguin said:
Xt1799-2 will only be able to flash Oreo ROMs for fingerprint because it isn't updated to Oreo/Oreo firmware isn't in the mirrors so we can't access the fingerprint driver files
Click to expand...
Click to collapse
XT-1799 will.never have a stock Oreo so...
To get Fingerprint work just follow this guide.
https://forum.xda-developers.com/moto-g5s/how-to/guide-fix-fingerprint-sensor-oreo-8-1-t3900508
I'm using pixel experience room and using fingerprint sensor as an unlocker works for me, but it seems that I can't use fingerprint gestures anymore. any solutions?
edit: fixed! thanks
zahidm said:
Hello Friends:
This method is Only for MOTO G5S Montana XT-179x @XT-1799-2 i am not sure
please don't try at any Other Device and if you stuck anywhere ask anytime...
Here is tested fix for Fingerprint Sensor Activation in Custom Oreo 8.1 and PIE 9.0 ROMs Thanks to @JarlPenguin
Follow the steps Below:
For Oreo 8.1 Custom ROMs:
1: Flash your favorite Oreo 8.1 Custom ROM (Set Up Your ROM)
2: Download file from the Link here: https://mega.nz/#!Az5EBYxC!_fqx-2iHD9KiddRwTgd3yharQ61jINDOcYjNLJnE-d4
3: Extract the Folder anywhere in PC
4: Connect your Phone in Bootloader mode with PC
5: Open Extracted Folder and just Run "Flash downgrade.bat"
6: Wait to end process and than Start Phone with power Button.
Your Fingerprint Must show in Security and Location setting, add fingers and Enjoy (I have tested at XT-1794 with PE Oreo)
For PIE 9.0 Custom ROMs:
1: Flash your favorite Oreo 9.0 Custom ROM (Set Up Your ROM)
2: Download file from the Link here: https://mega.nz/#!w3xEBCBb!MXvDbcxWY7TeiHmnzHFJT61yIOIzJIPJ6wNI9JGFkGY
3: Extract the Folder anywhere in PC
4: Connect your Phone in Bootloader mode with PC
5: Open Extracted Folder and just Run "Flash downgrade.bat"
6: Wait to end process and than Start Phone with power Button.
Your Fingerprint Must show in Security and Location setting, add fingers and Enjoy (I have tested at XT-1794 with PE PIE
Hit Thanks if you find this Guide a comprehansive to Fix the Fingerprint at your Device, because many times i went to bootloop While using TWRO fix, but this fix work Flawless:
Credits: @JarlPenguin
Click to expand...
Click to collapse
Im on pixel experience , getting very slow network but fingerprint is working good.
So will it help if i follow this ghuide?
Current baseband version
M8937_37.13.03.64R
NON-HLOS.bin
Hey. I installed RETEU for XT1793, the version OPPS28.65-37-7-6, the firmware got up to normal, then I installed crDroid v4.7.2 x64 nfc and camera function works. The problem is in the fingerprint, I install the files from the archive (Files4Downgrade) the fingerprint works but the firmware of the communication module flies, the imei disappears, specifically the problem is in the NON-HLOS.bin file. I install this file from the firmware, the connection is working, the fingerprint not working. Who faced How did you solve the problem? Maybe there is an updated file NON-HLOS.bin for OPPS28.65-37-7-6
Unfortunately, this "fix" removes IMEI/baseband from my device (montana), no signal/network on SIM. (Flashed over stock 8.1, and Pixel Experience 9.0).
Had to go back to stock again(via fastboot flash), update to latest version using OTA (wifi) updates, and then I got IMEI (baseband) back.
iChronox said:
Unfortunately, this "fix" removes IMEI/baseband from my device (montana), no signal/network on SIM. (Flashed over stock 8.1, and Pixel Experience 9.0).
Had to go back to stock again(via fastboot flash), update to latest version using OTA (wifi) updates, and then I got IMEI (baseband) back.
Click to expand...
Click to collapse
You can extract these files from your own stock ROM and perform this procedure, may be your variant is different
zahidm said:
Hello Friends:
This method is Only for MOTO G5S Montana XT-179x @XT-1799-2 i am not sure
please don't try at any Other Device and if you stuck anywhere ask anytime...
Here is tested fix for Fingerprint Sensor Activation in Custom Oreo 8.1 and PIE 9.0 ROMs Thanks to @JarlPenguin
Click to expand...
Click to collapse
Do I need to flash this if I am coming from Stock 8.1 and moving to Lineage 15.1 based on 8.1 ?
rizwan.mahai said:
Do I need to flash this if I am coming from Stock 8.1 and moving to Lineage 15.1 based on 8.1 ?
Click to expand...
Click to collapse
No, if you are going to LOS 16 Then
what about Moto g5s plus ?????
Puvan said:
what about Moto g5s plus ?????
Click to expand...
Click to collapse
It's different device. Check threads connected to your device. Moto G5S and Moto G5S PLUS are very different
JarlPenguin said:
Xt1799-2 will only be able to flash Oreo ROMs for fingerprint because it isn't updated to Oreo/Oreo firmware isn't in the mirrors so we can't access the fingerprint driver files
Click to expand...
Click to collapse
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
XT1799-2_MONTANA_RETCN_7.1.1_NZS26.68-117_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the xt1799-2 zui android 7.1.1 firmware, hope it can help you.
iChronox said:
Unfortunately, this "fix" removes IMEI/baseband from my device (montana), no signal/network on SIM. (Flashed over stock 8.1, and Pixel Experience 9.0).
Had to go back to stock again(via fastboot flash), update to latest version using OTA (wifi) updates, and then I got IMEI (baseband) back.
Click to expand...
Click to collapse
My device is moto g5s xt1799-2.
I download this file and unzip it.
I see it contain 'NON-HLOS.bin' and 'fsg.mbn' files.
These two files are related to the baseband, IMEI, network, fingerprint. Since moto's baseband can only be upgraded but not be downgraded, if you upgrade it and it's not match your device's firmware, your network and signal will be empty, your IMEI will turn 0.
The only solution is restore the 'EFS' and 'Persist' partitions backup via twrp. So you must make a twrp backup in twrp before you try the method.
Why do I know that? Long story. Ha~ Some apps don't offer 32bit version anymore since early this year. The latest version of those apps don't support my device. Since moto doesn't offer a firmware upgrade for xt1799-2 (the last firmware is android 7.1.1 zui), I need to upgrade my os version. (Actually it doesn't matter with the android os version. The 32bit os version is the problem! ) First I flash the lineageos 18.1, but I see from its website that device should be in 8.1.0 os version, but you know, moto doesn't give our xt1799-2 users. I ignore that and try to flash it. Then it stuck it the lineageos boot animation. Then I search on the net and find if any way to upgrade my xt1799-2 to 8.1.0 oreo, and find a page. I follow the method and upgrade my device to oreo 8.1.0. Since I was new to it at that time, I did follow all the steps it listed and flash the 'NON-HLOS.bin' and 'fsg.mbn' files. Only to find that it's still 32bit os version! One app I use most runs inefficiently in stock oreo 8.1.0 and the os kills my background app. So I want to downgrade to zui 7.1.1 os, and find that my IMEI turns 0 and network signal is empty. Worst of all, the battery drains 3-5% per several minutes (not hour)!!! I even can't unplug my device from the power. Then I search from the web. and do many tests and find out that is because I flash the BP (baseband part: 'NON-HLOS.bin' and 'fsg.mbn' files). And know that moto's BP can only be upgraded but not be downgraded. So I keep the baseband version stay in stock oreo 8.1.0 and only downgrade the AP (system part). Then I found my fingerprint is not working. Then I downgrade the BP and it's back but no signal and IMEI 0. Since I didn't know that issue before and didn't backup the 'EFS' and ‘Persist’ partitions in twrp (I even don't know twrp at that time.). Finally, I search from the net that the solution is to flash a full upper firmware which network, signal, and IMEI are all fine and stay in that version (For my case is moto stock oreo 8.1.0 ). Then make an 'EFS' and 'Persist' backup in twrp.
Thanks to the twrp backup. I flash many third party roms recently (More than 10 roms.) Sometimes when I flash back to stock oreo 8.1.0, I can see my baseband change itself. Like, 57R baseband version for my xt1799-2 in moto stock oreo 8.1.0 everything is fine. But it will change to 57e, sometimes 57U when I flash the AP(system part). Both of them network signals are empty. Then I need to restore my 'EFS' and 'Persist' backup in twrp, power off the device and boot into the system. Then you will see in the 'About phone' page', it's back to 57R, everything is fine again. And you power off not restart, and boot to bootloader, you will see the baseband is back to 57R.
Another weird thing is that I have another moto g5s xt1799-2. I keep the baseband version of it in zui's last firmware 7.1.1(NZS26.68-117) that is 54R. When I flash AP (system part) of stock oreo 8.1.0, its signal it empty sometimes is full, but both can't make a call and surf internet. But when the 54R device flashes a third party 8.1.0 rom, like crDroid and AICP, VoLTE works! But when the 54R device flashes a third party 9.0 and 10 rom, no network signal again! So I don't think it's the matter with the baseband version, otherwise the third party 8.1.0 rom will no signal, but it doesn't happen. VoLTE works in the third party 8.1.0 rom, but not the moto stock oreo 8.1.0 rom.
[Important] Read this before FLASHING/Updating to Stock PIE 9 {SPRINT,TMO AT&T ETC}
Mates! for newbies specially Sprint,TMO and Atn&t users I know you are sad to hear that you won't get stock Pie update and you have been watching threads here on XDA showing how to flash captured Stock Pie of Verizon/Brazil variant on your Sprint ,at&t TMO variants this very important to know that DO NOT UPDATE/FLASH 9.0 Pie update of Verizon/Brazil variants. Otherwise you will loose your IMEI, Baseband N, modem. AND definitely NO WIFI and there is turning back
That update only works for Verizon/brazil variant devices which are getting updates by Motorola it's not for sprint at&t tmo etc THIS ONLY WORKS FOR VARIANTS WHICH ARE ANNOUNCED BY MOTO.
Reasons: when you flash stock pie your Oreo modem is replaced with Pie modem which doesn't matches to your variant which results in loosing of imei,base band and wifi.
Even if you try to flash back oreo with a clean flash you may be able to use your stock oreo but due to pie modem you won't be able to downgrade to your oreo modem and in result your imei baseband will still be gone with pie and there is no solution haven't been found yet.
Please if you really want to use pie there are other custom roms like Dirty Unicorns, CR Droid,Havoc and Lineage OS use them till the developers found an solution for this problem. Thank you!
just don't flash modem,see no problems.sprint - pie
Can at&t ariants flash it?
As it is locked...
Dreamerok said:
just don't flash modem,see no problems.sprint - pie
Click to expand...
Click to collapse
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
KOAO said:
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
Click to expand...
Click to collapse
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
found this
Found this forum:
bbs.ixmoe.com/t/topic/22171
Could be a solution to unbrick ?
Dreamerok said:
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
Click to expand...
Click to collapse
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated ??
gokart2 said:
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated
Click to expand...
Click to collapse
work fine for me. some bugs with wifi (quick connect disconect sometimes)
battery better. twrp * magisk + gpay ) gcam last works perfect. motocamera & motoprojector ? moto verve buds work
Just came to me....there might be a way to revert back firmware. Way back in 3vo 3d days there was a Boost mobile update that had a newer Android version then what the Sprint people got. So many of us flashed it and had problems. And couldn't revert back.
The best kernel dev I've seen to date (name cannot be given due to settlement between him an xda) found he could hex edit the previous bootloaders version number to be post the Boost version, which then allowed it to flash. And we could then revert back to the Sprint firmware/ROM. I don't know how Moto checks or limits firmware flashing, but just an idea?
I have same problem but i had Lineage OS Backup and flashed it. Now I have normal Lineage OS on Partition B and Lineage OS with Problem on Partition A. (Official Rom only uses A partition, Lineage OS supports A/B partition update). I don't know if there is any way to copy B partition IMEI and Baseband on Partition A.
Moto z2 force sprint
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
can you update what have you done?
Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
I have the same problem. Can I fix it somehow?
For about a couple of weeks I run crDroid 7.16. This because I think an EOL A11 rom is developed out with minimal bugs.
Inside the flashing instructions I didn't read nothing about flashing Xiaomi firmware before, so I didn't think about that.
My Xiaomi firmware version was 12.5.3.0. EEA and flashing crDroid didn't give problems.
But viewing build.prop I saw the rom was based on v. 12.5.4 Global
Although I haven't problems, I wonder if it wouldn't be wiser to flash 12.5.4 Global after all
However, I want to avoid a bootloop, format or other surprises.
That's why I have some questions
- Can I flash the Xiaomi firmware without a clean install?
- Or is it better to dirty flash crDroid, Gapps, Magisk and decrypt again too?
- Or is it better to flash the latest A11 firmware 12.5.9 Global?
- Or leave it as it is?
You would need to do a clean installation because you'll be changing firmware. However, you said you're device region is EEA. No need to change anything. EEA and Global variants are roughly the same but it is best to stick to your region firmware.
BigChungus321 said:
You would need to do a clean installation because you'll be changing firmware. However, you said you're device region is EEA. No need to change anything. EEA and Global variants are roughly the same but it is best to stick to your region firmware.
Click to expand...
Click to collapse
Thanks for your answer.
I don't talk about installing complete Miui rom, but firmware from which is mentioned here
This is only a part of a complete Miui rom. Is clean install than really neccesary?
I ask because I read on another tread
"Firmware is simply the bootloader, modem and baseband files that are responsible for bluetooth, wifi and all wireless connections on the device, it is only necessary to update if you are coming from a very old version of the stock ROM."
That's why I have some doubts if it makes much difference
Personally, running previously on ArrowOS 11 then 12, now on LOS, I've been dirty updating firmware without flashing rom, by flashing it with twrp, cleaning cache and dalvik, and everything is ok.