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.
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
goast said:
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
Click to expand...
Click to collapse
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Global Version
stompysan said:
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Click to expand...
Click to collapse
Do you have a link as to where i can get Global version or steps for getting it ?
j1232 said:
Do you have a link as to where i can get Global version or steps for getting it ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
stompysan said:
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
Click to expand...
Click to collapse
How can one tell of phone is using 5g SA on OB3?
crazynapkinman said:
How can one tell of phone is using 5g SA on OB3?
Click to expand...
Click to collapse
Using a program like LTE Discovery will tell you. In my case, it indicates I am connected to NR NSA 5G. I have not ever seen my phone go to SA 5G since converting, and I do live in an SA location and have connected while on T-Mobile software. See screenshot.
Mine says 5G NR
crazynapkinman said:
Mine says 5G NR
Click to expand...
Click to collapse
I have noticed it takes some fiddling with WiFi to get it to display network type. The 5G detection is still a WIP. There are probably other apps that may work better, but I am just used to using LTE Discovery over the years.
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
xxBrun0xx said:
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
Click to expand...
Click to collapse
I have Sprint sim and this is not happening.
I purchased a fully unlocked OnePlus 8 (IN2015) but have discovered that only the OnePlus 5G UW (running Verizon firmware) can use all of the Verizon network features like wifi calling, vvm, etc. I have reflashed carrier phones with global firmware in the past, but is it possible to go in reverse? Where do I find the carrier images?
I certainly can't speak to the whole "going in reverse" thing, but you can find the Verizon MSM image here. Worst case scenario, you try and it fails, MSM back to the unlocked global and you're back to square 1.
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?
i am running the t mobile version with the global firmware. i updated with the indian version before everyone realized that it wasn't a global version (like every past OOS update). had the no signal issue (i'm assuming the indian version doesn't have the right radio bands for the us versions). i rolled back to OOS 11 and got my data signal back, waited for the global/us version (which just came out) but when I try to flash it I am still getting the same no signal issue. Oxygen Updater still thinks i have the Indian version, it says:
"It looks like you've selected the wrong device, "OnePlus 7 Pro" instead of "OnePlus 7 Pro (India)"
In Android Settings, phone is listed as GM1917 (Global/International Version)
Any help would be greatly appreciated!
I was able to regain tmobile data by flashing the modem.img from oos11 to finally fix this. Give it a shot go here. Do a data backup in case.. I had no problems until I did a data wipe after setting up the phone. I am not sure if this is a good fix or not but it works on my phone. Anyone else have a suggestion I am open to it.
So to do this I need to unlock my bootloader and setup TWRP? Right now everything is stock other than the global firmware...