Folks, wanted to leave you guys a heads up that some of us are facing issues with the phone not picking up a 4G signal, or picking a signal but not connecting to mobile data or VoLTE after the update to NPL26.118-20
Here's a thread I created specific to India and Jio 4G with Band 5 (850Hz) in the official Lenovo support forum - https://forums.lenovo.com/t5/forums.../Moto_Z/highlight/false/page/1/thread-id/2624
Here's one more thread - https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto_Z/thread-id/2668/page/1
Before you upgrade, use LTE Discovery app to ensure you're not in one of these regions with an affected LTE Band!
Update to the issue - my phone (running 7.1.1) is only trying to connect to Band 5 FDD-LTE in the location where I am at, but does not manage a LTE/ VoLTE signal or connects but drops/ does not connect after reboot. I used another XT1650-03 that is still running 7.0, which connects to Band 40 TDD-LTE (same exact location, same SIM used in both the devices). My service provider is known to utilize multiple LTE bands in the same location, but it is weird that 7.0 connects to Band 40 and works fine but 7.1.1 tries to connect only to Band 5 - that too without success.
I am roaming in a location where both Band 5 and Band 40 are available. 1650-03 with 7.0 connects to Band 40, but 7.1.1 insists on connecting to Band 5 but fails.
I have the same problem in austria.
gason74 said:
I have the same problem in austria.
Click to expand...
Click to collapse
Please post it in detail i n the Lenovo forum link from the first post of this thread. Let's make as much reports as we can there - we haven't seen any solution yet
RETUS Unit here
Only Band 3 works.
Everything else drops out.
(Been trying to downgrade to RETUS 7.0 ever since)
41LY45 said:
RETUS Unit here
Only Band 3 works.
Everything else drops out.
(Been trying to downgrade to RETUS 7.0 ever since)
Click to expand...
Click to collapse
There is no way to downgrade except for going in for replacement, and hope that the replacement device comes with 6.0.1 or 7.0, and not 7.1.1 - I tried this route with the Moto service already, and am thinking of going in for the replacement..
ph03n!x said:
There is no way to downgrade except for going in for replacement, and hope that the replacement device comes with 6.0.1 or 7.0, and not 7.1.1 - I tried this route with the Moto service already, and am thinking of going in for the replacement..
Click to expand...
Click to collapse
There are factory images available (for RETEU only 6.0.1 version is available), if i understand you correctly, downgrading by flashing the full ROM with mfastboot would not work properly...? I'm considering to just downgrade and wait for them to solve the issues with 7.1.1, since sending the device for repairs would be a hassle...
sheratan_b said:
There are factory images available (for RETEU only 6.0.1 version is available), if i understand you correctly, downgrading by flashing the full ROM with mfastboot would not work properly...? I'm considering to just downgrade and wait for them to solve the issues with 7.1.1, since sending the device for repairs would be a hassle...
Click to expand...
Click to collapse
It won't flash the boot, recovery, and system partitions (among others), and will tell you that you cannot downgrade.
I took mine to the service centre, and all they can do is reflash 7.1.1 - they cannot downgrade either, only option is replacement and hope the replaced device comes with 6.0.1 or 7.0
ph03n!x said:
It won't flash the boot, recovery, and system partitions (among others), and will tell you that you cannot downgrade.
I took mine to the service centre, and all they can do is reflash 7.1.1 - they cannot downgrade either, only option is replacement and hope the replaced device comes with 6.0.1 or 7.0
Click to expand...
Click to collapse
Have you tried flashing 7.0 on it? bullfinch110 suggested that the bootloader changed from 6.x to 7.x, that's why you can't downgrade, but flashing 7.0 should be fine. [link]
For you i suppose instead of the RETBR, you'd need some RETIN firmware.
sheratan_b said:
Have you tried flashing 7.0 on it? bullfinch110 suggested that the bootloader changed from 6.x to 7.x, that's why you can't downgrade, but flashing 7.0 should be fine. [link]
For you i suppose instead of the RETBR, you'd need some RETIN firmware.
Click to expand...
Click to collapse
I did not find the retin such image, think I tried the reteu 7.0, but it failed. Let me know if you're able to get it to downgrade - but have at least the 7.1.1 ota handy just in case. What I've found is that the modem will downgrade - and will probably fix the 4G issue, but WiFi won't work.
ph03n!x said:
There is no way to downgrade except for going in for replacement, and hope that the replacement device comes with 6.0.1 or 7.0, and not 7.1.1 - I tried this route with the Moto service already, and am thinking of going in for the replacement..
Click to expand...
Click to collapse
I unlocked the bootloader + used RSDLite to flash the retus 7.0.
Warranties be damned if it's gonna have to be ship it across the world.
41LY45 said:
I unlocked the bootloader + used RSDLite to flash the retus 7.0.
Warranties be damned if it's gonna have to be ship it across the world.
Click to expand...
Click to collapse
That's great.. now I need to find retin 7.0, couldn't find it anywhere
ph03n!x said:
That's great.. now I need to find retin 7.0, couldn't find it anywhere
Click to expand...
Click to collapse
I believe it shares software update line with REAPAC
At least according to this side:https://firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/
Android 7.0 also missing LTE bands
Got my hands on an European Moto Z model xt1650-03 reteu, still on Android 7.0 with security patch of April 1st 2017, and am having LTE-reception limited to Band 1, 3 and 20, although provider and coverage indicate that band 5 and 8 also should be present.
In settings there is only 4g present, no enchanced 4g for LTE or Volte, although having activated those services through my provider (Vodafone CZ). The occasional 4+ is sometimes also showing.
Having read about the problems with the total loss of LTE for several users after upgrading to 7.1.1, I am very reluctant to make the jump before an eventual patch.
Any thoughts from other users with similar issues?
best regards,
mirrormurr, CZ
(posted this also in the lenovo-forum)
After being thrown back and forth between phone support and service center, I have figured out the solution on my own. Long story short, use Baseband (NON-HLOS.bin) version M8996_1258.42.03.11R SID for retin considering it fixes the Jio 4G roaming issue. M8996_1258.42.03.11R is from retcn (XT1650-05)
As of build NPL26.118-20-5-3 (Oct 2017 Security patch), my phone has a Baseband version of M8996_1239.53.01.0126.04.01R SID, which does not work with Jio 4G if it is roaming between different parts of the country that uses different LTE Bands.
M8996_1258.42.03.11R SID works just fine - Jio 4G VoLTE works in roaming, Wifi and BT works too. When I need to update (security updates or to check if Moto finally fixed the problem), I flash the full firmware for NPL26.118-20-5, get OTA updates that came after, check if they fixed the issue (which they haven't till now) and flash M8996_1258.42.03.11R SID NON-HLOS.bin so that I can use my phone.
I also have my wife's phone with a SIM from the same Jio 4G network (in roaming too) that I have kept at 7.0 without upgrading to 7.1.1, only to prove to Moto service that the phone itself is fine, and its the update to 7.1.1 that messed it up. Her phone running 7.0 has Baseband version M8996_1239.53.01.126R SID and works fine in stock form. If I flash this Baseband version on my 7.1.1, 4G and VoLTE will work, but Wifi breaks.
Both the phones are bootloader-locked (never been unlocked), and not modded in any way. If you need any technical detail/ experiments, let me know - I am doing all that I can without unlocking my bootloader anyway.
ph03n!x said:
use Baseband (NON-HLOS.bin) version M8996_1258.42.03.11R SID for retin considering it fixes the Jio 4G roaming issue. M8996_1258.42.03.11R is from retcn (XT1650-05)
Click to expand...
Click to collapse
How did you flash the retcn baseband to your retin model?
Benoe said:
How did you flash the retcn baseband to your retin model?
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
Flashing the modem does not require an unlocked bootloader, so you can experiment with different modems - just make sure you are flashing modem versions from the different variants of XT1650, that's all.
September's 1+GB updated fixed most of the heating and LTE band issues.
You just have to fix the damage caused by the heating by replacing the batery.
41LY45 said:
September's 1+GB updated fixed most of the heating and LTE band issues.
You just have to fix the damage caused by the heating by replacing the batery.
Click to expand...
Click to collapse
Unfortunately, the update did not fix the Jio 4G roaming issue I'd described in the OP. And this is the only fix apart from staying with 7.0 that helps...
Finally, after almost 9 months of dealing with this problem, the retin update to OPL27.76-51 resolved the issue. The phone now readily latches on to Jio 4G when on roaming without me having to go through all the hassles I have been undergoing since I updated to 7.1.1.
Related
I'm running the KitKat+ ROM I found in the development section plus faux kernel, I flashed over jellybean and applied fix v2 so I'm getting no problems uninstalling apps or entering security settings. Thing is when I'm at home or even outside I get really slow network speeds of about 0.4 Mbps down,and in settings-aboutphone-status it switches between hspa and hspa+,but down the road about 350 metres at my kids school I get up to 7 Mbps down,I'm just wondering what version of the moto g is this KitKat+ rom based on,I own the UK retail version and was thinking if its based on a us version would it cause problems with connecting to a UK network or have problems with hspa+ in the UK based on what base this ROM is using,just throwing it out there.
Have you tried setting it to GSM auto (PRL) ?
My previous phone (HTC One X+) was running BlackBean rom and was set to CDMA by default, meant that i had to reset to GSM after every reboot.
I have experienced this also on a UK XT1032 running US Global GSM 4.4.2 - Data works but often slowly and stops entirely for periods of time. I had assumed it was the ROM and I'm waiting for the UK 4.4.2 stock firmware image which I expect will solve it. Perhaps unrelated, but I've noticed Opera Mini will not work over 3G in this ROM, but it works fine on Wifi.
EDIT: I was just thinking; that by fastboot flashing the Stock US firmware image, the UK modem firmware may also have been replaced. That could explain the problems. Flashing back the 4.4.2 UK modem firmware might fix it.
My Baseband version:
MSM8626BP_1032.340.63.00R
Can someone with a US Global GSM XT1032 confirm their Baseband version? Nevermind, confirmed via google. UK Tesco XT1032 running 4.4.2 also has the same Baseband version.
You could try flashing the UK stock 4.4.2 'NON-HLOS.bin' which appears to include the modem firmware. However if I remember correctly, flashing an incorrect radio firmware is one of the few ways to irrecoverably brick a handset.
Safest bet is to wait for the full UK stock 4.4.2 firmware image and fastboot flash that. In future when you flash a different ROM, i.e CM11, you are likely to use CWM/TWRP and the existing UK modem / radio firmware will remain untouched.
If someone wants to correct me on this, please do.
I have a US version MM LTE Nvidia Shield tablet. After the recent update I don't have LTE anymore on my tablet. I have tried to go into Cellular network setting and change the network type manually but the option is not there. I have also tried putting the SIM card into another tablet to ensure that it gets LTE and it does. (Samsung Note Pro 12.2). I have also hard reset and even flashed the MM firmware to see if it was a software issue. Still can't get LTE. I have verified that it only connected to the HSDPA network in the Settings > About Tablet > Status > SIM Status > Cellular Network Type.
I have also tried to download various apps to change the Cellular network type none have worked as of yet.
Does anybody else who has this tablet have the same issue?
If so can anybody recommend a good work around or good ROM to flash to alleviate this issue. I honestly rather go back to the previous firmware version to have LTE back.
Update
I flashed back to Lollipop and still have the same issue.
Update 2
I flashed the ROW version and able to select LTE recommended from Cellular network settings but still doesn't get LTE.
AllTheWay said:
I have a US version MM LTE Nvidia Shield tablet. After the recent update I don't have LTE anymore on my tablet. I have also hard reset and even flashed the MM firmware to see if it was a software issue.
I honestly rather go back to the previous firmware version to have LTE back.
Click to expand...
Click to collapse
Can you be more specific about which update you got? Are you using the US LTE firmware version 4.1? What method did you use to flash the firmware and did you use the full firmware or OTA?
Sent from my Nexus 6 using XDA-Developers mobile app
durgis said:
Can you be more specific about which update you got? Are you using the US LTE firmware version 4.1? What method did you use to flash the firmware and did you use the full firmware or OTA?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I received the Marshmallow 4.1 update from Nvidia. I am using the US LTE firmware version 4.1. Once I realized I was not getting LTE I then reflashed the device using the guide supplied by Nvidia and from the user guide posted on this link.
http://forum.xda-developers.com/shield-tablet/general/stock-recovery-images-ota-library-guides-t2988881
I was thinking of flashing the ROW LTE stock firmware on this device but I don't want to brick it.
Hey, I'm trying to make the lockscreen work on my 6039A under marshmallow, and I think I need the 6.0.1 radios for that to work so if someone who has an upgraded phone could please upload a TWRP backup of their modem partition for me to test, it would be great. Thanks!
Phantom410 said:
Hey, I'm trying to make the lockscreen work on my 6039A under marshmallow, and I think I need the 6.0.1 radios for that to work so if someone who has an upgraded phone could please upload a TWRP backup of their modem partition for me to test, it would be great. Thanks!
Click to expand...
Click to collapse
Hi! I have a few days with the phone and I'm dealing with the same issue. Just a question, if you flash r2 MM zip from 4pda with no additional modifications you get the whole mobile data function working (2G, 3G, LTE) but no PIN or pattern lockscreen, right?
Now, if you replace modem partition from 6.0.1, wouldn't it break some 4G capabilities due to different LTE classes?
pablog_86 said:
Hi! I have a few days with the phone and I'm dealing with the same issue. Just a question, if you flash r2 MM zip from 4pda with no additional modifications you get the whole mobile data function working (2G, 3G, LTE) but no PIN or pattern lockscreen, right?
Now, if you replace modem partition from 6.0.1, wouldn't it break some 4G capabilities due to different LTE classes?
Click to expand...
Click to collapse
When I flash r2 from 4pda I get just 2G and 3G but no LTE with working lockscreen, if I flash my modem partition from CM12.1 on top of it, I get LTE but it breaks the lockscreen.
My assumption is that since the r2 4pda is made for the russian model it removes the LTE band used in my country (Band 4) since the 6039Y doesn't support it, when I restore the modem partition from 5.1.1 I get band 4 support back, but apparently Lollipop radios break lockscreen on the Marshmallow version.
Since the 6039S supports band 4 and got Marshmallow I want to try if flashing the modem partition from it would give me both LTE and Lockscreen since it meets the two requirements I think I need.
This is all supositions from my part, I don't really know much about android development, but I won't be sure until I try and I'm willing to test and report back with results.
Which model do you own?
Phantom410 said:
When I flash r2 from 4pda I get just 2G and 3G but no LTE with working lockscreen, if I flash my modem partition from CM12.1 on top of it, I get LTE but it breaks the lockscreen.
My assumption is that since the r2 4pda is made for the russian model it removes the LTE band used in my country (Band 4) since the 6039Y doesn't support it, when I restore the modem partition from 5.1.1 I get band 4 support back, but apparently Lollipop radios break lockscreen on the Marshmallow version.
Since the 6039S supports band 4 and got Marshmallow I want to try if flashing the modem partition from it would give me both LTE and Lockscreen since it meets the two requirements I think I need.
This is all supositions from my part, I don't really know much about android development, but I won't be sure until I try and I'm willing to test and report back with results.
Which model do you own?
Click to expand...
Click to collapse
Ok. So we are on the same boat (6039A, Argentina, advanced user but not enough to be even a rookie developer ).
When I first flashed the r2 version I thought I haven't had LTE conection due to a non-supported area, but now I see that the problem comes from the russian baseband side.
So, back to the topic, is the modem partition from 5.1.1 the same as 5.0.2? As far as I see we don't have a 5.1 stock ROM for our device (or maybe I haven't seen to much).
pablog_86 said:
Ok. So we are on the same boat (6039A, Argentina, advanced user but not enough to be even a rookie developer ).
When I first flashed the r2 version I thought I haven't had LTE conection due to a non-supported area, but now I see that the problem comes from the russian baseband side.
So, back to the topic, is the modem partition from 5.1.1 the same as 5.0.2? As far as I see we don't have a 5.1 stock ROM for our device (or maybe I haven't seen to much).
Click to expand...
Click to collapse
We don't have stock 5.1.1 but we have a CyanogenMod 12.1 rom which is 5.1.1, I restored the modem partition from there, my guess is that stock 5.0.2 modem should work aswell. If you want I can upload the CM12.1 modem partition for you to try on the r2 version, it should give you LTE but break the lockscreen.
Phantom410 said:
We don't have stock 5.1.1 but we have a CyanogenMod 12.1 rom which is 5.1.1, I restored the modem partition from there, my guess is that stock 5.0.2 modem should work aswell. If you want I can upload the CM12.1 modem partition for you to try on the r2 version, it should give you LTE but break the lockscreen.
Click to expand...
Click to collapse
Ok, it would be great if you could.
I'll also check with stock modem partition from 5.0.2 (which I'm running now).
pablog_86 said:
Ok, it would be great if you could.
I'll also check with stock modem partition from 5.0.2 (which I'm running now).
Click to expand...
Click to collapse
Holy crap, I just booted into 6.0.1 and I have both lockscreen and LTE. What I did was mix both modem partitions from CM12.1 and from Marshmallow and it seems to work.
I will test this to see if it actually works, and if it does I will make a thread explaning how to do it.
Phantom410 said:
Holy crap, I just booted into 6.0.1 and I have both lockscreen and LTE. What I did was mix both modem partitions from CM12.1 and from Marshmallow and it seems to work.
I will test this to see if it actually works, and if it does I will make a thread explaning how to do it.
Click to expand...
Click to collapse
Congratulations! If your workaround is stable we can manage to include it in zip installer (with developer permission, obviously).
So i've read that the sprint version of the S8 Active is on bootloader v5 and the T-Mobile version is bootloader v1. Is it then possible to flash the T-Mobile firmware onto the Sprint Variant ?. The device is already unlocked but i would like Wifi-calling to work for T-Mobile.
Edit 1: Found this and successfully fully flashed from Sprint to T-Mobile(everything works including Wifi Calling). Only works if you are on bootloader version 1.
https://www.youtube.com/watch?v=DEDDTcR1SiQ
I AM NOT THE CREATOR NOR DO I TAKE CREDIT FOR THIS
No apparently the bootloader version must match or be lower so in this case sprint is higher so you can't flash. I've tried and downloaded the tmobile oreo firmware; you'll just get a fail in odin
zed011 said:
No apparently the bootloader version must match or be lower so in this case sprint is higher so you can't flash. I've tried and downloaded the tmobile oreo firmware; you'll just get a fail in odin
Click to expand...
Click to collapse
That is the part i am maybe not understanding. My Sprint S8 active says it is Software version G892USQS1ARC1. Doesn't that mean it is bootloader version 1?
Sorry I was wrong! I actually flashed it! Very happy right now. I was being stupid and using an older version of odin before. Now I successfully flashed sprint to t-mobile oreo with no problems! Use Odin 3.13.1; not prince comsy mod or anything else. So it was bootloader 1 after all; there were some misleading posts without proof. I will trust the software number from now on
zed011 said:
Sorry I was wrong! I actually flashed it! Very happy right now. I was being stupid and using an older version of odin before. Now I successfully flashed sprint to t-mobile oreo with no problems! Use Odin 3.13.1; not prince comsy mod or anything else. So it was bootloader 1 after all; there were some misleading posts without proof. I will trust the software number from now on
Click to expand...
Click to collapse
ARE YOU SERIOUS?!?! Does wifi calling work for you now?
I'm not sure. How can I check? I'm on Fido which is Canadian carrier without WiFi calling. I'm guessing I'm supposed to be looking for a tmobile WiFi calling app. See attachment screenshot for proof. Still recognizes my phone is from sprint
Yeah i just finished flashing it and i get the same as you. Phone still recognized as Sprint and no WiFi calling. Darn. Android 8.0 Oreo is a huge plus however.
zed011 said:
Sorry I was wrong! I actually flashed it! Very happy right now. I was being stupid and using an older version of odin before. Now I successfully flashed sprint to t-mobile oreo with no problems! Use Odin 3.13.1; not prince comsy mod or anything else. So it was bootloader 1 after all; there were some misleading posts without proof. I will trust the software number from now on
Click to expand...
Click to collapse
I think we need to follow this guide to change carrier but the thing is there is no factory binary for the s8 active so this guide won't work until there is one...
https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487
Actually I have found and flashed a factory binary trying to change it to T-Mobile. The problem I ran into is they want you to download the firmware with "w" after the model number. That is what I think let's you change the option after typing in the code. That firmware is only for s8 I think(not active as it has the s8 model #). Without flashing that, after I typed in the code the only option I had to choose from was sprint. No "xac" or whatever it was.
If I am not mistaken. The model with the "w" is the Canadian version of the s8. The s8 active is US only I think.
So Im getting ready to pick up a Sprint version to use on Att or Tmobile (good deal). Are you guys seeing any issues after flashing? Thanks
jmill75 said:
So Im getting ready to pick up a Sprint version to use on Att or Tmobile (good deal). Are you guys seeing any issues after flashing? Thanks
Click to expand...
Click to collapse
The only thing I've notice is there is no option for mobile hotspot( i don't think it was there to begin with, i could be wrong however). Other than that it works perfectly. Great battery life and everything. Flash the userdata to get rid of the Sprint Boot animation if you'd like. I did it and now there is just the "Samsung s8 Active" logo, then lock screen. Goodluck.
Mohamed1993 said:
The only thing I've notice is there is no option for mobile hotspot( i don't think it was there to begin with, i could be wrong however). Other than that it works perfectly. Great battery life and everything. Flash the userdata to get rid of the Sprint Boot animation if you'd like. I did it and now there is just the "Samsung s8 Active" logo, then lock screen. Goodluck.
Click to expand...
Click to collapse
Do you have a link by chance to the files? Thanks
After flashing Sprint variant of the device to T-Mobile firmware, do all features work: WiFi Calling, Band 12, VoLTE and Band 71?
Charkatak said:
After flashing Sprint variant of the device to T-Mobile firmware, do all features work: WiFi Calling, Band 12, VoLTE and Band 71?
Click to expand...
Click to collapse
No wifi calling, no VoLTE. Not sure about the bands
Charkatak said:
After flashing Sprint variant of the device to T-Mobile firmware, do all features work: WiFi Calling, Band 12, VoLTE and Band 71?
Click to expand...
Click to collapse
WiFi calling works fine on T-Mobile without flashing to T-Mobile firmware. Only issue is that sometimes it gets stuck enabling WiFi calling requiring a reboot. Band 12 also works, its in the Sprint specifications. The big question I wonder about is if band 71 can be enabled.
flash not working?
i flashed the tmobile firmware and after its all dont i boots up does an update and then boots with all the sprint stuff still
snowfirebeast said:
i flashed the tmobile firmware and after its all dont i boots up does an update and then boots with all the sprint stuff still
Click to expand...
Click to collapse
Did you follow the video I posted?. Ignore all the other comments about things not working. When i updated the OP with the link, it fully flashed the sprint device to T-Mobile. The only thing you have to watch out for, is if your Sprint software is running a new bootloader. You can tell by looking at the baseband version number. This will only work if you are on bootloader 1. My baseband is currently "G892USQS1BRD5". The bootloader version is the 5th character starting from the right. The number 1 before "BRD5".
Hi all,
Anyone tried to burn a SM-F721U1 device with sm-f721u firmware?
I remember doing it on a note10. Question is if it's still possible?
seems to flash just fine. I have only found tmo and u1 with july patch... are there others?
I tried. Mobile network get disabled. Grey out in status bar. I am using US Mobile services. I have to do a fresh flash A12 VZW build to get back working handset.
I was wondering this as well. I purchased my first unlocked phone and now I wait for the 13 update, while the T-Mobile version is already out. I am on T-Mobile, so I'm guessing it will work just fine. Will my phone still be "unlocked" if I flash the SM-F721U firmware?