Hi,
Recently, I used ODIN to return to Stock ROM. But, since then I am not getting OTA updates.
Once I used Smart Switch app to update software but I don't want to do it all the time.
Can someone please help? Thanks.
Tanay
Any help would be highly appreciated !!
Maybe just flash a firmware that receives OTAs constantly, like UK BTU.
Since you know how to use Odin. Flash the XEF firmware. It's the best with receiving monthly updates.
is there a way a phone can lose its ability to receive OTA updates.
Smart Switch shows new update, but not getting OTA.
Got the software update done from service center, but still no OTA when available.
Every time Smart Switch downloads around 2 GB of data which is very time consuming in India, I am not sure what is the best way to get my OTA updates back.
Someone please help.... Thanks.
tanaysrivastava23 said:
is there a way a phone can lose its ability to receive OTA updates.
Smart Switch shows new update, but not getting OTA.
Got the software update done from service center, but still no OTA when available.
Every time Smart Switch downloads around 2 GB of data which is very time consuming in India, I am not sure what is the best way to get my OTA updates back.
Someone please help.... Thanks.
Click to expand...
Click to collapse
something was changed in the kernal or you have applied a custom kernal. causing the phone to believe it has been modified
modified phones will not receive OTA updates you need to flash them manually.
What about the CSC? maybe you flashed wrong csc.. Or have multiple csc.
Cosmic Blue said:
something was changed in the kernal or you have applied a custom kernal. causing the phone to believe it has been modified
modified phones will not receive OTA updates you need to flash them manually.
Click to expand...
Click to collapse
modaifallah said:
What about the CSC? maybe you flashed wrong csc.. Or have multiple csc.
Click to expand...
Click to collapse
This could be possible.
I tried BTU beta ROM for Nougat and then reverted back.
But, current status shows official.
After manual update, Kernel version is changed to latest.
Please help, how can I correct my phone's settings. I have attached, my phone's software info page.
tanaysrivastava23 said:
This could be possible.
I tried BTU beta ROM for Nougat and then reverted back.
But, current status shows official.
After manual update, Kernel version is changed to latest.
Please help, how can I correct my phone's settings. I have attached, my phone's software info page.
Click to expand...
Click to collapse
Currently you have the latest update for your phone.
but you can try : cleaning the cache.
if the problem persists, you may have to make a back up of your data and phone numbers and do a full factory reset, that should return your phone completely back to stock.
Cosmic Blue said:
Currently you have the latest update for your phone.
but you can try : cleaning the cache.
if the problem persists, you may have to make a back up of your data and phone numbers and do a full factory reset, that should return your phone completely back to stock.
Click to expand...
Click to collapse
Thanks. But I tried clearing cache and factory reset already a few times, but that didn't help.
Also, there is another update available to my ROM, but not getting option over OTA. But, showing the update via Smart Switch.
Is there any way I can put correct Kernel or CSC to my phone? or, any other way to overcome my situation. Thanks.
I'm all stock and my android security patch is of 1 November 2016.. You're on the latest update.
A few things which I did recently might have caused my problem.
01) I was running at Stock ROM and getting OTA updates
02) I installed Nougat Beta BTU ROM
03) Registered myself to get OTA updates
04) But, didn't get OTA updates, returned to Stock ROM via Odin
05) I got updated to latest software by OTA updates
06) Again, I installed Nougat Beta BTU ROM, deregistered & registered again and got beta OTA updates
07) After a few days, returned back to Stock ROM
08) Since then, I am not getting OTA updates.
It seems, I am registered to get BTU OTA updates and lost my OTA update eligibility here (India)
Now, I will install Nougat Beta BTU ROM again and will deregister myself from there. Hope that way, I will get my OTA updates here in India.
I will keep you all updated. Thanks.
tanaysrivastava23 said:
A few things which I did recently might have caused my problem.
01) I was running at Stock ROM and getting OTA updates
02) I installed Nougat Beta BTU ROM
03) Registered myself to get OTA updates
04) But, didn't get OTA updates, returned to Stock ROM via Odin
05) I got updated to latest software by OTA updates
06) Again, I installed Nougat Beta BTU ROM, deregistered & registered again and got beta OTA updates
07) After a few days, returned back to Stock ROM
08) Since then, I am not getting OTA updates.
It seems, I am registered to get BTU OTA updates and lost my OTA update eligibility here (India)
Now, I will install Nougat Beta BTU ROM again and will deregister myself from there. Hope that way, I will get my OTA updates here in India.
I will keep you all updated. Thanks.
Click to expand...
Click to collapse
I'm experiencing the same thing as you.Tried multiple firmwares but only BTU works(something has to do with nougat).Waiting for the results
Cristi_10 said:
I'm experiencing the same thing as you.Tried multiple firmwares but only BTU works(something has to do with nougat).Waiting for the results
Click to expand...
Click to collapse
I did as I mentioned and this resolved my problem :good::good:
Many thanks to all for supporting me !!
I'm in this version and until now, no OTA here, that's weird.
Not getting OTA after back to INS from BTU
i am facing this issue so i installed Beta firmware and de-registered from beta program then installed Stock Rom now i am getting OTA
I am also facing same issue.... Any method to de-register from Beta without installing Beta firmware?
I tried by installing Beta registration apk... But it doesnt works.
AlanDS said:
I am also facing same issue.... Any method to de-register from Beta without installing Beta firmware?
I tried by installing Beta registration apk... But it doesnt works.
Click to expand...
Click to collapse
Everyone has done that so far. I am not aware of any alternate method.
So the second BTU Nougat update was released on 6th Feb. I flashed the first BTU Nougat at the start of the month using Odin (from Sammobile site, flashed AP and CSC files), cache reset, 2 factory data resets later, and now my CSC shows BTU in the recovery boot screen, yet even today (17th Feb) I'm still not getting the OTA update for the second Nougat.
Manual software update screen tells me I'm up to date!
"The latest updates have already been installed.
Current version: G935FXXU1DPLT/G935FOXA1DPLT/G935FXXU1PBJE"
Yet the latest version is: https://www.sammobile.com/firmwares/download/122404/G935FXXU1DQB3_G935FOXA1DQB1_BTU/
PDA G935FXXU1DQB3
CSC G935FOXA1DQB1
Anyone had similar issues? I know they're both still Android 7.0 but surely the later build should be detected for OTA updates? I will probably eventually give up and flash the latest, but the whole reason for the 2 factory resets at the start of the month was to make sure the BTU CSC applies so that I can get OTA updates from now on and not have to bother with flashing for every single update going forward... Don't particularly want to revert to the bloatware-filled branded version the phone came with... They're still 'testing' Nougat anyway, release date will be 'soon', and has been 'soon' for weeks now... Hence my BTU flash.
AngelaRI said:
So the second BTU Nougat update was released on 6th Feb. I flashed the first BTU Nougat at the start of the month using Odin (from Sammobile site, flashed AP and CSC files), cache reset, 2 factory data resets later, and now my CSC shows BTU in the recovery boot screen, yet even today (17th Feb) I'm still not getting the OTA update for the second Nougat.
Manual software update screen tells me I'm up to date!
"The latest updates have already been installed.
Current version: G935FXXU1DPLT/G935FOXA1DPLT/G935FXXU1PBJE"
Yet the latest version is: https://www.sammobile.com/firmwares/download/122404/G935FXXU1DQB3_G935FOXA1DQB1_BTU/
PDA G935FXXU1DQB3
CSC G935FOXA1DQB1
Anyone had similar issues? I know they're both still Android 7.0 but surely the later build should be detected for OTA updates? I will probably eventually give up and flash the latest, but the whole reason for the 2 factory resets at the start of the month was to make sure the BTU CSC applies so that I can get OTA updates from now on and not have to bother with flashing for every single update going forward... Don't particularly want to revert to the bloatware-filled branded version the phone came with... They're still 'testing' Nougat anyway, release date will be 'soon', and has been 'soon' for weeks now... Hence my BTU flash.
Click to expand...
Click to collapse
If you're registered for the BETA you will not receive any OTA updates other than those that are BETA updates. You would need to deregister.
Hey all. I am in the US but bought international S7Edge when it came out. I dont know what firmware it had I think it was some italian one maybe. Then i rooted and started using custom roms. Then when nougat officially came out for S7Edge i un-rooted and went back to 100% stock using i think Vodafone 7.0 firmware. I think because i rooted i have a negative test response from Knox which i think stops me from getting OTA updates. It shows in software info that my OS version has security patch only from January 2017 so I am clearly not on latest firmware even though OTA says I am on latest.
Is there a site with a database of all firmwares out for the S7Edge international variant So i can find the latest and flash it to my phone since OTA wont get the latest.
samsmobile has the latest.
Yoiu still have an issue with your kernal as phone still thinks you have custom rom. Tripped knox on stock firmware will not stop OTA from downloading.
I am having xt1686 indian variant .. i unlocked the bootloader and installed the custom roms.. now while going back to stock i mistakenly installed NPNS (US VARIANT, I suppose) ..
I am unable to install the NPN version now .. i guess the bootloader is not matching ..
Right now i am having a bootloader - C0.8(*) in NPNS ...
PLEAAE SUGGEST HOW TO MOVE TO INDIAN VERSION OF NPN... THNKS..
S does not mean US or any other variant specific build... there are literally different builds for different variants. My US Retail version is NPN25.173-83
In previous Moto models, the S meant it had been upgraded from an OTA, but in looking in my current device it has received several OTAs and does not have the S, so either that has been depreciated or our original assumptions in earlier models was incorrect.
Either way, the fact the S is there does not mean US (or any other country), just a slightly different build... I don't have an answer of why you can't go back though.
https://forum.xda-developers.com/g5-plus/help/npns-nps-firmware-t3677576
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
abhi.a3s said:
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
Click to expand...
Click to collapse
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. If you've flashed a NPNS firmware, you'd likely be at least on the may security patch. The Indian firmware you'd need is the January patch (NPN25.137-15, as I don't think the NPN25.137-67 or 67-5 firmwares have been leaked). Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
echo92 said:
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
Click to expand...
Click to collapse
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
abhi.a3s said:
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
echo92 said:
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Click to expand...
Click to collapse
Well ofcourse there is a big potential of hard bricking the device by the method. That's why I said last resort.
So what do you suggest?
TWRP image? And if it doesn't work, he should probably wait up for next NPN build? @toyesh.patra you should consider keeping a custom rom if possible.
Btw
The ota update which I received was August patch. After which I unlocked my bootloader. It was either NPN25.137-67 or NPN25.137-67-5. I'M not sure about version. But it was definitely August patch.
Or maybe I was lucky one time.
Won't do it another time.
anuraag.neo said:
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
Click to expand...
Click to collapse
For 1686? Full fastboot firmware leaked?
yea, right now i m using the 67-5 build using twrp..
although i wanted to use the 67-5 with locked bootloader.. nevermind ..
psychopac said:
For 1686? Full fastboot firmware leaked?
Click to expand...
Click to collapse
Yes
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
psychopac said:
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
Click to expand...
Click to collapse
Yes
I can't download it. How Can I download? please upload googel Thanks bro
birkhoffChang said:
I can't download it. How Can I download? please upload googel Thanks bro
Click to expand...
Click to collapse
use search function before asking
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738