I have a TMO version of Z2 force that I ran stock/rooted for a couple years without any problems. I decided to try Lineage and a couple other ROM's but I got tired of the problems, so I reflashed my phone back to stock using the latest FlashAll that I could find on these threads. So I am back to stock/rooted with no problems EXCEPT my radio sucks now. My home and local supermarket both barely have 1 signal bar if that, where I never had problems before. Phone/4G is very spotty in stores and I usually have to go near a window if I have to text....which I never had to do in the past.
Is it possible I just had a bad flash? Does anyone know which version of radio is the "best"? I currently have the following:
Baseband version M8998TMO_20207.117.02.41.08R NUS
Build OCXS27.1.7
Security patch July 1, 2019
Thx!
Can I ask, does your wifi still work okay?
I was (am) in your shoes here regards the details you gave in your question, exactly, the only difference being that my radio is non functional- it won't recognize SIM cards, even though it DOES read the iccid off of them, and my z2 force still has the baseband (identical to yours). I have flashed, and blankflashed every possible flashall to get my radio back- none worked, and everything prior to the 27.1.7 build lost my baseband entirely, so I ended up having to reflash 27.1.7.
My wifi still works good at least. My point here is that you may lose your radio entirely by reflashing other flashalls
ianmck said:
I have a TMO version of Z2 force that I ran stock/rooted for a couple years without any problems. I decided to try Lineage and a couple other ROM's but I got tired of the problems, so I reflashed my phone back to stock using the latest FlashAll that I could find on these threads. So I am back to stock/rooted with no problems EXCEPT my radio sucks now. My home and local supermarket both barely have 1 signal bar if that, where I never had problems before. Phone/4G is very spotty in stores and I usually have to go near a window if I have to text....which I never had to do in the past.
Is it possible I just had a bad flash? Does anyone know which version of radio is the "best"? I currently have the following:
Baseband version M8998TMO_20207.117.02.41.08R NUS
Build OCXS27.1.7
Security patch July 1, 2019
Thx!
Click to expand...
Click to collapse
ianmck said:
I have a TMO version of Z2 force that I ran stock/rooted for a couple years without any problems. I decided to try Lineage and a couple other ROM's but I got tired of the problems, so I reflashed my phone back to stock using the latest FlashAll that I could find on these threads. So I am back to stock/rooted with no problems EXCEPT my radio sucks now. My home and local supermarket both barely have 1 signal bar if that, where I never had problems before. Phone/4G is very spotty in stores and I usually have to go near a window if I have to text....which I never had to do in the past.
Is it possible I just had a bad flash? Does anyone know which version of radio is the "best"? I currently have the following:
Baseband version M8998TMO_20207.117.02.41.08R NUS
Build OCXS27.1.7
Security patch July 1, 2019
Thx!
Click to expand...
Click to collapse
I have read a few post from other users who had stated they were having radio issues with the 27.1.7 flash-all and reverting back to the 27.1.5 flash-all corrected the radio issues.
Sent from my Z2 Force using XDA Labs
fast69mopar said:
I have read a few post from other users who had stated they were having radio issues with the 27.1.7 flash-all and reverting back to the 27.1.5 flash-all corrected the radio issues.
Sent from my Z2 Force using XDA Labs
Click to expand...
Click to collapse
Thanks for letting me know! I'll try that.
way2aware said:
Can I ask, does your wifi still work okay?
I was (am) in your shoes here regards the details you gave in your question, exactly, the only difference being that my radio is non functional- it won't recognize SIM cards, even though it DOES read the iccid off of them, and my z2 force still has the baseband (identical to yours). I have flashed, and blankflashed every possible flashall to get my radio back- none worked, and everything prior to the 27.1.7 build lost my baseband entirely, so I ended up having to reflash 27.1.7.
My wifi still works good at least. My point here is that you may lose your radio entirely by reflashing other flashalls
Click to expand...
Click to collapse
My wifi works perfectly, its just the radio. The radio does work, but the reception seems weaker than it should. I used to get more bars at home and away. Indoor signal is really bad and I have a hard time with talk + text inside buildings, but otherwise seems working.
ive had radio and baseband problems after flashing lineage also... hopefully this helps someone.... nothing could return my sim or data... i found a thread in here about someone asking if anyone had flashed the andriod 10 potato rom... being as my phone was shot i flashed it and it brought back all my data, sim, everything and phone works again... dont know how or why but it worked for me
Can I ask where you got the rom you flashed that fixed it? Also did you try flashing back to stock after the fix worked? If so did everything stick for you?
Related
Hey guys I have a question about baseband compatibility
My GNex is completely stock 4.1.1 and is rooted.
I was on bigxies ROM running uglc1 and I seemed to have better reception with it.
Thing is, ever since I went back to stock, I've tried flashing the same radio over xxlf1 and I can't get any service. I am experiencing the same issues once again such as random signal loss and no service. I ran GetRil and everything is good there.
So is it that you just cant run a different baseband on a factory installed rom or am I doing something wrong?
Any ideas are greatly appreciated.
...Sorry for wasting anyones time http://forum.xda-developers.com/showpost.php?p=23305473&postcount=195
modiand said:
Hey guys I have a question about baseband compatibility
My GNex is completely stock 4.1.1 and is rooted.
I was on bigxies ROM running uglc1 and I seemed to have better reception with it.
Thing is, ever since I went back to stock, I've tried flashing the same radio over xxlf1 and I can't get any service. I am experiencing the same issues once again such as random signal loss and no service. I ran GetRil and everything is good there.
So is it that you just cant run a different baseband on a factory installed rom or am I doing something wrong?
Any ideas are greatly appreciated.
...Sorry for wasting anyones time http://forum.xda-developers.com/showpost.php?p=23305473&postcount=195
Click to expand...
Click to collapse
Not all radio versions are compatible with every version of Android. This sounds like you have a GSM version of the GNex as I myself have a the CDMA/LTE version but in some cases when new version of Android come out or leak or what have you it's best to keep current the radio versions with the OS.... If that helps or makes sense at all. I do know that on the CDMA/LTE JellyBean updates I'm still using the radio versions from 4.0.4 with it and it's perfectly fine. Have you always had the loss in signal or is this only of recent with testing different radios?
PaullieVicious said:
Not all radio versions are compatible with every version of Android. This sounds like you have a GSM version of the GNex as I myself have a the CDMA/LTE version but in some cases when new version of Android come out or leak or what have you it's best to keep current the radio versions with the OS.... If that helps or makes sense at all. I do know that on the CDMA/LTE JellyBean updates I'm still using the radio versions from 4.0.4 with it and it's perfectly fine. Have you always had the loss in signal or is this only of recent with testing different radios?
Click to expand...
Click to collapse
I got it to work. Apparently some thunderstorms knocked out at&t service last night and I was flashing radios during it so when I got done, I couldn't pull any service down. While I'm still without signal, I know its not a radio issue now. Thanks for the response
Sent from my Galaxy Nexus using xda premium
I have had annoying ongoing problem of my phone needing to restart due to my Sim card being removed. I have not removed my sim card at all and it has been happening since I have updated to the newest modem NB4. My setup is as follows the Insane Kit Kat Rom V5 with the included Kernel. To note this has happened since updating to the new NB4 modem. If anyone has any suggestions I would appreciate it.
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
baseballfanz said:
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
Click to expand...
Click to collapse
Really?? That's great, hopefully it stays working great. What kernel are you using?
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
vinniej said:
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
Click to expand...
Click to collapse
I will try all of these suggestions that I have seen so far. What about Odining back to stock and then rooting again? Like I have stated previously I have started seeing this issue since updating to the NB4 Modem and Insane KK. I am sure it isn't the ROM, so I will stick with Insane KK because it is a nice ROM. If anything changes I will report back.
Well, I'm going to take back what I said about fixing it. Sim card removed error happened again. I managed to get a logcat, and dmesg. I have not seen any smoking guns in the logs so I'm going to try a different kernel.
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
crazyc78 said:
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had Talexop's and switched to Ktoonsez's (TW 4.4.2). I did get another error after switching so I'm not sold on a kernel issue either.
I think I'm going to retrace my steps and start from the ground up. I jumped directly from the MDL modem directly to NB4. Maybe I need to go MDL>MK2>NB4?? Maybe try a different Odin version? Switch USB ports on my desktop? Different cable? I'm going to keep trying different things until I get it fixed. It is quite an annoyance because the error happens at times when the phone is asleep and you obviously cannot get any calls, messages, etc.
I'll keep the thread updated for sure.
Been half a day and no errors yet (knock on wood). I did not change anything as far as kernel, rom, or modem is concerned. I did go into Settings>More networks>Mobile Networks>Network Operators>Search Networks and then tapped the tmo network (manual network selection).
I do live / work in an area where Tmo goes bye-bye and there is only Vzn and ATT. I recall having to switch networks recently in order to make a call in that area for work from the no signal zone (I have a spare "work" SIM and my phone is unlocked). Perhaps doing that jacked with my selected default network and could indirectly be the cause of the no sim errors?
And I've done the SIM switch in the past on 4.3 roms without issue. Maybe it is a KK / NB4 bug?
Sounds like you're on track bro, I have tried a few things and so far knock on wood like you said it seems to have worked. First I thought about going back to stock but Odin couldn't recognize the md5 or tar files I downloaded. So then I decided to reflash the NB4 modem. I flashed it three times!! Maybe to see if that would make a difference. Then I reinstalled Insane Kit Kat V5 and did a clean install then restored my backup. So far I have Been running my set up for almost 24 hours and not one error! I will keep looking out for it and report back after my current battery had drained out.
SENT FROM MY INSANELY SICK S4
So I just wanted to give an update on my situation. I have gone back to stock the original 4.2.2, and then rooted my device and then installed Insane KK V5. I have noticed with the stock tar ball file of 4.2.2 I get the NB4 modem. A couple times I did not get the NB4 modem I had the original modem. So then I flashed the NB4 modem and my phone was saying unknown baseband. The last two times I have went back to stock it has given me the NB4 modem and I am still on Knox free bootloader. I am still getting SIM card removed errors, more frequently than ever now. A few times my phone tells me that there is no SIM card inserted at all!!! Very frustrating, I was on a phone call earlier tonight and the error happened during the call. So I called Tmo for a replacement SIM card and we will see if that helps, I'm optimistic that it will. I'm now convinced it may be the NB4 modem, we will see what happens when I get my new SIM. If anyone has any more suggestions I will be open to them.
SENT FROM MY INSANELY SICK S4
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
vinniej said:
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
Click to expand...
Click to collapse
This was the 2nd post in the thread. I've tried all that and for a while I thought it was fixed. I think I made it 4 days without a problem but then they came back.
_eroz said:
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well...Here is my latest and greatest attempt. I flashed the NB4 modem 3 times (no auto reboot throughout the process), and did battery pulls after the first two flashes. 36 hours and no messages.
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
analogchild said:
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
Click to expand...
Click to collapse
I'll try to explain what I know (which ain't much!). In order to avoid Knox some folks including myself have retained the knox free (MDL) 4.2.2 bootloader. How to tell if you have a knox free bootloader look HERE (credit to @shiamatsu) By flashing a modem.bin (which can only be done via. ODIN) we are able to have the benefits of the newer radio, but keep the knox free bootloader. A few of us like _eroz and crazyc78 have seen issues with SIM errors since going to the NB4 modem with MDL bootloader. And thus this thread. And in case you want the instructions to upgrade to the NB4 modem look HERE
I imagine if you don't mind knox and you did the full upgrade, you probably should not be seeing the SIM card errors. I'd be curious to know if anyone is seeing SIM card removed errors with the NB4 bootloader / modem.
Brain hurts. Time for a beer...
Thank you. I'm gunna give it a go and see if it works
This may be a hardware issue. My wife gets it on stock never rooted.
I am curious to know when you flashed the NB4 modem did you go back to stock first and then reroot your device and then flash a rom and then odin the NB4 modem? I did all that and still got errors. I am going to update to Insane Kit Kat V6 later tonight hopefully I don't have issues after updating. I am going to try your remedy and see if it works, and if it doesn'tjust wait for my new simcard.
SENT FROM MY INSANELY SICK S4
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.
One week ago I got sprint model (sm-g920p) used for one week with 0 problems,i decided to update marsmhallow 6.0.1 PB6.
I wasnt getting any ota updates even ota update wasnt in settings anyway.. so i updated through odin.
Everything was ok except service connection, no service,no data,no calls nothing. Tried search manually and auto but no luck. tried gsm or lte or cdma didnt work either. Did factory reset and network reset but no luck.
It supposed to be baseband or imei problem right?
I've checked them but imei and baseband was ok.. but no carrier.
I decided to install another roms and kernels but none of them worked either.
I am out of US zone but my phone is unlocked.
Right now I downgraded to 5.1.1 (OJ7) through odin and everything is ok right now. ( carrier service,3g,4g,lte, everything works fine.)
I am so frustrated and need help, am i missing something here?
Yarraque said:
One week ago I got sprint model (sm-g920p) used for one week with 0 problems,i decided to update marsmhallow 6.0.1 PB6.
I wasnt getting any ota updates even ota update wasnt in settings anyway.. so i updated through odin.
Everything was ok except service connection, no service,no data,no calls nothing. Tried search manually and auto but no luck. tried gsm or lte or cdma didnt work either. Did factory reset and network reset but no luck.
It supposed to be baseband or imei problem right?
I've checked them but imei and baseband was ok.. but no carrier.
I decided to install another roms and kernels but none of them worked either.
I am out of US zone but my phone is unlocked.
Right now I downgraded to 5.1.1 (OJ7) through odin and everything is ok right now. ( carrier service,3g,4g,lte, everything works fine.)
I am so frustrated and need help, am i missing something here?
Click to expand...
Click to collapse
There are issues with the data connection on some phones that get 6.0.1 with specific radio files.
Mine worked just fine after ODIN though.
That said, I installed the Renegade ROM, and have no issues with radio. You have the option of 2 kernels as well with that file, so you can choose your poison.
Karlinski said:
There are issues with the data connection on some phones that get 6.0.1 with specific radio files.
Mine worked just fine after ODIN though.
That said, I installed the Renegade ROM, and have no issues with radio. You have the option of 2 kernels as well with that file, so you can choose your poison.
Click to expand...
Click to collapse
I tried with renegade rom but no luck. And the skyhigh kernel, i wasnt able to boot properly with lamlazy rom tho. maybe i miss somethin with installing instructions.
Anyway, now i am with stock 5.1.1 with unikernelv9.
Are you sure this is a kernel problem?
Saafir said:
Go back to stock 5.1 and take the OTA. Use Wifi if you still arnt getting signal. See how that pans out.
Click to expand...
Click to collapse
+1 on that. always the best option!
Karlinski said:
+1 on that. always the best option!
Click to expand...
Click to collapse
Ok i'll try tomorrow. I will update.
Saafir said:
Go back to stock 5.1 and take the OTA. Use Wifi if you still arnt getting signal. See how that pans out.
Click to expand...
Click to collapse
UPDATE! it's working now!. flashed stock 5.1.1 and got OTA 6.0.1 everything works fine. Thank you guys :*
I flashed the t-mobile flashall on my AT&T Z2 and attempted to return to AT&T stock. Now I have no wifi or cellular and fastboot shows "Baseband: <not found> and attempting to punch in the imei code in the dialer causes the app to crash. I can flash the tmo modem and get wifi back, but no cellular, rendering the phone useless. I've attempted to use the moto smart assistant app to run a rescue but that just breaks things again and makes wifi and cellular inoperable.
Is there any way to fix this?
ohht said:
I flashed the t-mobile flashall on my AT&T Z2 and attempted to return to AT&T stock. Now I have no wifi or cellular and fastboot shows "Baseband: <not found> and attempting to punch in the imei code in the dialer causes the app to crash. I can flash the tmo modem and get wifi back, but no cellular, rendering the phone useless. I've attempted to use the moto smart assistant app to run a rescue but that just breaks things again and makes wifi and cellular inoperable.
Is there any way to fix this?
Click to expand...
Click to collapse
I'm surprised it let you flash the tmo image. I guess as long as it's signed for an xt1789 device it doesn't care?
pitchdarkice said:
I'm surprised it let you flash the tmo image. I guess as long as it's signed for an xt1789 device it doesn't care?
Click to expand...
Click to collapse
It didn't exactly flash the whole image, just the bootloader and the modem. It booted into the AT&T rom with a T-Mobile splash screen.
My best guess is that because tmo is on a newer version of the modem package, downgrading to the older one on the att rom is causing my issue. I'm really frustrated because I've turned my brand new phone into a glorified ipod touch until I find a solution. Not to mention I discovered that att hasn't enabled wifi calling on the stock rom yet which renders the phone pretty-much useless for me anyway.
ohht said:
It didn't exactly flash the whole image, just the bootloader and the modem. It booted into the AT&T rom with a T-Mobile splash screen.
My best guess is that because tmo is on a newer version of the modem package, downgrading to the older one on the att rom is causing my issue. I'm really frustrated because I've turned my brand new phone into a glorified ipod touch until I find a solution. Not to mention I discovered that att hasn't enabled wifi calling on the stock rom yet which renders the phone pretty-much useless for me anyway.
Click to expand...
Click to collapse
I have an at&t z2 force that has the exact issue. Earlier this year I made a mistake and flashed the tmobile modem, tried going back to at&t and ended up with a tiny tablet like you. Every new security patch from at&t I try and flash, and every time the same result as yours - no baseband. Flash back to a tmobile modem for wifi and wait... Hopefully they get Pie and it will become a functioning phone once again.
I liked the phone so I ended up getting a sprint version (lesson learned about locked bootloaders), and the at&t mini tablet sits attached to my jbl soundboost for some sleeping white noise and alarm clock.
Not what you wanted to hear, but you're not alone. Maybe with the $99 sale recently on the at&t version increasing ownership someone will find a way past the locked bootloader and give us hope, but I'm not holding my breath.
cubalis said:
I have an at&t z2 force that has the exact issue. Earlier this year I made a mistake and flashed the tmobile modem, tried going back to at&t and ended up with a tiny tablet like you. Every new security patch from at&t I try and flash, and every time the same result as yours - no baseband. Flash back to a tmobile modem for wifi and wait... Hopefully they get Pie and it will become a functioning phone once again.
I liked the phone so I ended up getting a sprint version (lesson learned about locked bootloaders), and the at&t mini tablet sits attached to my jbl soundboost for some sleeping white noise and alarm clock.
Not what you wanted to hear, but you're not alone. Maybe with the $99 sale recently on the at&t version increasing ownership someone will find a way past the locked bootloader and give us hope, but I'm not holding my breath.
Click to expand...
Click to collapse
Just a heads up, but I turned my phone on today to see it trying to install updates. The update wouldn't complete, so I used the Moto Smart Assistant app to install the update and when I booted back into android I now have cellular service again and a new baseband version. Looks like att finally updated their baseband to a newer version than the tmobile one!
In summary, WOOHOO I didn't waste $100!
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
douglascs77 said:
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
Click to expand...
Click to collapse
I wouldn't recommend this to anyone. Once you flash a pie modem you can't go back, more so flashing a variant not intended for your phone is often the cause of these problems. ATT is a locked bootloader, so you're limited to what you can flash, and when things go wrong it is extremely difficult to solve those problems because of the locked bootloader, and most times it remains so. Not only that, you're not very specific as to what you're actually using, what your system is, and what carrier you're using. -05 covers a few different countries and modems and US modems tend to be very specific. Not trying to be an ass, but you need to offer a lot of info and specifics about your setup otherwise people might blindly flash some pie modem and that'll be the end of it.
douglascs77 said:
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
Click to expand...
Click to collapse
Can u update to android 10?
henrywhtin said:
Can u update to android 10?
Click to expand...
Click to collapse
Unfortunately, Motorola do not gave me an unlock code for my phone.
I'm pissed about this. I'm stuck to Android Oreo. My Moto G5 has Pixel Experience Android 10 rom, it's an amazing upgrade.