I have been getting terrible radio drops on baseband 03.84. I am on Oreo with the latest November security patch. I downloaded several older radio img files to try. I also found an app called FlashFire. Is anyone familiar with it. I wanted to know if I can flash the radio img files using it without problems. Thanks.
Don't do it with flashfire !!!!!!!! I did flash the bootloader two days ago with flashfire and had a hardbrick. ( Like a lot of other people trying to flash bootloader and radio with flashfire )Yesterday I spent a lot of hours of reading and with big luck i got my phone unbricked, but that's not always the case.
Don't be lazy like me, flash bootloader and radio only with fastboot to be safe. For the rest flashfire is a good app.
cigator said:
I have been getting terrible radio drops on baseband 03.84. I am on Oreo with the latest November security patch. I downloaded several older radio img files to try. I also found an app called FlashFire. Is anyone familiar with it. I wanted to know if I can flash the radio img files using it without problems. Thanks.
Click to expand...
Click to collapse
No. FF is a great app for updating your phone(s) every month, retaining root and custom recovery. That said, it is not intended for flashing protected partitions (like bootloader and modem) and Chainfire explicitly points this out in the documentation. A different radio is unlikely to help you. You may want to lay out what carrier you are on, your geographic location and what you have tried already such as swapping SIMs from a different carrier, and signal data you get from a app like LTE Discovery.
v12xke said:
No. FF is a great app for updating your phone(s) every month, retaining root and custom recovery. That said, it is not intended for flashing protected partitions (like bootloader and modem) and Chainfire explicitly points this out in the documentation. A different radio is unlikely to help you. You may want to lay out what carrier you are on, your geographic location and what you have tried already such as swapping SIMs from a different carrier, and signal data you get from a app like LTE Discovery.
Click to expand...
Click to collapse
Thanks to both posters for stopping me from using Flashfire to flash radio. I appreciate your questions, if you can offer any help that would be great. I'm on Verizon, in the Orlando Fl area. I have tried new sims, the one I have now was a replacement from about 2 months ago. I looked at LTE Discovery, sitting in my living room I'm at -114 dBm. What other data is useful for me to look at. The issue I have is many times I go to 0 bars of signal and calls drop or I can't connect to call. Looking for any solutions to this. I like my 6p, had it for 1.5 years, I would like to keep it longer but not if it keeps performing like this on phone calls.
cigator said:
Thanks to both posters for stopping me from using Flashfire to flash radio. I appreciate your questions, if you can offer any help that would be great. I'm on Verizon, in the Orlando Fl area. I have tried new sims, the one I have now was a replacement from about 2 months ago. I looked at LTE Discovery, sitting in my living room I'm at -114 dBm. What other data is useful for me to look at. The issue I have is many times I go to 0 bars of signal and calls drop or I can't connect to call. Looking for any solutions to this. I like my 6p, had it for 1.5 years, I would like to keep it longer but not if it keeps performing like this on phone calls.
Click to expand...
Click to collapse
I'm not us citizen and not using Verizon, but may the radio of this factory image gives you a good connection, just an idea.
7.1.1 (NUF26N, Mar 2017, Verizon Only)
cigator said:
Thanks to both posters for stopping me from using Flashfire to flash radio. I appreciate your questions, if you can offer any help that would be great. I'm on Verizon, in the Orlando Fl area. I have tried new sims, the one I have now was a replacement from about 2 months ago. I looked at LTE Discovery, sitting in my living room I'm at -114 dBm. What other data is useful for me to look at. The issue I have is many times I go to 0 bars of signal and calls drop or I can't connect to call. Looking for any solutions to this. I like my 6p, had it for 1.5 years, I would like to keep it longer but not if it keeps performing like this on phone calls.
Click to expand...
Click to collapse
Very few on Verizon complain about signal strength. They do rightfully complain about the many other things the Red Devil does, but signal strength is usually not one of them. I've found LTE Discovery to be useful in knowing what band I am on, what tower I am connected with, best signal strength location within my home/office/pub, what bands work best and when I get stuck with ****ty signal.... I can reset the network and it locks to a different band. This happened at my local pub all the time until they got excellent wi-fi. The phone would not give up (release) a poor connection and search for a stronger one. You can play around with Open Signal as well. They have a signal strength coverage map that is real-time crowd sourced rather than carrier propoganda. Once you have collected your data trends, you could then also try a different carrier for a day or two. Those Verizon specific images/radios simply contain additional support for Verizon specific add-ons like VVM and HD calling, etc. They won't make your signal better.
v12xke said:
No. FF is a great app for updating your phone(s) every month, retaining root and custom recovery. That said, it is not intended for flashing protected partitions (like bootloader and modem) and Chainfire explicitly points this out in the documentation. A different radio is unlikely to help you. You may want to lay out what carrier you are on, your geographic location and what you have tried already such as swapping SIMs from a different carrier, and signal data you get from a app like LTE Discovery.
Click to expand...
Click to collapse
v12xke said:
Very few on Verizon complain about signal strength. They do rightfully complain about the many other things the Red Devil does, but signal strength is usually not one of them. I've found LTE Discovery to be useful in knowing what band I am on, what tower I am connected with, best signal strength location within my home/office/pub, what bands work best and when I get stuck with ****ty signal.... I can reset the network and it locks to a different band. This happened at my local pub all the time until they got excellent wi-fi. The phone would not give up (release) a poor connection and search for a stronger one. You can play around with Open Signal as well. They have a signal strength coverage map that is real-time crowd sourced rather than carrier propoganda. Once you have collected your data trends, you could then also try a different carrier for a day or two. Those Verizon specific images/radios simply contain additional support for Verizon specific add-ons like VVM and HD calling, etc. They won't make your signal better.
Click to expand...
Click to collapse
Thanks, I flashed an older radio and don't see any improvement. When I use LTE discovery and cycle the radio on and off it changes the band and my signal seems stronger, but then it reverts to the weaker band. Is there some way to lock it to the stronger band?
cigator said:
Thanks, I flashed an older radio and don't see any improvement. When I use LTE discovery and cycle the radio on and off it changes the band and my signal seems stronger, but then it reverts to the weaker band. Is there some way to lock it to the stronger band?
Click to expand...
Click to collapse
I've read of a root hack but can't remember where exactly. I think it was in one of the Indian threads. I'll look around. I still believe this is probably down to the carrier vs. hardware.
What does radio image normally include ? Does it have a solution for my WiFi problem? I have been asking this on several forums but unfortunately I get no reply, my N6P is no more detecting WiFi signals. I literally get only loading screen on my WiFi panel and end up loading at the end only. I flashed stock images as referred by one of my friend but unfortunately nothing happend N6P without a WiFi is boring guys please help.
I don't get Bluetooth signals also
There is also no IP address seen and it is showing unavailable and MAC address in 20:00:00:00 from long time
Some screenshots below
zeeshanalpha said:
What does radio image normally include ? Does it have a solution for my WiFi problem? I have been asking this on several forums but unfortunately I get no reply, my N6P is no more detecting WiFi signals. I literally get only loading screen on my WiFi panel and end up loading at the end only. I flashed stock images as referred by one of my friend but unfortunately nothing happend N6P without a WiFi is boring guys please help.
I don't get Bluetooth signals also
There is also no IP address seen and it is showing unavailable and MAC address in 20:00:00:00 from long time
Some screenshots below
Click to expand...
Click to collapse
Which stock image did you flash?
Sent from my Nexus 6P using XDA Labs
mdfarazb2 said:
Which stock image did you flash?
Click to expand...
Click to collapse
NJH47F 7.1.2 Nougat Stock Firmware
zeeshanalpha said:
NJH47F 7.1.2 Nougat Stock Firmware
Click to expand...
Click to collapse
Try the latest 8.1
Sent from my Nexus 6P using XDA Labs
zeeshanalpha said:
What does radio image normally include ? Does it have a solution for my WiFi problem? I have been asking this on several forums but unfortunately I get no reply, my N6P is no more detecting WiFi signals. I literally get only loading screen on my WiFi panel and end up loading at the end only. I flashed stock images as referred by one of my friend but unfortunately nothing happend N6P without a WiFi is boring guys please help.
I don't get Bluetooth signals also
There is also no IP address seen and it is showing unavailable and MAC address in 20:00:00:00 from long time
Some screenshots below
Click to expand...
Click to collapse
Do you have any efs partition backup with TWRP, if yes, try to restore it with TWRP.
Edit: for some guys it help to remove simcard and reboot the phone without, don't ask me why.
Edit: and some solutions from a n6 thread with the same issue, if the issue still persist
https://forum.xda-developers.com/nexus-6/help/wifi-mac-address-200000000000-t3257465
zeeshanalpha said:
NJH47F 7.1.2 Nougat Stock Firmware
Click to expand...
Click to collapse
Could you explain why you flashed a Pixel XL factory image or radio onto your Nexus 6P?
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Didn't even see that, guess there's no explanation
SlimSnoopOS said:
Could you explain why you flashed a Pixel XL factory image or radio onto your Nexus 6P?
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Where ? No I didnt flash Pixel images why would I even do that to my N6P. It was the latest stock nougat firmware for N6P which I flashed !
I cycled through different ROMs thinking that it might solve the issue but nothing happend. I even tried flashing radio images but no sign of wifi. Not getting the exact problem
Tried through different forums
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
SlimSnoopOS said:
Could you explain why you flashed a Pixel XL factory image or radio onto your Nexus 6P?
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Its actually 7.1.2 N2G48C if I was wrong cuz I reverted back into RR and still no signs of Wifi.
---------- Post added at 05:20 AM ---------- Previous post was at 05:16 AM ----------
coremania said:
Do you have any efs partition backup with TWRP, if yes, try to restore it with TWRP.
Edit: for some guys it help to remove simcard and reboot the phone without, don't ask me why.
Edit: and some solutions from a n6 thread with the same issue, if the issue still persist
https://forum.xda-developers.com/nexus-6/help/wifi-mac-address-200000000000-t3257465
Click to expand...
Click to collapse
My EFS backup is done after flashing the stock firmware. But even the stock OS isn't showing any signs of WiFi so I guess if I restore through its of no use I still won't get the WiFi bruh
zeeshanalpha said:
My EFS backup is done after flashing the stock firmware. But even the stock OS isn't showing any signs of WiFi so I guess if I restore through its of no use I still won't get the WiFi bruh
Click to expand...
Click to collapse
Maybe I'm not understanding you correctly, but the modemst1 and modemst2 partitions are not part of any Google image, they are protected and unique to your phone. You may or may not have backed them up previously with TWRP. If you did back them up, you can restore just those two partitions. If you did not back them up previously, you can try deleting them and letting them rebuild as in this article.
v12xke said:
Maybe I'm not understanding you correctly, but the modemst1 and modemst2 partitions are not part of any Google image, they are protected and unique to your phone. You may or may not have backed them up previously with TWRP. If you did back them up, you can restore just those two partitions. If you did not back them up previously, you can try deleting them and letting them rebuild as in this article.
Click to expand...
Click to collapse
Didn't work bro
But unique method though. I literally had high hopes on this technique of restoring efs files I.e modemst1 and 2
Still facing the same WiFi loading issue and disabled on the main screen. I really dont wanna give up on my N6P its a lucky one for me
I hope I get the solution early for this
Thanks btw
zeeshanalpha said:
Didn't work bro
But unique method though. I literally had high hopes on this technique of restoring efs files I.e modemst1 and 2
Still facing the same WiFi loading issue and disabled on the main screen. I really dont wanna give up on my N6P its a lucky one for me
I hope I get the solution early for this Thanks btw
Click to expand...
Click to collapse
So you used the fastboot method and deleted the partitions, and it completed on reboot (re-wrote) the partitions... what confirmation did you get it was successful?
At this point, and in order to rule out hardware, you should fastboot format system, userdata and cache. Use the latest 8.0 full image with the included flash-all.bat script. Until you do this (including formatting the partitions) you cannot rule out the motherboard. If this does not fix it, the problem is hardware related and not worth repairing on a used 6P.
v12xke said:
So you used the fastboot method and deleted the partitions, and it completed on reboot (re-wrote) the partitions... what confirmation did you get it was successful?
At this point, and in order to rule out hardware, you should fastboot format system, userdata and cache. Use the latest 8.0 full image with the included flash-all.bat script. Until you do this (including formatting the partitions) you cannot rule out the motherboard. If this does not fix it, the problem is hardware related and not worth repairing on a used 6P.
Click to expand...
Click to collapse
Is 8.0 full image stable ? I guess its still in developer preview right ? Get me the download link if possible.
Thanks
Related
Hi
Last june I finally got my new Redmi 2 Pro (HM2014819, ergo the Brazilian version) and as soon as it arrived, I decided to reflash it into the latest available Nexus Experience custom ROM. Before that, though, I managed to check that my phone did had access even to LTE networks.
Turns out the GPS got weird because I supposedly didn't attempt to fix it before in the original ROM. I tried the the modemst1/2 format trick and it also didn't work. So I flashed MIUI7 over it again in an attempt to get a fix in the original ROM.
When I got back to MIUI, all celular/signal data was gone, along with my IMEI number (probably from the modemst partition wipe). I had to struggle a lot and I finally was able to recover it using this tutorial. However, as I just noticed recently playing Pokemon Go, 4G networks never came back even though I'm up and running on both H and H+ networks.
Using QPST and QXDM, I delve further into the QCN file and I could notice that the LTE values were actually set for Redmi2 PRIME version, which are Asia-related basebands 3 and 40 (meaning the actual LTE value in binary had 1's in the 3th and 40th bytes). However, the Redmi2 PRO version supports South America-related LTE bands 2, 4 and 7, as GSMArena points out.
Using this information and following this guide, I also tried to change/write over new Decimal values that would match my required LTE bands, but to no avail. When manually selecting networks, only 3G networks show up, even though I'm sure I could see and even pick 4G networks manually when I first booted up my (at that time, unmodified) new Redmi2.
What did just happen? What CAN I do?! How can I recover the intended, factory original version of the brazilian Redmi 2 networks?! Is there something to do with modemst2 erasure, or IMEI loss, or even NON-HLOS.bin file? Aren't they all overwritten when you reflash MIUI through MiFlash anyway?
Please, PLEASE, help me! I'm already on the brink of purchasing another cellphone (and it won't be another Xiaomi, that's for sure) if I can't get this to work. I did purchase this sorely because of the 4G connection and now I lost it entirely. Come on! :crying:
damn.... i've done this mess of erasing modemst's too and got the same problem. VERY LUCKY of me, i had a twrp backup that i did some days before doing this. hope you find some solution to this and dont give up on xiaomi just for a mess that you did xD
igorinolw said:
damn.... i've done this mess of erasing modemst's too and got the same problem. VERY LUCKY of me, i had a twrp backup that i did some days before doing this. hope you find some solution to this and dont give up on xiaomi just for a mess that you did xD
Click to expand...
Click to collapse
Igor, do you think you could at least share your modemst partition and/or your QCN file? I could use this to find the differences between my modem configurations and set it exactly as the brazilian's factory default modem.
If you're worried about IMEI scamming, then a simple printscreen from certain screens on QPST/QXDM will suffice, since I can tell what's wrong from them. If you're willing to help me (and have a rooted device), please, do tell and I can walk you through how to get them. Thanks!
http://en.miui.com/thread-218200-1-1.html
Follow this tutorial.
My signal came back but I'm having frequent signal loss. The only solution is to turn on/off airplaine mode.
I've to send it to tecnical assistant but I don't want to stay without the phone.
Acttually I'm not sure if the 4g works, because my city only supports 3G. When the data connection is on I don't loss the signal.
LuizHPiccinini said:
Follow this tutorial.
Click to expand...
Click to collapse
That's the exact tutorial I've followed to recover my IMEI. And I even mentioned that in the OP, bud. My problem happened after that. Please read more carefully.
Sorry, I just saw the second link.
Drezus said:
Igor, do you think you could at least share your modemst partition and/or your QCN file? I could use this to find the differences between my modem configurations and set it exactly as the brazilian's factory default modem.
If you're worried about IMEI scamming, then a simple printscreen from certain screens on QPST/QXDM will suffice, since I can tell what's wrong from them. If you're willing to help me (and have a rooted device), please, do tell and I can walk you through how to get them. Thanks!
Click to expand...
Click to collapse
as soon i get to my pc with the programs, ill try to help you if nobody comes first :highfive:
igorinolw said:
as soon i get to my pc with the programs, ill try to help you if nobody comes first :highfive:
Click to expand...
Click to collapse
Thanks a lot!
Oh gosh guys, I hope you can help me too! I've got the exact same problem with my HM2014819!
Did you manage to fix that?
Hi the exact same thing happened to me, I had no mobile internet at all and I fixed that qcn stuff but all I could find was asian versions, I get no 4G network and I have no other brazilian file to compare. If you managed to fix that, please please share, thanks a lot.
Okay, who has followed my posts know my new Nexus 6P, which I bought from a guy wasn't recognizing my SIM card. (I'm apparently the second owner. He said that he imported the device so I assume that he was really the first owner)
Luckily I made it recognize the SIM card putting a tape on it at the SIM tray, but now my device keeps at No Service | Vivo.
Vivo is my carrier, but no matter what I do my Network Type at *#*#4636#*#* keeps at LTE/*I don't remember/CDMA. I've tried changing it in Settings/more/cellular network but didn't work either. Removing and putting SIM tray again didn't work as well.
Flashed factory image didn't work too. Also, flashing custom ROM didn't work.
Someone have a solution for it, please?
Since I fixed the unrecognized SIM with a simple tape I can believe something will fix this No Service trouble.
Had the same issue at my wifes old opo, the simpins inside the phone were broken. May yours are only bent if your lucky, hard to check without opening the backcover. Can you try another sim card first, friends, family or neighbors??? Or you need one tape more I had to replace the mobo. Took one of a broken phone cheap from the bay.
coremania said:
Had the same issue at my wifes old opo, the simpins inside the phone were broken. May yours are only bent if your lucky, hard to check without opening the backcover. Can you try another sim card first, friends, family or neighbors??? Or you need one tape more I had to replace the mobo. Took one of a broken phone cheap from the bay.
Click to expand...
Click to collapse
I'll try to tape it even more. I've checked over xda and a guy fixed it flashing February factory image. I'll try it as soon as I arrive home.
Debuffer said:
I'll try to tape it even more. I've checked over xda and a guy fixed it flashing February factory image. I'll try it as soon as I arrive home.
Click to expand...
Click to collapse
Hope you don't have to stay on it, good luck
Edit: is your simcardholder ok ?? May one site hangs and you don't have contact to the right pin.
Edit2: can you see the pins by using a bright flashlight ???
coremania said:
Hope you don't have to stay on it, good luck
Edit: is your simcardholder ok ?? May one site hangs and you don't have contact to the right pin.
Edit2: can you see the pins by using a bright flashlight ???
Click to expand...
Click to collapse
The device recognize the SIM, but it doesn't get network.
Debuffer said:
The device recognize the SIM, but it doesn't get network.
Click to expand...
Click to collapse
Yes, I get that, this was exactly my issue with the opo. Recognize but no service.
Your phone may be stuck on USA bands. The hidden menu apparently is buggy and once USA bands is selected by accident, you can't change it back. 7.1.2 was supposed to have added the ability to switch back to Auto, but I cannot confirm that. Look here. I know you are new, so to access the menu, youopen up the dialer and type this in- *#*#4636#*#*
I just noticed that I can switch to any (PRL) network in *#*#4636#*#*, but can't switch to LTE, GSM or WCDMA without the (PRL)...
v12xke said:
Your phone may be stuck on USA bands. The hidden menu apparently is buggy and once USA bands is selected by accident, you can't change it back. 7.1.2 was supposed to have added the ability to switch back to Auto, but I cannot confirm that. Look here. I know you are new, so to access the menu, youopen up the dialer and type this in- *#*#4636#*#*
Click to expand...
Click to collapse
I'm download it and very hopeful because it worked for many people... Anyway, this are the bands I've available for now:
United States
Cellular 800
PCS
Class 10 (800Mhz-Secondary)
Hopefully this PureNexus gonna fix this issue.
Debuffer said:
I'm download it and very hopeful because it worked for many people... Anyway, this are the bands I've available for now:
United States
Cellular 800
PCS
Class 10 (800Mhz-Secondary) Hopefully this PureNexus gonna fix this issue.
Click to expand...
Click to collapse
Sounds like you are stuck on USA bands. Good luck.
v12xke said:
Sounds like you are stuck on USA bands. Good luck.
Click to expand...
Click to collapse
My Nexus 6 (shamu), which works perfectly with the same Nano SIM, has all the Network Bands I quoted in my previous post + Class 15.
Not sure if my device should use Class 15, but I'm (was) using the same ROM on both (PureNexus Shamu and PureNexus Angler) and the angler doesn't work.
Download Chroma ROM to test it since the PureNexus quoted in the post you sent me is bootlooping in the Google Logo.
Just an EDIT...
I can select the Automatic bands selector, and it says that the Automatic was selected, which still doesn't give me any signal strenght.
Debuffer said:
Just an EDIT... I can select the Automatic bands selector, and it says that the Automatic was selected, which still doesn't give me any signal strenght.
Click to expand...
Click to collapse
In Chroma or PN? You may need to fastboot format your partitions, especially System coming from a custom ROM. Why not step back and fastboot format system, userdata and cache then reflash the custom PN ROM to try and get it booted. It also may take some time after changing bands to Auto. Maybe 5-10 minutes max. Let it settle.
v12xke said:
In Chroma or PN? You may need to fastboot format your partitions, especially System coming from a custom ROM. Why not step back and fastboot format system, userdata and cache then reflash the custom PN ROM to try and get it booted. It also may take some time after changing bands to Auto. Maybe 5-10 minutes max. Let it settle.
Click to expand...
Click to collapse
I'm now downloading a factory image for 6.0.1 then I'll flash PureNexus again. I read in the thread that it needs the 6.0.1 vendor to boot.
I'll flash this 6.0.1 stock then I'll flash PureNexus. Fingers crossed to this work.
Anyway, can we talk via Telegram? You look like know more than I and I would love to keep talking to you during this proccess.
I'm @Debuffer.
v12xke said:
In Chroma or PN? You may need to fastboot format your partitions, especially System coming from a custom ROM. Why not step back and fastboot format system, userdata and cache then reflash the custom PN ROM to try and get it booted. It also may take some time after changing bands to Auto. Maybe 5-10 minutes max. Let it settle.
Click to expand...
Click to collapse
And I meant I could select the Automatic Band in the latest 7.1.2 PN and/or stock rom.
Unhappily it didn't work.
Still No Service|Vivo
Just came from the tech and he tested the antenna. Everything is working great with the antenna. Anyway, I can't get any signal. He said maybe there's a problem in the SIM slot, and he showed me that the 6P is dual SIM
He told me to try finding a dual SIM tray and put my SIM in the slot 2.
Someone have any idea about what to do with it?
Hi all,
I picked up a used G5 Plus (XT1687) on eBay, with the bootloader already unlocked. I immediately installed AICP ROM with a VZW SIM from a working G4. The phone showed LTE for data, but no voice service. That started a long series of firmware changes that saw me trying Pixel Experience, and a few stock ROMs, having my IMEI show as 0 a few times as well.
I'm at a point with the phone now where I'm on the latest retus channel stock ROM (POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with the bootloader locked. The phone now connects with 1xRTT for voice and EvDo (3G) for data. If I swap this SIM into my other phone (Pixel XL) I get full LTE in the Pixel but still 3G only in the G5+.
The only other standout item is in the BP tools SIM menu, where I get the following errors.
Phone ICCID Compare with SIM ICCID: ERROR
and
PHONE ICCID: PHONE_ICCID_UNKNOWN
I feel like with all the flashes I may have really screwed things up. does anyone have any recommendations on what to try to get LTE service back?
TIA!
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
[email protected] said:
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
Click to expand...
Click to collapse
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
bra1niac said:
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It seems they would rather replace than fix.
Same with my phone. It has been unlocked and I've been on numerous variations of ROMs stock and custom. Everything was smooth with no issues until I decided to flash an Oreo 8.1 ROM. Immediately after I was greeted with 3G EVDO-Rev A./1xRTT mode with no access to 4G/LTE on Verizon. Sim Card status is screwy with some apps seeing it, albeit improperly configured, most not able to detect it at all. If I return to any ROM below 8.1 I have no data service whatsoever. Hoping a fix is found as all the workarounds do nothing.
Also like the OP, I can get LTE to stick sometimes by messing around with Radio Bands and switching options around in the 4636 menu. But that leaves me without voice/text/mms service.
[email protected] said:
It seems they would rather replace than fix.
Click to expand...
Click to collapse
sad but true
Sent from my Pixel XL using Tapatalk
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
[email protected] said:
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
Click to expand...
Click to collapse
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
bra1niac said:
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
Click to expand...
Click to collapse
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me
this zip will "erase" format the modem status partition:
mdm1m9kefs1 = modemst1
mdm1m9kefs2 = modemst2
Click to expand...
Click to collapse
Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
[email protected] said:
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
Click to expand...
Click to collapse
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Archangel said:
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Click to expand...
Click to collapse
yeah a factory Oreo ROM would probably help straighten a bunch of things out.
Sent from my Pixel XL using Tapatalk
bra1niac said:
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
Click to expand...
Click to collapse
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
A little research into the baseband processor and its radio firmware RTOS [real-time operating system,] shows it to be closed source, proprietary, yet full of flaws. It is even susceptible to the long standing "Hayes command set" but I don't believe this to be where our particular problem lies. Because it is so closed, it is doubtful the Oreo roms were able to inadvertently touch anything inside this secondary operating system all phones have. It is more likely it is the communication between our android firmware, and the radio firmware, but why the restoration back to stock, doesn't remedy it, is a mystery. The devs that adapted the Oreo roms to this device, missed this link or they would not have written to that area, I'm sure.
You guys are a lot smarter than me,,,it just scared the heck out of me. I flashed a 8.1 rom like I have done at least a dozen or so times on this phone and then suddenly no signal at all,,,then just 4g data and no voice service. I went back to a 8.1 back up that I have and within a few mins everything came back. Now, I am afraid to flash anything rom wise for fear of not getting any signal back.
Something like this really deserves an official statement by Lenovo, Motorola or Verizon. Even if that statement is an unfortunate "you knew the risks associated with unlocking the bootloader and flashing ROMs / modems". Even if none of the three know what exactly is going on they should at least let us know.
Is this problem something that happens with all carriers and their LTE signals? Am I right in thinking that using Verizon is currently the only carrier in which the issue can't be fully repaired?
I havent yet restored my partially working (3g/1x) EFS backup to a stock Nougat Rom yet as I want to have 4G working as well if I do that. If the other carriers can be fully repaired I'll just switch carriers until I get a new phone.
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
[email protected] said:
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
Click to expand...
Click to collapse
Yeah that all seems to make sense. Something we broke with a software change should be fixable with a software change. Hopefully the next OTA isn't too far away.
[email protected] said:
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
Click to expand...
Click to collapse
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
bra1niac said:
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
Click to expand...
Click to collapse
It might pay to remove your sim, flash the
Code:
fastboot erase modemst1 fastboot erase modemst2
and then insert her sim. I'm just thinking that would clear the modem for the new bands to set themselves.
Got a tough one. Ever since last Wednesday my SIM card hasn't been recognizing like it should be. It will randomly stop working and not work again untill I flash a new rom/backup/stock. I've tried clearing the cache... Nothing. When I go into *#*#4636#*#*, if I turn of radio power, it will recognize my phone number after about 10 seconds. Also, It says that APN settings are not available for this user under APN settings... Any help is appreciated, thanks.
Ol
olfred said:
jajajaja . You now . You have loose you imei the soluchion is root you divese an lukin the apk chamelephon.apk an thes apk repair you imei ok oleas dont flash a unoficial room . I am olfred velasco from mexixco
Click to expand...
Click to collapse
This only works with mediatek devices...
I have seen many posts about the sim card error, and have now experienced it myself. I have a USC XT1768 (on AT&T), running RR for about the last 4 months. Everything has worked perfectly until 3 nights ago when, suddenly, for no reason I had no service & saw there was "no sim" recognized. A Google search led me to switch to 3G and turn on airplane mode and reboot. After rebooting, I turned off airplane mode and service was restored. However, I am forced to use only 3G. After multiple "tests" switching back to 4G LTE, I always lose service. Yesterday, I "tested" again and LTE worked for about 8 hours before I got the sim card error. I re-did the airplane mode/3G process and I was back in business...just with 3G.
Last night when I got the "No Sim" error, I noticed that the preferred network in *#*#4636#*#* was "Unknown". It had been set to LTE/UMTS/Auto. It doesn't seem to make a difference if I switch it to Global, or anything else. The problem remains. Oddly, when I just entered *#*#4636#*#*, the preferred network setting was on WCDMA. Weird...I didn't select that setting.
Anyway, maybe this can kind of help someone else.
Tried the airplane mode/3g thing, still nothing for me. Just "lost" all recognition of a SIM. Nothing. No matter what I do, won't recognize. Lots online about it, loaded the latest F/W, etc., still nothing. The phone is like a new phone. Something feels hinkey about it though. Seems it's happening to unlocked Moto phones after about two-months.
TomJ2 said:
Tried the airplane mode/3g thing, still nothing for me. Just "lost" all recognition of a SIM. Nothing. No matter what I do, won't recognize. Lots online about it, loaded the latest F/W, etc., still nothing. The phone is like a new phone. Something feels hinkey about it though. Seems it's happening to unlocked Moto phones after about two-months.
Click to expand...
Click to collapse
I've had it for about a year when it happened, but what I did was send it to Moto and just told them it stopped working out of the blue. Flashed stock and sent it in. Within about 4 days they sent a new one. I would recommend that if you have a backup phone.
Did you have an unlocked bootloader (using the Moto code they send along with the warning that it'll void warranty)? If they still warrantied it, I'll do what you did, then sell the replacement ASAP. What an unreliable POS...
TomJ2 said:
What an unreliable POS...
Click to expand...
Click to collapse
Not really. Clearly a small percentage of E4s have a SIM problem; Moto should own up to it. However, that's unlikely as they never acknowledged the HW GPS issue on the G4P line that impacts a much larger proportion of devices.
codyalan said:
This only works with mediatek devices...
Click to expand...
Click to collapse
Just use QPST TOOL FROM QUALCOMM
https://www.androidbrick.com/ultima...agon-xiaomi-mi5-imei-and-baseband-repair-fix/
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
I think it's more related to custom modifications
TomJ2 said:
Did you have an unlocked bootloader (using the Moto code they send along with the warning that it'll void warranty)? If they still warrantied it, I'll do what you did, then sell the replacement ASAP. What an unreliable POS...
Click to expand...
Click to collapse
Yeah, it was unlocked but I don't know why they had still look it though..
If you erase modemst1 and 2, the SIM will be recognized again. At least, it was on my XT1768. I wrote a small TWRP flashable version, for when it happens when I'm out and about. Just boot to recovery and "install" it. It's attached to my reply.
Additionally, the following firmware build is supposed to have the fix for this issue: https://androidfilehost.com/?fid=746010030569967659
Addendum: AFAIK, all Moto E4's running a build less than NPQ26.69-64 have the SIM issue. From what I've seen, it happens when one doesn't have any signal for a few hours, then comes back into an area that has a signal.
zahna said:
If you erase modemst1 and 2, the SIM will be recognized again. At least, it was on my XT1768. I wrote a small TWRP flashable version, for when it happens when I'm out and about. Just boot to recovery and "install" it. It's attached to my reply.
Additionally, the following firmware build is supposed to have the fix for this issue
Addendum: AFAIK, all Moto E4's running a build less than NPQ26.69-64 have the SIM issue. From what I've seen, it happens when one doesn't have any signal for a few hours, then comes back into an area that has a signal.
Click to expand...
Click to collapse
can you please explain this step by step for a naive person. My Moto E4 amazon version has same problem. Hoping to fix it on my own
satyavidu123 said:
can you please explain this step by step for a naive person. My Moto E4 amazon version has same problem. Hoping to fix it on my own
Click to expand...
Click to collapse
Can you boot TWRP or another custom recovery? Need that to apply the 'fix' in the form presented. Not even sure it will work on a bootloader locked device.
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
zahna said:
Addendum: AFAIK, all Moto E4's running a build less than NPQ26.69-64 have the SIM issue. From what I've seen, it happens when one doesn't have any signal for a few hours, then comes back into an area that has a signal.
Click to expand...
Click to collapse
Must be other variables involved. Have a much older build and frequently travel to/through areas with no coverage. Have yet to experience a SIM issue.
satyavidu123 said:
can you please explain this step by step for a naive person. My Moto E4 amazon version has same problem. Hoping to fix it on my own
Click to expand...
Click to collapse
Your bootloader is locked, so you can't apply my fix from TWRP. You will need to hook up your phone to a computer, boot your phone to your bootloader (power + down), on your computer cd to your Android Sdk tools directory, then run "fastboot erase modemst1" and "fastboot erase modemst2", then reboot your phone.
However, you should be getting OTA updates. The most recent firmware should prevent the issue.
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Knuxyl said:
Somehow or another I have managed to screw up my modem on my SPerry XT1766 (Boost Mobile).
I only get Emergency Calls Only radio signal, Settings app and bootloader info shows Baseband Not Found or Unknown.
I tried using RSDLite to flash
XT1766_SPERRY_SPRINT_7.1.1_NCQS26.69-64-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
which contains the fsg.mbn and NON-HLOS.bin files, but this doesn't seem to help. I've tried multiple firmwares with multiple different modems and nothing seems to be getting my modem up and going. Back when I originally updated I flashed the partition updater also. I have no idea what to do now. I'm downloading the 69-56 version to try that, but I doubt it'll be any different. If anyone has any idea on what to do that would be great. Thanks
Click to expand...
Click to collapse
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Yeah I already tried that but it jept giving me an error saying unknown command [ ]] or somrthing along those lines. i looked through the script and didnt see any typis. i think your NON-HLOS.img is different format than the NON-HLOS.bin files found in the stock firmwares, plus it's much larger. Anyways, tried a fastboot flash the modem with it and that didnt work either.
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
madbat99 said:
@Knuxyl
Are you on Boost network? I've seen the radio off problem with ppl using a different sim.
Click to expand...
Click to collapse
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Also as an update, the 56 version didn't fix it either
Knuxyl said:
No I am not on a boost network but this problem goes more into firmware than network compatibility because the bootloadet itself isnt even recognizing the baseband. For the record I am still using a CDMA network like boost (Verizon)
Click to expand...
Click to collapse
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
madbat99 said:
The latest update did that too many people. It won't work with a different sim. The radio will be off.
I bet if you put in a boost SIM, it would pop right on.
They changed something in the -8 firmware.
One guy building ROMs (not here anymore) made some changes to his build that got certain networks to work on his ROM.
He never got the chance to share exactly what he was changing.
It seems that if you booted the phone ever with the original sim inserted, it tripped a qfuse (of sorts) and it seems they have added a way for that particular reading to turn off the radio completely if you're not using one of their SIMs.
Click to expand...
Click to collapse
You are 100% on point. Sprint (and its subsidiaries) had Motorola Mobility to include code in an OTA update which would disable functionality of any network other than the original UICC (SIM). In other words, when you got a new Sprint compatible xt1766 (Sprint, Boost or Virgin Mobile), opened the box and booted the device with the preinstalled SIM in it, the xt1766 became forever locked to that network -- the OTA update carved that in stone. The update made it impossible to downgrade the baseband radio, killed all GSM functionality, and broke the radio on custom ROMs (the latter being unintended most likely). The only people I have heard of getting around this are the ones that didn't take the -8 OTA update. Like you were saying, I'd like to know what Jason M. done in his custom ROM to fix radio function, whereas at least the radio would work with the original SIM on a custom ROM. He said something about "adding missing symlinks" to the build.
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
chmod 0700 /persist/rfs/msm/mpss/datablock/id_00
Click to expand...
Click to collapse
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
lugnut2099 said:
I did this too somehow. I think this might bring your baseband back (it did for me), but... well, I'll get to the "but..." Anyway, Boot to TWRP, mount the Persist partition, then go to terminal or pull up an ADB shell and do:
Reboot with a SIM card inserted and voila, you maybe might have a baseband again. Hooray! Except in my particular case, I regained a baseband and then somehow lost an IMEI. Well, not really "lost," it's still there when I pull up the barcodes page... but on bootup it thinks it's 000000000000001. I still haven't ever fixed it, though I did manage to turn it to a single 0 somewhere along the line. Fkit.
But I don't know of anyone else who's lost their IMEI this way, and it's been too long ago and I've tried way too many failed fixes to remember what else could have triggered the problem to start with, so who knows. If you decide to try it, definitely make a backup of the Persist partition before you do anything...and make sure your backup turns out to be good first, not corrupt like mine turned out to be....sigh.
Click to expand...
Click to collapse
Seriously, you unbricked my kids phone!
Requested permission to access your file twice
LenovoTech said:
Try my baseband updater from this thread. https://forum.xda-developers.com/mo.../rom-stock-android-7-1-1-rom-moto-e4-t3885821
It will attempt to update your baseband to the latest version (M8920_15000.280.06.58.06R) from firmware build NCQS26.68-64-11. If this doesn't work for you let me know, I may have a solution.
Click to expand...
Click to collapse
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
ELEKTRIKMESSIAH said:
Is your updater still available?
May I please download your file?
my email: [email protected]
thank you
Click to expand...
Click to collapse
You see that member's account disabled? So.... You're talking to no one
Reading is fundamental