Database Develop

Suddenly fails to find any network operators

My son's Moto X with unofficial Lineage OS 13 has been working just fine until today, when it suddenly stopped finding any network operators. The SIM card is still recognized, I may enter the pin, but then it says "No service", and when I go to network operators choice, I find that not a single operator is displayed.
I tested the SIM in another phone, it seems to be fine. I also inserted different sim, which I know to work into this phone, but that did not help.
This is what I get from adb logcat, but I can't make sense of it:
XXXXXXXXXXX simSlotIndex=0 displayName=Willkommen carrierName=No service nameSource=0 iconTint=-16746133 dataRoaming=0 [email protected] mcc 26
2 mnc 7 mUserNwMode=9}]
01-07 18:11:59.254 1572 1572 D NetworkSettings: onSubscriptionsChanged: Slot matched SimSlotIndex: 0
01-07 18:11:59.257 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1572 3902 D OpenGLRenderer: endAllStagingAnimators on 0x99f02e00 (RippleDrawable) with handle 0x9d070520
01-07 18:11:59.361 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.361 1833 1833 D KP2AAF : event: 32, package = com.android.phone
01-07 18:11:59.361 1833 1833 D KP2AAF : event package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : root package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : URL=androidapp://com.android.phone
01-07 18:11:59.368 1833 1833 D KP2AAF : Cancel notif
01-07 18:11:59.438 1881 6159 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.458 1881 1903 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.575 1572 1572 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
01-07 18:11:59.579 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.634 1572 1572 I art : Explicit concurrent mark sweep GC freed 29733(3MB) AllocSpace objects, 7(156KB) LOS objects, 40% free, 10MB/17MB, paused 610u
s total 41.233ms
01-07 18:11:59.656 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.676 1572 1572 I art : Explicit concurrent mark sweep GC freed 13973(846KB) AllocSpace objects, 2(80KB) LOS objects, 39% free, 9MB/15MB, paused 640u
s total 19.563ms
01-07 18:11:59.676 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.691 1881 1901 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.695 1572 1572 I art : Explicit concurrent mark sweep GC freed 3(96B) AllocSpace objects, 0(0B) LOS objects, 40% free, 9MB/15MB, paused 579us total
19.136ms
01-07 18:12:00.121 21030 21030 W ps : type=1400 audit(0.0:1428831): avc: denied { getattr } for path="/proc/1" dev="proc" ino=3578 scontext=u:r:untrusted_app:s0:c5
12,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
01-07 18:12:00.145 1833 1833 D KP2AAF : OnAccEvent
01-07 18:12:00.145 1833 1833 D KP2AAF : event: 2048, package = com.android.systemui
01-07 18:12:00.145 1833 1833 D KP2AAF : return.
Could it be that suddenly the hardware has become faulty? Does anybody have suggestions how to test for the cause?
Thanks very much in advance!!!

Did a factory reset, which did not solve it. Still no network operators found.

Trying to understand the problem. logcat reveals that when it scans for networks, something goes wrong:
IsDataRoamingFromRegistration=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false IsDataRoamingFromRegistration=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1
Can someone enlighten me, what CSS stands for?

Now I spotted more errors:
01-10 15:54:50.960 2132 2132 D DCT : [0]stopNetStatPoll
01-10 15:54:50.964 2132 2132 D DCT : [0]overall state is IDLE
01-10 15:59:14.763 2132 2795 D RILJ : [4000]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB0]
01-10 15:59:14.770 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_req_log: req QMI NAS, msg id: 67, e len:0
01-10 15:59:14.804 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_resp_log: rsp - QMI NAS, msg id: 67, e len:7
01-10 15:59:14.804 2132 2243 D RilRequest: [4000]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
01-10 15:59:14.804 2132 2132 D GsmSST : [GsmSST] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-10 15:59:14.804 2132 2795 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
01-10 15:59:14.805 2132 2795 D GsmSST : [GsmSST] getCellLocation(): X empty mCellLoc and CellInfo mCellLoc=[-1,-1,-1]
01-10 15:59:14.817 1929 3007 D TelephonyManager: getCellLocation returning null because CellLocation is empty
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): return last, back to back calls
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
This "Generic failure" sounds spooky to me. As if something about the hardware is broken.

yahya69 said:
Did a factory reset, which did not solve it. Still no network operators found.
Click to expand...
Click to collapse
Have you tried restoring to the stock firmware? If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.

VitaTaf said:
Have you tried restoring to the stock firmware?
Click to expand...
Click to collapse
Yes, but that also did not help, so I returned to LineageOS again.
If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am not clear what that does. Seemingly, it erases two partitions. Is their content rebuilt after? Are those two partitions shipped with the custom rom? I did several google searches and each time I found it accompanied by the instruction to flash something else in the next step. So before nuking a partition I certainly would want to know., but so far I have not found an explanation of the partition layout.
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
Click to expand...
Click to collapse
I know. There it says it has no cellular network. As the logs I posted indicate, something goes badly wrong while searching for cells.

Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.

yahya69 said:
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
Click to expand...
Click to collapse
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related. Which method did you use to restore to the stock firmware?

VitaTaf said:
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related.
Click to expand...
Click to collapse
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
VitaTaf said:
Which method did you use to restore to the stock firmware?
Click to expand...
Click to collapse
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.

yahya69 said:
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
Click to expand...
Click to collapse
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.

VitaTaf said:
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
Click to expand...
Click to collapse
I reflashed them but as a result, the sim card is no longer recognized, rebooted several times.
Update: Reflashed lineageOS and now I got my sim card back, although still not connecting to the network. Reflashed the stock firmware with twrp (not sure how this would be done via fastboot), I got my phone to re-connect to the network for a few seconds, which made me jump up and down in excitement, but then the connection dropped again, before I could even make a phonecall
Update 2 Tried a different sim card, but again, when I try to register automatically, this is what I see:
}
D/PHONE (15915): [ServiceState] setDataRegState=1
D/PHONE (15915): [ServiceState] setDataRadioTechnology=0
D/GsmSST (15915): [GsmSST] 0handlPollStateResultMessage: GsmSST setDataRegState=1 regState=0 dataRadioTechnology=0
D/PHONE (15915): [ServiceState] setVoiceRegState=1
E/PHONE (15915): [ServiceState] setState deprecated use setVoiceRegState()
D/GsmSST (15915): [GsmSST] 0handleSIB5LackIssue: no cell location change and config is 'on'
D/GsmSST (15915): [GsmSST] 0Poll ServiceState done: oldSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1 realOldType=Unknown realNewType=Unknown mNewReasonDataDenied=-1
D/PHONE (15915): [ServiceState] setNullState=1
Needless to say it fails.

Titanium Backup crashing on start

Hi
I am using Lineageos 15.1 on my good old nexus 6. Working well but Titanium Backup is crashing on start .... I tried uninstall, then reinstall but nothing.
I tried one
Code:
adb logcat
in order to get some clue , here is one extract of the file :
08-04 18:38:37.718 2562 2574 I ActivityManager: Start proc 6602:com.keramidas.TitaniumBackup/u0a233 for activity com.keramidas.TitaniumBackup/.MainActivity
08-04 18:38:37.802 14937 5573 I DeviceStateChecker: DeviceStateChecker cancelled
08-04 18:38:37.802 14937 14937 I MicroDetector: Keeping mic open: false
08-04 18:38:37.811 14937 5898 I AudioController: internalShutdown
08-04 18:38:37.813 14937 6308 I MicroRecognitionRunner: Stopping hotword detection.
08-04 18:38:37.818 6602 6602 I o.კ : onCreate()
08-04 18:38:37.842 6602 6602 I o.კ : Detected CPU architecture: ARM
08-04 18:38:37.845 6602 6602 W Settings: Setting android_id has moved from android.provider.Settings.System to android.provider.Settings.Secure, returning read-only value.
08-04 18:38:37.851 6602 6602 D o.dJ : Debug features are disabled.
08-04 18:38:37.855 6602 6602 I o.dx : restoreMySettings_ifNeeded()
08-04 18:38:37.863 6602 6602 I o.dx : Internal settings found => No need to restore.
08-04 18:38:37.865 2235 6523 D audio_hw_primary: disable_audio_route: usecase(9) reset and update mixer path: audio-record
08-04 18:38:37.866 2235 6523 D audio_hw_primary: disable_snd_device: snd_device(75: voice-rec-mic)
08-04 18:38:37.879 14937 5898 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
08-04 18:38:37.879 14937 5417 I MicroRecognitionRunner: Detection finished
08-04 18:38:37.949 6602 6602 I com.keramidas.TitaniumBackup.MainActivity: Main Activity is being created for the first time => scheduling next wake-up ...
08-04 18:38:37.950 6602 6602 I o.dg : scheduleNextWakeup(): Invoked with idToExcludeForToday=null
08-04 18:38:37.974 6602 6602 I o.dg : scheduleNextWakeup(): No next wakeup scheduled.
08-04 18:38:37.975 6602 6621 I o.ỵ : Thread started.
08-04 18:38:37.989 6602 6602 I ToolbarWidgetWrapper: Progress display unsupported
08-04 18:38:38.024 6602 6623 D OpenGLRenderer: HWUI GL Pipeline
08-04 18:38:38.031 6602 6622 I o.ep : Detected 0 mount point(s) in addition to Android "external" storage.
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] No cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] Cache valid? = false
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] Deleting non-valid cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-04 18:38:38.035 6602 6622 I o.cj : [Licensing] Performing query: attempt 1/4
08-04 18:38:38.040 11256 11256 I com.keramidas.TitaniumBackupPro.LicenseQueryService: onCreate()
08-04 18:38:38.078 6602 6623 I Adreno : QUALCOMM build : a5b4970, If5818605d9
08-04 18:38:38.078 6602 6623 I Adreno : Build Date : 10/12/16
08-04 18:38:38.078 6602 6623 I Adreno : OpenGL ES Shader Compiler Version: XE031.09.00.04
08-04 18:38:38.078 6602 6623 I Adreno : Local Branch : N24D
08-04 18:38:38.078 6602 6623 I Adreno : Remote Branch :
08-04 18:38:38.078 6602 6623 I Adreno : Remote Branch :
08-04 18:38:38.078 6602 6623 I Adreno : Reconstruct Branch :
08-04 18:38:38.087 6602 6623 I zygote : android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
08-04 18:38:38.106 6602 6623 I OpenGLRenderer: Initialized EGL, version 1.4
08-04 18:38:38.106 6602 6623 D OpenGLRenderer: Swap behavior 1
08-04 18:38:38.138 2562 3863 W ActivityManager: Permission Denial: Accessing service ComponentInfo{com.android.vending/com.google.android.finsky.services.LicensingService} from pid=11256, uid=10143 requires com.android.vending.CHECK_LICENSE
08-04 18:38:38.140 6602 6624 E AndroidRuntime: FATAL EXCEPTION: Thread-4
08-04 18:38:38.140 6602 6624 E AndroidRuntime: Process: com.keramidas.TitaniumBackup, PID: 6602
08-04 18:38:38.140 6602 6624 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.vending.licensing.ILicensingService pkg=com.android.vending }
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2005)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1951)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at com.keramidas.TitaniumBackupPro.LicenseQueryServiceRemoteInterface$if$if.ˊ(Source:133)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at o.cl.run(Source:75)
08-04 18:38:38.148 2562 3275 W ActivityManager: Force finishing activity com.keramidas.TitaniumBackup/.MainActivity
08-04 18:38:38.165 6602 6624 I Process : Sending signal. PID: 6602 SIG: 9
08-04 18:38:38.201 2562 3290 I ActivityManager: Process com.keramidas.TitaniumBackup (pid 6602) has died: vis +99TOP
Click to expand...
Click to collapse
It seems to be a permission issue but any help will be welcome ... How to solve ?
Thanks
mahashakti89

I think this has to do with the play store. Have you tried clearing cache and data for the play store then reinstalling TiBu?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
I think this has to do with the play store. Have you tried clearing cache and data for the play store then reinstalling TiBu?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
Yes, I already tried clearing cache, uninstall, reinstall but it won't work.
Thanks

I want to double check, you cleared the play store app's data and cache. I'm not talking about TiBu cache/data.
If that's what you meant, then I would do a nandroid and clean flash the ROM again (wiping system, data, dalvik and cache - NOT user data). Use a small Gapps package like nano, then install just TiBu after setup and see if the problem persists.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
I want to double check, you cleared the play store app's data and cache. I'm not talking about TiBu cache/data.
If that's what you meant, then I would do a nandroid and clean flash the ROM again (wiping system, data, dalvik and cache - NOT user data). Use a small Gapps package like nano, then install just TiBu after setup and see if the problem persists.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
I did a clean install this morning. Wiped system , cache, dalvik but I did'nt format data. I used TWRP. How do you format data and NOT user data ?
What do you mean by clearing play store app's data and cache ?
Thanks

No need to format data. That is usually only done in internal storage (user data) to permanently dycrypt the device.
Wiping data (the partition mounted at /data), is done as a part of a factory reset, or the default wipe in TWRP. Wiping system requires going into the advanced menu in the TWRP wipe screen, and selecting it. Data, cache and dalvik are selected there as well. Internal storage (user data) can also be wiped from that screen, but typically you don't want to do that as all personal files get deleted.
To clear the play store data and cache, you go to settings -> apps -> google play store -> storage
If your problem with TiBu began as part of a clean install, it may be due to a bad flash, wrong gapps, bad download (always use checksums like MD5) or a hiccup during setup.
In this case then, I would remove TiBu, clear the play store data and cache then reinstall TiBu if it doesn't improve, them double check the quality of the downloaded files you installed, make site you've got the correct gapps and wipe, then flash again.
Sent from my Nexus 6 using XDA-Developers Legacy app

ktmom said:
No need to format data. That is usually only done in internal storage (user data) to permanently dycrypt the device.
Wiping data (the partition mounted at /data), is done as a part of a factory reset, or the default wipe in TWRP. Wiping system requires going into the advanced menu in the TWRP wipe screen, and selecting it. Data, cache and dalvik are selected there as well. Internal storage (user data) can also be wiped from that screen, but typically you don't want to do that as all personal files get deleted.
That's exactly what I did. Formatted all partitions except /data and Internal storage.
To clear the play store data and cache, you go to settings -> apps -> google play store -> storage
Already done. I asked because I was not sure if I mean the same as you mean
I will perhaps a full wipe tomorrow or wit till a new version of LineageOS.
Regards
Click to expand...
Click to collapse

I hope you mean "wipe" when you're saying format [emoji6]. A format is a different process.
The fact that you did not wipe data is in all probability, the cause of your problem.
Sent from my Nexus 6 using XDA-Developers Legacy app

ktmom said:
I hope you mean "wipe" when you're saying format [emoji6]. A format is a different process.
The fact that you did not wipe data is in all probability, the cause of your problem.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, I mean wipe when I say format .... I wait till Wednesday, new LineageOS version, if it doesn't work I shall wipe data .
Thanks

mahashakti89 said:
Yes, I mean wipe when I say format .... I wait till Wednesday, new LineageOS version, if it doesn't work I shall wipe data .
Thanks
Click to expand...
Click to collapse
I did'nt wait .... Wiped data. It works now ....
Thanks for helping

Hitting the "thanks" button on posts is always appreciated.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

[Guide] Moto G5s(xt179x) stock rom on Qingyou(xt1799-2)

DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO:
1) Download Montana_Retcn(i updated to original zui) and Montana last firmware in
Lolinet
2) Install adb and fastboot
3) Unlock Bootloader, on my Qingyou i just put it in fastboot mode(vol down + power) then connect to PC, open terminal and
Code:
fastboot flashing unlock
4) Extract Montana_retcn firmware and extract RSD-Lite-Mac-Linux and put the files on the firmware folder
5) Flash Montana_Retcn using
Code:
./rsd-flash.sh flashfile.xml
6) Boot your phone and reboot to fastboot again
7) Extract Montana firmware and open terminal
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
8) Boot again and put this on the fastboot mode again
9) Flash Twrp recovery
Code:
fastboot flash recovery twrp.img
10) Flash RemoveWarningLogo
Code:
fastboot flash logo removewarninglogo.bin
11) Go to recovery and flash MONTANA_RETCN_DRIVERS.zip
12) Just Boot your phone and everything is now working
Special Thanks for @Kamin4ri
Sorry for the bad english and for the bad guide , I hope it helps...

wow... thanks a lot
can somebody to make video guid?

jvfigueredo said:
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO:
1) Download Montana_Retcn(i updated to original zui) and Montana last firmware in
Lolinet
2) Install adb and fastboot
3) Unlock Bootloader, on my Qingyou i just put it in fastboot mode(vol down + power) then connect to PC, open terminal and
Code:
fastboot flashing unlock
4) Extract Montana_retcn firmware and extract RSD-Lite-Mac-Linux and put the files on the firmware folder
5) Flash Montana_Retcn using
Code:
./rsd-flash.sh flashfile.xml
6) Boot your phone and reboot to fastboot again
7) Extract Montana firmware and open terminal
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
8) Boot again and put this on the fastboot mode again
9) Flash Twrp recovery
Code:
fastboot flash recovery twrp.img
10) Flash RemoveWarningLogo
Code:
fastboot flash logo removewarninglogo.bin
11) Go to recovery and flash MONTANA_RETCN_DRIVERS.zip
12) Just Boot your phone and everything is now working
Special Thanks for @Kamin4ri
Sorry for the bad english and for the bad guide , I hope it helps...
Click to expand...
Click to collapse
what version of bootloader do you have now?

jahhh1 said:
what version of bootloader do you have now?
Click to expand...
Click to collapse
The last of Montana_retcn its 6(i hope), dont flash bootloader of Montana its can brick your device.

jvfigueredo said:
The last of Montana_retcn its 6(i hope), dont flash bootloader of Montana its can brick your device.
Click to expand...
Click to collapse
so, now you have BC06 after all?
how a new firmware recognize RAM (3 or 4 Gb) and camera (5 or 16 Mp)?
can you make some screenshots with system information?
maybe did you detect some bugs?

jahhh1 said:
so, now you have BC06 after all?
how a new firmware recognize RAM (3 or 4 Gb) and camera (5 or 16 Mp)?
can you make some screenshots with system information?
maybe did you detect some bugs?
Click to expand...
Click to collapse
Yes BC06, the ram recognize 4gb but the câmera 2mp, not detect bugs except the mp of câmera... Before i will search a solution for the little bug

jvfigueredo said:
Yes BC06, the ram recognize 4gb but the câmera 2mp, not detect bugs except the mp of câmera... Before i will search a solution for the little bug
Click to expand...
Click to collapse
make a photo by front camera and chek properties of picture
maybe it is just bug of recognizing , and photos have 16 mp resolution
even if that bug is present it is big problem at all

Moto g5s xt1799-2 "HardBrick"
jvfigueredo said:
The last of Montana_retcn its 6(i hope), dont flash bootloader of Montana its can brick your device.
Click to expand...
Click to collapse
friend, I have an equal, XT1799-2 came with the rom of the zui, when updating he did not call him "Hardbrick", you could help me return him even if it is for rom da zui.

ggjandson said:
friend, I have an equal, XT1799-2 came with the rom of the zui, when updating he did not call him "Hardbrick", you could help me return him even if it is for rom da zui.
Click to expand...
Click to collapse
You don't enter on fastboot? Only a led light and turn off?

jahhh1 said:
make a photo by front camera and chek properties of picture
maybe it is just bug of recognizing , and photos have 16 mp resolution
even if that bug is present it is big problem at all
Click to expand...
Click to collapse
Nop, its 3.0mp...
I do not know how to fix this, I need some advice on how I can fix this.

Moto g5s xt1799-2 "HardBrick"
jvfigueredo said:
You don't enter on fastboot? Only a led light and turn off?
Click to expand...
Click to collapse
I can not enter fastboot "Botao" - "+ power", just led flashing when I connect to the usb cable, the computer recognizes as cualcomm qdloader 9008.

ggjandson said:
I can not enter fastboot "Botao" - "+ power", just led flashing when I connect to the usb cable, the computer recognizes as cualcomm qdloader 9008.
Click to expand...
Click to collapse
You can test this
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150

Moto g5s xt1799-2 "HardBrick"
jvfigueredo said:
You can test this
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150
Click to expand...
Click to collapse
mine is xt1799-2 4gb of ram and 16mp of rear and front camera, do you think it will not have problem with this rom xt1794?

ggjandson said:
mine is xt1799-2 4gb of ram and 16mp of rear and front camera, do you think it will not have problem with this rom xt1794?
Click to expand...
Click to collapse
You just use the blank file on the sdcard to make your device boot and put It on fastboot mode and flash the last montanaretcn ROM, i don't have a sdcard of 32gb tô make this filé for you, just try of 1794 It can work, the gpt of its the same i hope

Thanks for the Guide, everything Works Fine, except the wi-fi, anyway to fix It? I have a 4gb ram 32gb storage version oficial 1799-2.

Moto g5s xt1799-2 "HardBrick"
rodrigober said:
Thanks for the Guide, everything Works Fine, except the wi-fi, anyway to fix It? I have a 4gb ram 32gb storage version oficial 1799-2.
Click to expand...
Click to collapse
yours too happened hardbrick? I still can not solve it, could you help me?

rodrigober said:
Thanks for the Guide, everything Works Fine, except the wi-fi, anyway to fix It? I have a 4gb ram 32gb storage version oficial 1799-2.
Click to expand...
Click to collapse
Yes, sorry for it, i will research some files and make it works, i make this work on mine but don't remember what files i flash

jvfigueredo said:
Yes, sorry for it, i will research some files and make it works, i make this work on mine but don't remember what files i flash
Click to expand...
Click to collapse
Ok, thank you Very much!

rodrigober said:
Ok, thank you Very much!
Click to expand...
Click to collapse
I updated the MONTANA_RETCN_DRIVERS.zip file.
Could you please reinstall the rom stock of the montana and flash this via TWRP Recovery and tell me if your wifi works?
I'm trying to make the front camera recognize the 16mp but it's only recognizing 4mp, if I change a /lib/hw/camera.msm8937.so by the motanaretcn the camera does not open, I think the problem is exactly that file, but I can not make it work by using this file simply from forced closing.
Could someone help me or advise me?
Logcat
Code:
--------- beginning of crash
09-11 19:44:00.954 4943 4943 E AndroidRuntime: FATAL EXCEPTION: main
09-11 19:44:00.954 4943 4943 E AndroidRuntime: Process: com.motorola.cameraone, PID: 4943
09-11 19:44:00.954 4943 4943 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.motorola.camera.CameraApp: java.lang.ArrayIndexOutOfBoundsException: length=0; index=-1
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5447)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.-wrap2(ActivityThread.java)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1558)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6165)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:778)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=-1
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.CameraApp.getCameraInfo(CameraApp.java:194)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.settings.ShutterToneSetting.isCameraSoundForced(ShutterToneSetting.java:63)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.settings.ShutterToneSetting.<init>(ShutterToneSetting.java:23)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.settings.AppSettings.<init>(AppSettings.java:39)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.CameraApp.onCreate(CameraApp.java:83)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1046)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5444)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: ... 8 more

ggjandson said:
yours too happened hardbrick? I still can not solve it, could you help me?
Click to expand...
Click to collapse
I dont had no problem with hardbrick.
jvfigueredo said:
I updated the MONTANA_RETCN_DRIVERS.zip file.
Could you please reinstall the rom stock of the montana and flash this via TWRP Recovery and tell me if your wifi works?
I'm trying to make the front camera recognize the 16mp but it's only recognizing 4mp, if I change a /lib/hw/camera.msm8937.so by the motanaretcn the camera does not open, I think the problem is exactly that file, but I can not make it work by using this file simply from forced closing.
Could someone help me or advise me?
Logcat
Code:
--------- beginning of crash
09-11 19:44:00.954 4943 4943 E AndroidRuntime: FATAL EXCEPTION: main
09-11 19:44:00.954 4943 4943 E AndroidRuntime: Process: com.motorola.cameraone, PID: 4943
09-11 19:44:00.954 4943 4943 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.motorola.camera.CameraApp: java.lang.ArrayIndexOutOfBoundsException: length=0; index=-1
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5447)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.-wrap2(ActivityThread.java)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1558)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6165)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:778)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=-1
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.CameraApp.getCameraInfo(CameraApp.java:194)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.settings.ShutterToneSetting.isCameraSoundForced(ShutterToneSetting.java:63)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.settings.ShutterToneSetting.<init>(ShutterToneSetting.java:23)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.settings.AppSettings.<init>(AppSettings.java:39)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at com.motorola.camera.CameraApp.onCreate(CameraApp.java:83)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1046)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5444)
09-11 19:44:00.954 4943 4943 E AndroidRuntime: ... 8 more
Click to expand...
Click to collapse
Okay, I'll try to do this later. The cell phone is not mine, it's my grandmother's, Thays why I had to change the rom, she was having difficulty with the zui.

Update problems

I also posted this in the general support thread but there are simply too many comments and nobody replied to mine.
Magisk Manager kept crashing on open, so I tried to update it but then it started complaining that it doesn't support the actual Magisk version in use (which is quite odd). When I tried to update that, everything broke:
ALL settings and modules are lost
The /system partition seems to have vanished: mount: can't find /system in /proc/mounts
Link2SD can no longer mount my second partition usd for app storage, I can mount it just fine manually but that doesn't help if it's expected to be there at boot time
These are pretty major issues. I had to restore a backup from both the boot and system partitions to get a working Android again.
Also, the Manager has a lot of trouble starting up. It will be stuck on the splash screen and I have to close it and reopen it twice/thrice before I actually get to the app. And then I have to get lucky and not have the Manager crash on me.
A logcat from around the crash:
Code:
10-01 22:24:28.512 6877 6948 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #4
10-01 22:24:28.512 6877 6948 E AndroidRuntime: Process: com.Ni.i.X.CSKtdIpsA, PID: 6877
10-01 22:24:28.512 6877 6948 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.String.indexOf(int)' on a null object reference
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at a.ql.a(Unknown Source:78)
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at a.ql.b(Unknown Source:19)
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at a.ql.lambda$l2fFZC2Jq4qpiuFgxpU9uWDPuvs(Unknown Source:0)
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at a.-$$Lambda$ql$l2fFZC2Jq4qpiuFgxpU9uWDPuvs.run(Unknown Source:4)
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
10-01 22:24:28.512 6877 6948 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
10-01 22:24:28.517 2219 2747 W ActivityManager: Force finishing activity com.Ni.i.X.CSKtdIpsA/a.b

WiFi not working after installing LineageOS for microG

Hi there! I'm trying to flash LineageOS-microG version (https://lineage.microg.org), but after successful (?) installation WiFi isn't working, I'm getting an error "Failed or timed out awaiting driver ready":
Code:
09-25 19:15:36.920 894 894 E WifiHAL : Timed out wating on Driver ready ...
09-25 19:15:36.921 894 894 E [email protected]: Failed or timed out awaiting driver ready
09-25 19:15:36.921 894 894 E [email protected]: Failed to start legacy HAL: TIMED_OUT
09-25 19:15:36.929 1307 3910 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 (, timed out)
09-25 19:15:36.929 1307 3910 E WifiVendorHal: Failed to create STA iface
09-25 19:15:36.929 1307 3910 E WifiNative: Failed to create iface in vendor HAL
09-25 19:15:36.930 1307 3910 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
I've downloaded latest "-microG-bramble-recovery.img" and "-microG-bramble.zip" form https://download.lineage.microg.org/bramble/, flashed recovery, rebooted into it and flashed zip as described in official LineageOS wiki https://wiki.lineageos.org/devices/bramble/install#installing-lineageos-from-recovery.
After rebooting and post-install setup WiFi is not working :/
Official LineageOS images works fine. So, what I'm doing wrong?
I've also unpacked "payload.bin" from this image https://download.lineage.microg.org/bramble/lineage-18.1-20210914-microG-bramble.zip with some python script https://github.com/cyxx/extract_android_ota_payload and there are some noticeable differences in official and microG LineageOS editions:
LineageOS-microG payload.bin:
Code:
4,0K ./vbmeta_system.img
8,0K ./vbmeta.img
16M ./dtbo.img
96M ./boot.img
96M ./vendor_boot.img
280M ./system_ext.img
553M ./product.img
710M ./vendor.img
1,1G ./system.img
2,8G .
Official LineageOS payload.bin:
Code:
4,0K ./vbmeta_system.img
8,0K ./vbmeta.img
44K ./devcfg.img
56K ./qupfw.img
80K ./xbl_config.img
88K ./featenabler.img
124K ./uefisecapp.img
192K ./aop.img
236K ./keymaster.img
404K ./hyp.img
1,0M ./abl.img
2,9M ./tz.img
3,5M ./xbl.img
16M ./dtbo.img
96M ./boot.img
96M ./vendor_boot.img
147M ./modem.img
280M ./system_ext.img
710M ./vendor.img
948M ./product.img
2,6G ./system.img
4,9G .
Does this mean that LineageOS-microG images are broken in some way or something?
Thanks!

I had the same issues with newer versions for Pixel 5, only initial 18.1 works fine. LineageOS for microG have huge issues with connectivity for redfin, they even don't have reachable support anywhere...
Update: I just managed to install a version of Lineage-18.1-20211021-microg-redfin-recovery.img (newest) with a fully operating MicroG and a working flawlessly WiFi/cellular connectivity - I used CalyxOS installer (to update Pixel 5 firmware during the installation), then I unlocked the bootloader (in CalyxOS dev. options and later in fastboot by typing "fastboot flashing unlock" through adb), and get rid of Calyx by making a wipe and install LineageOS recovery and LineageOS for microG image.
CalyxOS has installation module for Pixel 4, so I hope it could be helpful for you.

I have the same problem. The last build of Los4microG that works is the from May 21. Would a simple firmware update do the trick as well?