Database Users

Is there a full firmware available for the US version's latest NPNS25.137-35-5

I am trying to re-lock the bootloader, which requires flashing a stock firmware. But it won't allow flashing any older version due to older security patch. Any ideas?
Is the full firmware for the US version with May security update available somewhere?

If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)

echo92 said:
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
Thanks a lot.
That worked perfect. Flashed NPNS25.137-35-5 on my US unlocked version and it got the May security patch.

suhridkhan said:
Thanks a lot.
That worked perfect. Flashed NPNS25.137-35-5 on my US unlocked version and it got the May security patch.
Click to expand...
Click to collapse
Hi!!! Hey could you please help me with something? Can you tell me which version of bootloader you have right now?
To know that, you have to restart the phone into bootloader mode, and you have to tell me the number after BL: line
You'll see something like:
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:7) <---- THIS IS WHAT I NEED TO KNOW!!! Please!
Or could you take a picture of this screen?

MarckozZ said:
Hi!!! Hey could you please help me with something? Can you tell me which version of bootloader you have right now?
To know that, you have to restart the phone into bootloader mode, and you have to tell me the number after BL: line
You'll see something like:
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:7) <---- THIS IS WHAT I NEED TO KNOW!!! Please!
Or could you take a picture of this screen?
Click to expand...
Click to collapse
I got this.
BL: C0.8A(*) (sha-c90d6a9-dirty, 2017-04-24 13:31:32)
Just curious, what is the use of this information?

suhridkhan said:
I got this.
BL: C0.8A(*) (sha-c90d6a9-dirty, 2017-04-24 13:31:32)
Just curious, what is the use of this information?
Click to expand...
Click to collapse
I totally hardbricked my potter. To revive it, I had to blankflash some files from other Moto phone. Now I have the bootloader from Moto Z Play (which has the version number I gave you as an example).
I asked you the bootloader version to make sure I can flash the new 135.5-5 bootloader and partition table to return my phone back to normal! But since I have software parts from Moto Z Play, I'm afraid it wont accept potter bootloader back again. So, I'll test this later!

echo92 said:
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
Great question. Mine is the US version with -33, so it must not be an EU firmware. I asked the same question a few weeks back and no one can confirm either way. I do wish we had some confirmation so someone doesn't flash the wrong version. Maybe if everyone responded with version info (screenshot?) and location?

long2ski said:
Great question. Mine is the US version with -33, so it must not be an EU firmware. I asked the same question a few weeks back and no one can confirm either way. I do wish we had some confirmation so someone doesn't flash the wrong version. Maybe if everyone responded with version info (screenshot?) and location?
Click to expand...
Click to collapse
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
Code:
ui_print("Source: motorola/potter/potter:7.0/NPN25.137-33/35:user/release-keys");
ui_print("Target: motorola/potter/potter:7.0/NPN25.137-35/37:user/release-keys");
3)Seems that devices running on other networks are on the 137-33 firmware (e.g. AT&T, retus: https://forums.lenovo.com/t5/Moto-G...ce-G5-plus-stuck-on-NPN25-137-33/td-p/3738547)
4) Seems that there's 2 update paths to the May security patch:
From 137-33 > 137-35 > NPNS25.137-35-5 (this May update seems to be also the wider reported version too for US devices, probably this is the path if you are on the Verizon network)
From 137-33 > NPNS25.137-33-5
I don't know if there's any major differences between the 2 builds besides the VoLTE 911 fix, or if you were on the 137-33-5 build whether you could switch to the Verizon network and be able to make emergency calls on VoLTE (I honestly would hope that fix was rolled into both May patches though...) I'm also not sure what factors decide which update you get, besides possibly being on the Verizon network at some point?
I honestly hope at a later date, Motorola unifies the firmware (like they've done with the G4 Plus), so you can just flash one version rather than multiple different types.
Again, if someone has more information (as I don't have a G5 Plus), feel free to add/correct what I've written!

I have a US version that was shipped with NPN25.137-35 and I'm on the AT&T network.

echo92 said:
If you're after the NPNS25.137-35-5 firmware, have a look here: https://www.androidfilehost.com/?a=show&w=files&flid=171014 (Just ensure you download the firmware that doesn't have AMZ in its name for retail devices, AMZ is for Amazon Prime devices )
Please doublecheck that it's the right firmware for you - I'm trying to work out which firmwares are for which regions, but Motorola isn't making it easy...
EDIT - maybe people can confirm, is this accurate (I sourced the info from the Moto G5 Lenovo forums)?
G5 Plus (potter)
NPN25.137-15 (India), updated to NPN25.137.67 (March security patch)
NPN25.137-33 (EU?) - updated to NPNS25.137-33-5 (May security patch)
NPN25.137-35 (US?) - updated to NPNS25.137-35-5 (May security patch)
Click to expand...
Click to collapse
That last one for indian version?and it's latest .67?

dayask said:
That last one for indian version?and it's latest .67?
Click to expand...
Click to collapse
If you mean the NPN25.137-35 firmware, I don't think it was released in India (unless your device came with it?). As far as I can tell, looks like 137-67 appears to be the latest build currently for India.

echo92 said:
If you mean the NPN25.137-35 firmware, I don't think it was released in India (unless your device came with it?). As far as I can tell, looks like 137-67 appears to be the latest build currently for India.
Click to expand...
Click to collapse
So which one you recommend?

Hello XDA - Am new here, but thought i'd share my info - I have build number NPNS25.137-33-5 (7.0 Nougat) with 1. May (just upgraded from jan/feb if memory serve) as latest security patch. I am from Europe, more specific based in the Benelux area (NL/BE/GE) - If i can provide any more info on the matter, please let me know!

dayask said:
So which one you recommend?
Click to expand...
Click to collapse
I'd suggest staying on NPN25.137-67 if you're on an Indian device, else you may not receive OTA updates. Furthermore, if you swap to 137-35 you may run the risk of bricking your device in future.

So I went ahead and took a chance and flashed the *35 build on top of *33 in rsd lite. It works. Almost immediately I got the OTA of the *35-5 update. I think @echo92 is right and it is more geared towards Verizon. It took me a little to get AT&T to work on LTE here in the US but it all seems fine now.

I had -35 flashed on EU device and no updates for me.

wiceqq said:
I had -35 flashed on EU device and no updates for me.
Click to expand...
Click to collapse
Ah, then you may be on the wrong build for the EU region (I've only seen reports of 137-33 for the EU), and thus the reteu software channel might not have an update for you. I see from your previous post you flashed the 137-35 update onto your device?
I honestly don't know if you can safely revert to NPN25.137-33, but here's a stock NPN25.137-33 ROM to flash via fastboot (as always, back up your data and keep it off your device, as this fastboot ROM will likely wipe your device in the flash): https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I also do not know what will happen if you try to flash the NPNS25.137-35-5 update onto a reteu device (it might work, but could result in you being off the update path still).
Good luck either way.

echo92 said:
Ah, then you may be on the wrong build for the EU region (I've only seen reports of 137-33 for the EU), and thus the reteu software channel might not have an update for you. I see from your previous post you flashed the 137-35 update onto your device?
I honestly don't know if you can safely revert to NPN25.137-33, but here's a stock NPN25.137-33 ROM to flash via fastboot (as always, back up your data and keep it off your device, as this fastboot ROM will likely wipe your device in the flash): https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I also do not know what will happen if you try to flash the NPNS25.137-35-5 update onto a reteu device (it might work, but could result in you being off the update path still).
Good luck either way.
Click to expand...
Click to collapse
Well right now I'm on a custom rom. When I'll decide to revert to stock I'll probably fastboot flash -33 build and see how it goes. Cheers.

echo92 said:
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
Code:
ui_print("Source: motorola/potter/potter:7.0/NPN25.137-33/35:user/release-keys");
ui_print("Target: motorola/potter/potter:7.0/NPN25.137-35/37:user/release-keys");
3)Seems that devices running on other networks are on the 137-33 firmware (e.g. AT&T, retus: https://forums.lenovo.com/t5/Moto-G...ce-G5-plus-stuck-on-NPN25-137-33/td-p/3738547)
4) Seems that there's 2 update paths to the May security patch:
From 137-33 > 137-35 > NPNS25.137-35-5 (this May update seems to be also the wider reported version too for US devices, probably this is the path if you are on the Verizon network)
From 137-33 > NPNS25.137-33-5
I don't know if there's any major differences between the 2 builds besides the VoLTE 911 fix, or if you were on the 137-33-5 build whether you could switch to the Verizon network and be able to make emergency calls on VoLTE (I honestly would hope that fix was rolled into both May patches though...) I'm also not sure what factors decide which update you get, besides possibly being on the Verizon network at some point?
I honestly hope at a later date, Motorola unifies the firmware (like they've done with the G4 Plus), so you can just flash one version rather than multiple different types.
Again, if someone has more information (as I don't have a G5 Plus), feel free to add/correct what I've written!
Click to expand...
Click to collapse
i also am in the U.S. on straight talk with ATT but i have NPN25.137-33 on mine and i got it in july bought it off amazon without ads 64gb version for $299 and its asking me to update to the NPNS25.137-35-5 i believe i soft bricked mine when i updated it now it goes straight to twrp recovery when booting up i used a back up copy i had the phone works fine but still goes to recovery when i shut it down how do i fix this any help will be greatly appreciated.

shaker3000 said:
Yeah, Moto G5 Plus firmwares seem to be confusing, and I agree, we don't need/want more bricks!
From what I've been reading on the Lenovo forums, as the users there are more likely to have stayed on the firmware originally issued:
1)Looks like 137-33 and 137-35 were deployed in the US (though 137-33 seems to be more widely reported in the EU).
2)137-35 seems to be an emergency patch to update 137-33 for devices on the Verizon network (to fix the 911 call bug if you were running VoLTE on Verizon) and was released on retus devices: https://forums.lenovo.com/t5/Moto-G...5-OTA-update-just-received-in-US/td-p/3730072 I had a look at the updater script for that patch (from here: https://forum.xda-developers.com/g5-plus/help/update-to-fix-volte-911-bug-t3594630 ) which appears to confirm it too:
i also am in the U.S. on straight talk with ATT but i have NPN25.137-33 on mine and i got it in july bought it off amazon without ads 64gb version for $299 and its asking me to update to the NPNS25.137-35-5 i believe i soft bricked mine when i updated it now it goes straight to twrp recovery when booting up i used a back up copy i had the phone works fine but still goes to recovery when i shut it down how do i fix this any help will be greatly appreciated.
Click to expand...
Click to collapse
Update TWRP to the latest.

H915 rooted users

Hi I'm looking for h915 users of the Canadian v20 that have successfully rooted their phones. I have many questions and concerns to ask concerning the h915.
I don't know if in 2018, will there still be h915 Users since not much developments for the h915.

Welcome to the small group of Canadian 915 users. Allow me to summarize your information quickly.
If you have received the latest security patch pushed OTA, you're unfortunately out of luck and can not safely root your V20. I unfortunately downloaded the update before I even reached home during the day I purchased mine... Boy, do I regret that terribly. I want root so terribly bad.
Secondly, if you have NOT run the latest security patch, you can flash the US 996 version and successfully achieve root without any problem. The only issues that may arise are baseband incompatibilities, but those are easily corrected by flashing back a 915baseband.zip found here in the forum.
To clarify the aforementioned security patches; In your settings -> software info ... you'll find 'Android Security Patch Level'. If it reads May 1, 2017 then you're out of luck. That bumped your software version from something like H91510d to H91510q. If I'm not mistaken, I believe '10d' was the latest software version released by LG that would allow us to cross flash software versions. Later versions are patched up and locked down.
If you're v10d then hallelujah for you brother!
*If anyone has a correction on this info, please chime in!*

murph187 said:
Welcome to the small group of Canadian 915 users. Allow me to summarize your information quickly.
If you have received the latest security patch pushed OTA, you're unfortunately out of luck and can not safely root your V20. I unfortunately downloaded the update before I even reached home during the day I purchased mine... Boy, do I regret that terribly. I want root so terribly bad.
Secondly, if you have NOT run the latest security patch, you can flash the US 996 version and successfully achieve root without any problem. The only issues that may arise are baseband incompatibilities, but those are easily corrected by flashing back a 915baseband.zip found here in the forum.
To clarify the aforementioned security patches; In your settings -> software info ... you'll find 'Android Security Patch Level'. If it reads May 1, 2017 then you're out of luck. That bumped your software version from something like H91510d to H91510q. If I'm not mistaken, I believe '10d' was the latest software version released by LG that would allow us to cross flash software versions. Later versions are patched up and locked down.
If you're v10d then hallelujah for you brother!
*If anyone has a correction on this info, please chime in!*
Click to expand...
Click to collapse
I was told that you can use lgup to downgrade to h91510e or h91510d since h91510q doesn't have anti-rollback features. So if thats the case I still have the option to start ?

darkknight200 said:
I was told that you can use lgup to downgrade to h91510e or h91510d since h91510q doesn't have anti-rollback features. So if thats the case I still have the option to start ?
Click to expand...
Click to collapse
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means ?.
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!

murph187 said:
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means ?.
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
Click to expand...
Click to collapse
I would wait for Oreo to come to v30 and g6 before getting excited. Who knows, their Oreo update suppose to come in March and still hasn't.
As for rooting, im still hesitant to pull the trigger. I still need to find out if my LTE on freedom mobile is going to be affected even after restoring the basebands.

darkknight200 said:
I would wait for Oreo to come to v30 and g6 before getting excited. Who knows, their Oreo update suppose to come in March and still hasn't.
As for rooting, im still hesitant to pull the trigger. I still need to find out if my LTE on freedom mobile is going to be affected even after restoring the basebands.
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/how-to/h915-guide-fix-lagg-signal-root-lg-v20-t3699540
Freedom/wind functioning just fine according to this thread.
As for the V30; Oreo beta release is already out to the entire country of South Korea for the V30, for a few weeks. A small select few of American users have already received this beta as well.
G6; China has already been testing 8.0.
Seeing as 8.1 is already released, it's highly presumed by a many sources that LG will likely skip 8.0 altogether and push 8.1 to our devices. 8.0 merely serves as a means to identify larger incompatibilitys/bugs.

i just rooted my h915 with this thread https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
it is much simpler process compared to the older dirtyelf method. The thread op was very helpful in getting through it.

darkknight200 said:
i just rooted my h915 with this thread https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
it is much simpler process compared to the older dirtyelf method. The thread op was very helpful in getting through it.
Click to expand...
Click to collapse
Thank you so much for this input brother. I'm strongly considering this now. How is your cell signal/LATE speeds? FM radio functioning correctly as well? Any odd vibrations upon bootup?

murph187 said:
Thank you so much for this input brother. I'm strongly considering this now. How is your cell signal/LATE speeds? FM radio functioning correctly as well? Any odd vibrations upon bootup?
Click to expand...
Click to collapse
hmm it turns out i can't connect to freedom mobile. Im working with the op to resolve the issue. I will update when i can get my signal working along with root.
update 1: so I was told to use lgup to install the us99610f kdz and factory reset and now I have signal again. Now I am gonna use the same process of the guide i used again to root the now converted device.
update 2: i have gone thru the guide again and have achieved root + freedom mobile signal on my phone.
update3: I have installed weta rom and it is working all fine with signal.

the op of that thread @dksoni411 will be including a separate guide for h915 users in that thread since it has additional steps to follow. In the meantime, i can help you if you want to get root on the h915.

murph187 said:
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means .
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
Click to expand...
Click to collapse
Could you share the link where announcement was made about releasing Android Oreo for LG V20?

dksoni411 said:
Could you share the link where announcement was made about releasing Android Oreo for LG V20?
Click to expand...
Click to collapse
i made this thread https://www.reddit.com/r/lgv20/comm..._v20_canadian_update/?st=jeh88vej&sh=d1dca001.
keep in mind i asked for info on the h915 since its been stuck on may security patch.
Lge security product is suppose to be the best accurate info compared to the customer rep of lg social media accounts.

darkknight200 said:
hmm it turns out i can't connect to freedom mobile. Im working with the op to resolve the issue. I will update when i can get my signal working along with root.
update 1: so I was told to use lgup to install the us99610f kdz and factory reset and now I have signal again. Now I am gonna use the same process of the guide i used again to root the now converted device.
update 2: i have gone thru the guide again and have achieved root + freedom mobile signal on my phone.
update3: I have installed weta rom and it is working all fine with signal.
Click to expand...
Click to collapse
Did you try installing the 915 baseband.zip from post #6 for your inability to connect to freedom?

murph187 said:
Did you try installing the 915 baseband.zip from post #6 for your inability to connect to freedom?
Click to expand...
Click to collapse
no i used patched lgup to flash us99610f kdz to get working signal and then did the whole guide again to get a working signal rooted h915 phone. Afterwards no need to do any baseband installing as the signal is strong as how it was on normal h915.

Wifi calling working on freedom after root?

EnIXmA said:
Wifi calling working on freedom after root?
Click to expand...
Click to collapse
No wifi calling.

US996 Firmware

Can anyone tell me what the most current version in for my US Factory unlocked US996 is? Thanks for your help

Officially just 10n which iirc has the November 2017 security patch. Unofficially it can also use the us Cellular us996 firmware (through flashable zip,, or lgup with kdz) which is on the February 2018 security patch. Or if you want to absolutely abandon stock and get further into rooting and roms based you could run LineageOS which is on the March security patch but the second screen doesn't work and neither does HiFi mode.

Phoenix591 said:
Officially just 10n which iirc has the November 2017 security patch. Unofficially it can also use the us Cellular us996 firmware (through flashable zip,, or lgup with kdz) which is on the February 2018 security patch. Or if you want to absolutely abandon stock and get further into rooting and roms based you could run LineageOS which is on the March security patch but the second screen doesn't work and neither does HiFi mode.
Click to expand...
Click to collapse
Thanks Phoenix, I flashed 10N, build # NRD90M with Nov 6th security patch some months ago right after getting the phone. This must be US Cellular firmware and I didn't know it of course. Not carrying the phone around these days but I do still like it and use it as my music player. When (if) Oreo is ever released I'll start using it more again. I have hope... for LG to not upgrade a flagship device at least once is unimaginable (I think, lol). Thanks again

H910 not updating OTG/PC Suite

Hi There !
I have recently bought LG V20 H910. It is on android 7.0 and its further details are as below:
Android security patch level: December 1, 2016
Build number: NRD90M
Software version: H91010i
Whenever i try to update the android, it says that there is no further update available. I tried both OTG as well as LG PC suite methods. When i tried searching for security patches on LG site, i got this info that latest patch is from March 2018.
I wanted to know how can i update my phone and why it says that there is no update available, when there is update available as per this LG site
My device is not rooted. I tried to root it earlier to install lineage OS (by following the guide). I am not a tech savvy kind of person at all.
Please help me with this.
Regards
Awais Javaid.

awaisagha said:
Hi There !
I have recently bought LG V20 H910. It is on android 7.0 and its further details are as below:
Android security patch level: December 1, 2016
Build number: NRD90M
Software version: H91010i
Whenever i try to update the android, it says that there is no further update available. I tried both OTG as well as LG PC suite methods. When i tried searching for security patches on LG site, i got this info that latest patch is from March 2018.
I wanted to know how can i update my phone and why it says that there is no update available, when there is update available as per this LG site
My device is not rooted. I tried to root it earlier to install lineage OS (by following the guide). I am not a tech savvy kind of person at all.
Please help me with this.
Regards
Awais Javaid.
Click to expand...
Click to collapse
Sounds like your previous attempt at root screwed up automatic Ota from your carrier. Your going to need to root and twrp to flash an updated stock rom
Sent from my LG-H910 using XDA Labs

awaisagha said:
Hi There !
I have recently bought LG V20 H910. It is on android 7.0 and its further details are as below:
Android security patch level: December 1, 2016
Build number: NRD90M
Software version: H91010i
Whenever i try to update the android, it says that there is no further update available. I tried both OTG as well as LG PC suite methods. When i tried searching for security patches on LG site, i got this info that latest patch is from March 2018.
I wanted to know how can i update my phone and why it says that there is no update available, when there is update available as per this LG site
My device is not rooted. I tried to root it earlier to install lineage OS (by following the guide). I am not a tech savvy kind of person at all.
Please help me with this.
Regards
Awais Javaid.
Click to expand...
Click to collapse
Looks like you've the att model, are you actually on ATT? I've seen reports that if the att model doesnt have an ATT sim it wont find updates.

cnjax said:
Sounds like your previous attempt at root screwed up automatic Ota from your carrier. Your going to need to root and twrp to flash an updated stock rom
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Well it seems so. I tried rooting it with kingoroot and it failed. Then i searched online for rooting solution and came to know that v20 cannot be rooted by these software because the bootloader is locked.. It needs another method (told in forums). Well i didn't try them.
I need some further help in this regards. I have few questions. I hope you can answer them.
1. If i unlock the bootloader and install twrp and then install the stock rom, CAN I INSTALL ANY stock rom, for example, stock rom of international model instead of at&t version?
2. I am using h910 but not with at&t sim. I am on other network. Will installing with official rom (other than at&t version), keep the gsm working>?

awaisagha said:
Well it seems so. I tried rooting it with kingoroot and it failed. Then i searched online for rooting solution and came to know that v20 cannot be rooted by these software because the bootloader is locked.. It needs another method (told in forums). Well i didn't try them.
I need some further help in this regards. I have few questions. I hope you can answer them.
1. If i unlock the bootloader and install twrp and then install the stock rom, CAN I INSTALL ANY stock rom, for example, stock rom of international model instead of at&t version?
2. I am using h910 but not with at&t sim. I am on other network. Will installing with official rom (other than at&t version), keep the gsm working>?
Click to expand...
Click to collapse
You could possibly flash the US996 which is the unlocked version, as far as updates you'll have to check and see if there's updates for it from LG, but the big concern would be determining what bands are available with that variant to see if they are compatible with your carrier, you can also check this forum and see if there's updated 996 roms that you could flash to get the latest security patches. But as the previous poster stated as long as you are on 910 rom and using another carrier's sim you'll never get an update from AT&T
Sent from my LG-H910 using XDA Labs

No security patches since January '17

Hello everyone,
I read several post about updating to Android 8.1 on the Moto G5 plus, but I'm still on Android 7 with Security Patch from January 2017. I never had any OTA updates. When I manually do a check, there are no updates available.
Here is a screenshot:
I'm also unable to update to 8.1, but I think the problem is that I first needs the security patches, before updating to 8.1 will work.
It is no custom ROM. What can I do to get the security patches?

Screenshot unreadable, can you give software channel and build, both found in about phone section in settings.
Thanks

It is a thumbnail to the bigger one. Here is the link: https://tweakers.net/ext/f/pYZxVQJCcXqbkf5Q4zS5GXcq/full.png

I have no idea why your phone is not on the latest European software which is currently at NPNS137-93-14, take it your in Europe with a mainstream phone provider.
You could try fastbooting update or maybe using motorola update tool, sorry neither of which I have used, so cannot be of any help there.

OK, thanks for you reply anyway!
Is it possible to grap the OTA updates to NPNS137-93-14 manually?

theovds said:
OK, thanks for you reply anyway!
Is it possible to grap the OTA updates to NPNS137-93-14 manually?
Click to expand...
Click to collapse
I was able to grab the OTA with this:
https://motoota.lolinet.com
It has to run on a PC browser and you have to use the lines like the ones from a getprop command, for example
Moto G (5)
Blur_Version.25.226.11.potter.retail.en.US
RETEU
Sent from my Moto G5 Plus using XDA Labs