I have a Bell Canada Nexus 6P running Android 7.0 and it tells me that there are no updates available when we're already past 7.1 to 7.11. This is a work phone, so installing custom ROMs won't be acceptable, but I do want it up to date (otherwise I would have gotten a Samsung ). Any suggestions as to what might be wrong?
I have recently gone through 2 full resets, one when I came off the developer beta stream for hardware troubleshooting and one when encryption failed and I would really not want to go through that again.
I checked my work policies and while they want me up to date, developer beta channel is frowned upon. As well, coming off the beta program was painful as none of my apps or settings were remembered. So I'd like to avoid that route.
Thanks
Peter
Is there a problem unlocking the device , flashing the full factory image and relocking the device?
That would be the easiest and simplest route in my opinion.
peliopoulos said:
I have a Bell Canada Nexus 6P running Android 7.0 and it tells me that there are no updates available when we're already past 7.1 to 7.11. This is a work phone, so installing custom ROMs won't be acceptable, but I do want it up to date (otherwise I would have gotten a Samsung ). Any suggestions as to what might be wrong?
I have recently gone through 2 full resets, one when I came off the developer beta stream for hardware troubleshooting and one when encryption failed and I would really not want to go through that again.
I checked my work policies and while they want me up to date, developer beta channel is frowned upon. As well, coming off the beta program was painful as none of my apps or settings were remembered. So I'd like to avoid that route.
Thanks
Peter
Click to expand...
Click to collapse
Enable "USB Debugging" in Developer Options then boot into stock recovery and ADB sideload the December 7.1.1 OTA image:
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk
Thanks for the suggestions:
@ibsk8: Unlocking, flashing and relocking is something I have tried before but the monitoring software detected it (different phone but don't want to risk red flags)
@SlimSnoopOS Great suggestion, but I was reluctant to reset my phone again...
...however, I didn't get much choice but to reset as I got another decryption error with the only choice being to factory reset. After the reset, I was able to upgrade to 7.1.1 OTA
Thanks!
Peter
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
tbmoc96 said:
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
Click to expand...
Click to collapse
Try the flash all bat with stock rom and then relock your boot loader
Sent from my Pixel XL using Tapatalk
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
bennyboy2120 said:
Try the flash all bat with stock rom and then relock your boot loader
Click to expand...
Click to collapse
coremania said:
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
Click to expand...
Click to collapse
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Again try relock on the boot loader and tell me if it helps
Sent from my Pixel XL using Tapatalk
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
bennyboy2120 said:
Again try relock on the boot loader and tell me if it helps
Click to expand...
Click to collapse
The guide has the re-lock part so I'm 100% sure I tried to re-lock the bootloader. Not only the Google guide but on other topics on xda and Nexus Community someone re-locked the bootloader and they fixed the problem. Therefor, I followed them to re-lock but still no service
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Click to expand...
Click to collapse
I also tried to flash back to 6.0.0 first release firmware and 6.0.1 to get vendor for chroma / purenexus , still the same
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
Click to expand...
Click to collapse
My imei still there, I also have EFS backup ;(
tbmoc96 said:
My imei still there, I also have EFS backup ;(
Click to expand...
Click to collapse
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
coremania said:
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
Click to expand...
Click to collapse
I lost the network right after I upgraded my phone through OTA ;( I flashed stock firmware right after that so I guess it's not come from EFS partition. I backed up all things with TWRP after I had finished the flash-all.bat process. I'm checking out the thread, maybe there's a way out?
Yesterday I brought my phone to Huawei service center in my country but they don't officially sell the Nexus 6P in my country so they didn't take the phone because they don't have anything to fix its problem.
I would try, seems that you got nothing to loose
I'm having the same problem.
I've tried everything you did and when I select automatic bands in 4636 it does successfully, but still no signal.
Also, when I search for network in the mobile settings it always error.
I noticed that my GPS also stopped working. I only can use apps like Maps if I'm connected to a Wi-Fi.
Since the GPS stopped working this makes me believe it's an antenna problem.
If I selected WDCMA Only my network goes to Global instead of what I've selected.
I have the xt1511 (US Nexus Version), but since Nexus is always unlocked I know it isn't a CDMA/GSM trouble.
My wife's 6P started doing this about a month ago where she would randomly lose service for a minute. Today she lost it completely and it seems like there is an issue internally with the radio. I've tried multiple sim cards, factory resets, flashing the latest factory image, trying an old radio version etc. It seems like there has to be some kind of defect. I would hang on to the phone just in case there ends up being a class action lawsuit. Her phone is exactly one year and one month old.
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing... Now what?, we dont know if its a hardware problem or is it a software one. Should I take it to a service center in the us? I have no warranty.
Click to expand...
Click to collapse
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
In my case I have a 1511 and I've tried this Chroma fix. No success.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
its the 1511 version. Yes the phone worked perfectly after the repair. I was in the US, and three weeks ago I came to colombia. Suddenly it stoped working a couple of days again. I tried the chroma rom. Selected the Auto band. but it did nothing, rebooted and everything but didnt work.
Earlier today i installed a older factory image and it work, i thought it was solved, then i flashed twrp, rooted and lost service again... tried the factory images again and nothing...
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Debuffer said:
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Click to expand...
Click to collapse
Hey, i went to my carrier. And they tol me it was blocked. And they un blocked it.
It was imei blocked because ut wasebt in that imei national list. Soo it didnt work with any carrier.
you've fixed your phone
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
I can not have a case if you are not resolve. Im vietnames my english very bad sory!. Help me
Hi all.
I've asked this question in numerous threads so, to be fair to all the others whose questions I'm getting in the way of, I thought I'd post it here and wait with baited breath for a potential solution.
I very recently bought an XT1684 (3GB/32GB) UK G5 Plus. I installed all the official OTAs and got myself up to firmware version NPNS25.137-33-11. All was well, amazing battery life, but needed root for some apps. The steps I followed are roughly as follows:
1. Unlocked bootloader: I did this the usual way, got my code, chucked it into fastboot etc voila, job done.
2. BOOTED Twrp: I did this so I could attempt to back everything up without modifying, for purpose of returning to stock. It didn't work, I could not back anything up nor could I install magisk or a custom kernel. My Twrp would not read the internal storage and said something about formatting data. I ended up formatting data, which actually formatted the whole damn thing, losing my stock ROM completely.
3. FLASHED Twrp: By this point I had to, as I had limited access to the internet outside of my phone so put a lineage ROM on my phone and some gapps and flashed it.
4. Installed magisk 15.3
5. Installed Alize kernel: I did this because I was looking for improved battery life over the lineageos kernel. It hasn't been better.
So that's where I am. I have two main reasons I need to return to stock:
1. The battery life was better on my stock firmware.
2. Whenever I use lineage, I find my signal not to be as strong, and it seems to randomly lose all signal for a few seconds several times an hour, usually affecting my data more than voice calls. This is absolutely not something that happened on stock. I dunno if it's related to baseband or something, but it happens and I don't like it.
My main issue is I have seen several retUS versions of the firmware above, and lots about many other XT16xx models but nothing about my XT1684 and no fastboot images for retGB. I'm comfortable flashing pretty much anything via Twrp as I have a full backup of all partitions including OEM, system image etc but these were taken after installing lineage. I'm just totally not comfortable fastboot flashing anything except the exact correct firmware, as I've had this phone literally a week.
If anyone can help me locate the right firmware, or advise me how I could possibly return totally to stock, that would be amazing. I can provide any logs or other information required, but may need walking through more obscure commands as I am only technically proficient enough to do a basic fastboot flash, Twrp, etc.
Many thanks for reading and my apologies to all of those whose threads I've muscled in on up to this point.
Filmware is here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
And there is a tool that automates flashing in the development section here..
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
Firmware - https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
How to flash - https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
?hope it helps.
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it.
Could someone confirm that these are safe to flash for me? Thanks for the replies, though.
Your filmware is there yes? Having said that mine is a xt1685 the same filmware number as yours but mine is euret dual SIM. Sold by Amazon UK
My confusion is that I thought they were for US models.
Well US version has no NFC but had a compass.
Has yours?
Mine has NFC and no compass lol!
darkglobe87 said:
Mine has NFC and no compass lol!
Click to expand...
Click to collapse
Seems to be typical for EU G5+ devices, NFC but no compass.
The retail firmwares don't appear to have region restrictions, hence no labelling for retEU/retGB/retUS etc. However, as you may have noticed, flashing the incorrect build for your region causes all sorts of headaches, including loss of SIM network.
That being said, you know what firmware you need (NPNS25.137-33-11) and that particular firmware was only released for EU/UK devices to the best of my knowledge. India/Brazil, US and other territories had different firmware builds released.
So, you should be okay with flashing that particular firmware - but please verify you have the correct firmware downloaded and the correct flashing instructions, and take your time in flashing.
Also, if you choose to re-lock your bootloader, re-locking your bootloader will unfortunately not restore your warranty with Motorola (which is 2 years now for EU/UK users at least). However, UK consumer laws may cover you in the eventuality of hardware repairs, just be careful. Also, re-locking will erase your device and requires firmware of the same build or newer than what is currently on your device.
Good luck whatever you decide.
I have the UK version and have gone back to stock a few times, I used this thread, and the linked firmware is the same as UK one. The guide is for bootloader locking, but ignore that part if you only wish to return to stock.
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952