Related
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.
Hey, can anyone provide and confirm which version of the stock firmware fits EU devices best? I bought used device with custom rom on it, and I'm curious which version should be base for my EU (german) device to get legit OTAs and security updates for my region? I'm a bit confused, because I couldn't find any proper adnotation for each firmware out there.
In other words, which stock rom versions will be suitable for European retEU XT1685 Moto G5 Plus? I don't want to mess something up if some stock firmwares are not meant to be flashed on EU device.
Please cleanse my concerns.
Cheers!
Mine is running NPNS25.137-33-5 also on reteu
dirkie171980 said:
Mine is running NPNS25.137-33-5 also on reteu
Click to expand...
Click to collapse
I see, so you started from flat NPNS25.137-33? How about the -67 version on EU devices, as it fixes some issues ie with camera recording?
Thats only on retin, this is the latest on reteu.
Hmm I installed myself -35 version before, in settings i had retEU, but couldn't get any ota updates and was on january securities.
Up
I'm seeing NPJS25.93-14-8 firmware floating around. I'm using g4 Plus xt1644 (us) NPJ25.93-14.5, am I on the newest or is 14-8 the newest? Or does it even apply to me? Thanks
ice711 said:
I'm seeing NPJS25.93-14-8 firmware floating around. I'm using g4 Plus xt1644 (us) NPJ25.93-14.5, am I on the newest or is 14-8 the newest? Or does it even apply to me? Thanks
Click to expand...
Click to collapse
NPJS25.93-14-8 and NPJS25.93-14-5 are IMO most likely the same. 14-8 is for unlocked retail phones, 14-5 for Amazon phones.
thorin0815 said:
NPJS25.93-14-8 and NPJS25.93-14-5 are IMO most likely the same. 14-8 is for unlocked retail phones, 14-5 for Amazon phones.
Click to expand...
Click to collapse
Thanks for the reply!!
NPJ25.93-14.5, as far as I know, is also the latest update for US devices ( like yours, on retus software channel). As mentioned above, there's also a separate version (same build) for Amazon devices.
The NPJ25.93-14.5 has the same bootloader as the retail June update (NPJS25.93-14-8), though it looks like the baseband might have some emergency calling patches
https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-moto-g4-update-t3665900
If you need the fastboot ROM for NPJ25.93-14.5, retail is https://www.androidfilehost.com/?fid=673368273298984458
Amazon is here: https://www.androidfilehost.com/?fid=817550096634798183
Hi guys,
This is the last version i have on my phone h870ds and havent received an update since november, but i've seen in other forums security updates in january and march, does anyone else have the same issue? Is this a region thing?
you not alone. TWN is the same version V10M - thought it says 1st October for me. Pretty much forgotten regions I think!
Just flash another Region, if you're able to handle this. I did it also by myself. I got the TWN v10m version like you, now i have v10v sea global 1st March Patch. LG left the China Market, maybe also the Updates.
ric84 said:
Just flash another Region, if you're able to handle this. I did it also by myself. I got the TWN v10m version like you, now i have v10v sea global 1st March Patch. LG left the China Market, maybe also the Updates.
Click to expand...
Click to collapse
I have considered that - just keeping an eye out if/when OREO gets released for the TWN region then saves me messing around flashing other regions. Ain't you might as well flash with a KOREAN version then you should get OREO straight away? Unless the SEA is KOREAN - if thats the case, haven't you got an opportunity to update to OREO?
Im on the same boat... SEA is south east asia, wich means Indonesia, Malasya, Singapur, Vietnam, Thailand among others, its a kinda big market to be left alone all things consider... Someone should ask LG about it, since my phone is from that region, and my LG support on my country at least sucks... otherwise i would do it myself...
Edit: From a quick search on lg firmwares site i found that many other LG products got updates on firmware for SEA versions as old as this past month.. so i dont think it stopped updating phones...
same here! just wating for oreo to flash another region...
So we should still receive Oreo even if the security patches stopped?
aaramos28 said:
So we should still receive Oreo even if the security patches stopped?
Click to expand...
Click to collapse
not necessary, but when Oreo get released, you may choose region which get an update first
LazyG said:
not necessary, but when Oreo get released, you may choose region which get an update first
Click to expand...
Click to collapse
And if we flash to another region do we still receive OTA's or we need to keep flashing firmwares everytime?
My G6 is from the HKG region, is there a way to flash another region?
both HKG and SEA can get Oreo update now via LG bridge
My F5321 from Malaysia isn't receiving any of the new updates. Last one was 34.4.A.2.32.
Could anyone explain why?
You can check xpericheck.com if there's a newer version,but there's a good chance there isn't one. I'm stuck on 34.4.A.2.50 on the Central Europe version for example, the newest one is .85
Matej101 said:
You can check xpericheck.com if there's a newer version,but there's a good chance there isn't one. I'm stuck on 34.4.A.2.50 on the Central Europe version for example, the newest one is .85
Click to expand...
Click to collapse
Customised MY isn't even listed. :/
What now? Unlocking bootloader if you want latest security patches?
Is there another firmware variant that would be suitable for your location? There may be less difference between the variants than you might expect.
pseudonym58 said:
Is there another firmware variant that would be suitable for your location? There may be less difference between the variants than you might expect.
Click to expand...
Click to collapse
Can you just flash the firmware straight from xperifirm, or do you need an unlocked bootloader or sth?
Bro do not update it to 8.0 oreo is wery bad I swear im back to stock Nougat again
Qendra said:
Bro do not update it to 8.0 oreo is wery bad I swear im back to stock Nougat again
Click to expand...
Click to collapse
true
Matej101 said:
You can check xpericheck.com if there's a newer version,but there's a good chance there isn't one. I'm stuck on 34.4.A.2.50 on the Central Europe version for example, the newest one is .85
Click to expand...
Click to collapse
me too.. central europe and stuck on 34.4.A.2.50, I don't understand why
andy356 said:
My F5321 from Malaysia isn't receiving any of the new updates. Last one was 34.4.A.2.32.
Could anyone explain why?
Click to expand...
Click to collapse
According to xpericheck, singapore region firmware is also stuck in March. I guess both MY and SG are using the sme FW. I think you cn flsh other region FW without unlocking Bootloader.
Is there a way to flash security updates only, without upgrading to oreo?
trewelu said:
According to xpericheck, singapore region firmware is also stuck in March. I guess both MY and SG are using the sme FW. I think you cn flsh other region FW without unlocking Bootloader.
Click to expand...
Click to collapse
Can anyone please confirm this? I'll unlock the bootloader if I have to, but it would be great if it is not needed.
andy356 said:
Can anyone please confirm this? I'll unlock the bootloader if I have to, but it would be great if it is not needed.
Click to expand...
Click to collapse
I'm in USA, and I've flashed f'd from at least 10 different countries and never seen any affect on the phone operation.
andy356 said:
Can anyone please confirm this? I'll unlock the bootloader if I have to, but it would be great if it is not needed.
Click to expand...
Click to collapse
If you want to retain the fingerprint sensor operation, don't flash to US. People here have in the past recommended either DE or UK, as they tend to be updated promptly. No unlocking of bootloader needed.
Okay guys. I'm ready to flash a new firmware, probably Customised UK. Is the guide on xperiablog up to date and accurate? Also, there is a flashtool by Androxyde on flashtool dot net, but there is also a flashtool on Sony Developer World. Which one should I use?
There is only one xperifirm so that's unambiguous, at least.
Edit: also, it doesn't affect user data or the OS in general, does it?
I can only speak from personal experience with the Androxyde flashtool. I've never tried (nor even known about) the Sony flash tool. In my experience, if you don't make any changes to the default settings, the existing user data is carried over into the newly installed firmware. I'm assuming here that you're flashing from one variant of Android 8.0 to another, not from Android 7 to 8, etc.
BTW, I would always advise backing up your data first, of course. If, for some reason, you are dissatisfied with the result, you can normally get a factory installation of your currently-installed firmware by using software restore from SONY (as part of Xperia Companion).
@pseudonym58 Thanks. Is the guide on Xperia blog the one to follow or is there a better one out there?
I don't recall which guide I used. It basically runs like this:
Run Xperiafirm from within flashtool; it will refresh available software. Choose particular phone model and download desired firmware. Back in flashtool proper, connect phone in flash mode. Select downloaded firmware, which is unpacked and prepared for flashing. As I mentioned above, you should not need to make any configuration changes to the default. Flashing can now begin (it might seem to pause temporarily from time to time but don't cancel process).
Don't worry about warnings of missing elements; I have never had a flashing procedure fail as a result of a claimed missing component.
This is just a general procedure; perhaps someone else can recommend the best full tutorial.
Ok so CE1 got the newest (.107) update right now so it can probably be used too.