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.
My Moto G5 Plus is telling me that my software is up to date, yet it's still running Android 7.0, but more importantly the security patch level is 1/1/17. I don't know about major OS updates, but there MUST be at least some updates out there that I'm not getting. Can someone link me to somewhere where I can find a .zip files for all OTA updates, so I can just flash the update and then flash Magisk again to retain root? Thanks!
You are probably not receiving OTA updates since you've rooted your phone, right? There was no major updates but there was few security patches this year. Which model exactly you have? That's gonna help in providing you correct links...
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
nlinecomputers said:
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
Click to expand...
Click to collapse
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
acejavelin said:
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
Click to expand...
Click to collapse
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
nlinecomputers said:
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
Click to expand...
Click to collapse
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
acejavelin said:
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
Click to expand...
Click to collapse
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
nlinecomputers said:
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
Click to expand...
Click to collapse
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
FamilyGuy0395 said:
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
Click to expand...
Click to collapse
Sort of... OTA files can only be flashed on a pure stock system, no root, no TWRP, no Xposed, nothing changed in system, no removed packages, etc. If the OTA script even detects that /system was ever mounted R/W it can fail (I don't know if Moto goes that far).
To flash an OTA you must restore your stock ROM completely (/system, /boot, and any other system level partitions), and restore stock recovery, and all versions must match or the OTA script will crap out with an error.
The OTA files are out there, on this forum in various threads... you can find them along with instructions on how to apply them to rooted and stock systems.
acejavelin said:
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
Click to expand...
Click to collapse
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
nlinecomputers said:
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
Click to expand...
Click to collapse
Oh yeah... Moto's level of doing what the carriers "recommend" or whatever you want to call it, is ridiculous lately.
Good example is Nougat for the Moto X Pure Edition, if you are on Sprint or US Cellular you got it 2 months ago, but Verizon, AT&T, and T-Mobile users still haven't seen it. Except many users have figured it out, pop in a Boost Mobile SIM (not even activated) and it will grab the update almost immediately, let it apply, then swap your original SIM back in and enjoy some Nougat goodness. However that device never had a specific version for a certain carrier. Still today probably 80% of users of that FLAGSHIP device still haven't gotten an update that we know was completed in June/July, due to "partner approvals" or some such BS.
All these updates still come directly from Moto and their servers, but they are doing what the carriers tell them and only allowing it to certain devices... This has vaguely been admitted to by the mods on the official Lenovo support forums.
Honestly, many smaller brands with a history of poor update frequency get better update support than Moto's these days... My son's Axon 7 Mini already has 7.1.1 with the September update for BlueBourne, he got it the third week of September, and gets on every 3 months like clockwork. My faith in Moto is diminishing quickly, I gave them the benefit of the doubt on my last two (Moto X Pure Edition and Moto G 2015) because they were kind of transitional device during the Google-Lenovo switch over, and although my Moto G5 Plus is supported a little better I believe it is just because it is newer and not because Moto got better.
Chances this will be last Moto device? Let's just say this could be my last Moto device, and I have been a big Motorola fan for many years.
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Can anyone link me where to find OTA updates for Moto G5 Plus and, if necessary, instructions? I don't see why the instructions would be any different from the OnePlus 5, other than Motorola making it harder on purpose.
FamilyGuy0395 said:
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Click to expand...
Click to collapse
Never said it was true for every phone or manufacturer, but that is the way it is with Moto devices... You cannot flash an OTA with TWRP, the script checks (among other things) the recovery and will fail if it doesn't have the correct signature, same with the modems, bootloader, partition table, and things in /system. Moto OTA updates are VERY picky and will fail at the drop of a hat on a device that is not purely stock.
The only work around, that works in SOME cases with Moto devices, is using FlashFire by Chainfire, but that is hit and miss, depends on what is updated.
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Karlinski said:
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Click to expand...
Click to collapse
Do you have a link to this thread? I am curious how the modems, partition table, and bootloader updates are handled since TWRP doesn't have the correct signature to write to these partitions. I can see where it could maybe update the boot and system partitions if they were extracted from the ROM, even if they are differential deltas, but my guess is that a "TWRP flashable" OTA is mearly an extract of a blank device's boot and system partition or just he changes, and packed into an OpenRecovery script, and not the "real" OTA file.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Karlinski said:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Q9Nap said:
Do NOT attempt to apply standard OTAs over these builds; they will fail.
Click to expand...
Click to collapse
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
acejavelin said:
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
Click to expand...
Click to collapse
The TWRP flashable stock builds DO upgrade the modem.
As stated in the OP, the only partitions NOT upgraded are gpt and bootloader.
I didn't omit these partitions because they can't be written; I omitted them to prevent potential issues for people who really don't know what they're doing.
Disabling dm-verity is required due to some partitions unavoidably losing their oem signatures during the conversion process.
Disabling force encryption is practically required, as TWRP seems buggy with it enabled.
The intended purpose of these builds is to provide a dead simple (and safe) way for users to return to stock.
I have linked useful tools at the bottom of the OP for those interested in making their own modifications to these stock builds.
Hope this helps :good:
Q9Nap said:
Hope this helps :good:
Click to expand...
Click to collapse
It does actually, thank you... Obviously I have a lot to learn about the differences between current devices and older Moto devices I am used to working.
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.
So a user in Brazil captured a snapshot of the official OTA soak test and it's been making its rounds on Twitter. Users in Brazil, Mexico, and India can install this without problems but me (USA) and another Twitter user (Germany) are unable to install it. It cannot find the update for some reason. (YES it is in the root of internal storage, YES Motorola update has storage permission, YES I restarted my phone and redownloaded the file many times)
I am not willing to root but I am curious if there is any way I can get this OTA version to work on the USA model of the G5+.
If anyone can help me get Oreo on my phone without root I'd greatly appreciate it! Thank you!
-Slim
slim_radio said:
So a user in Brazil captured a snapshot of the official OTA soak test and it's been making its rounds on Twitter. Users in Brazil, Mexico, and India can install this without problems but me (USA) and another Twitter user (Germany) are unable to install it. It cannot find the update for some reason. (YES it is in the root of internal storage, YES Motorola update has storage permission, YES I restarted my phone and redownloaded the file many times)
I am not willing to root but I am curious if there is any way I can get this OTA version to work on the USA model of the G5+.
If anyone can help me get Oreo on my phone without root I'd greatly appreciate it! Thank you!
-Slim
Click to expand...
Click to collapse
You have to be on 137-92-14 to update (this is the software for India and Brazil).
As you're from US you should be on 137-93-14 or earlier. So there's no way to update your device to Oreo without rooting until the Oreo OTA for reteu/retus get's leaked.
Sent from my Moto G5 Plus using XDA Labs
Hey guys,
I've been digging all over the place to try to find H910A 10U or 10V (last versions release for Nougat) firmware so I can extract the modems from it and pair it with Lineage OS 17.1 but I can't find this for the life of me anywhere. 10U and 10V have the same modems but just different security updates included in the package, so either one is the same as far as what I'm trying to use them for.
I've downloaded SuperROM 4.0 for the V20 as well as Alpha-Omega 4.0 and neither one includes firmware dumps in them.
I found a link where forum member toastyp had created a flashable zip of just that firmware, but his link to the file up on google docs is no longer active.
Here is the thread i'm referring to:
H910v10u Files
runningnak3d and dudeawsome here are the h910 10u files! ATT finally let me update this morning. Let me know if I missed anything. https://drive.google.com/open?id=1gm823SV5rVSUOEOErbVqWYnBX3sd2RqC I'm adding the h910 v10v files here as well...
forum.xda-developers.com
If anyone has h91010U or 10V firmware and could share that, it would be very much appreciated!
Download AT&T LG V20 to H91010u (March 2018 Security Patch)
AT&T LG V20 started receiving the latest Android Security Patch level for March Month 2018. The update bumps the build number from H91010r to H91010u. Along with March 2018 Security patch, the update also comes with regular bug fixes and improvement. Along with March 2018 Security Patch, AT&T...
www.getdroidtips.com
Try his site hope it helps.
Found it my saved android folders.
H91810u.zip - Shared with pCloud
Keep, share and access your files whenever you need from wherever you are. Create a free pCloud account and make your life easier.
u.pcloud.link
SoberD said:
H91810u.zip - Shared with pCloud
Keep, share and access your files whenever you need from wherever you are. Create a free pCloud account and make your life easier.
u.pcloud.link
Click to expand...
Click to collapse
Thanks but that appears to be for the H918, not the H910. Using this on an H910 will hard brick it.
partyman66 said:
Thanks but that appears to be for the H918, not the H910. Using this on an H910 will hard brick it.
Click to expand...
Click to collapse
OK I see my bad!