Related
Simple answer - NO.
When a new software release is made for an OS, all the developers would have done is test it on a very few devices within the developers and then roll it out to testers. And after analyzing the bugs identified from these testers, the developers sit on fixing it and finally come up with a release. Now would this release be bug-less? Absolutely not! Remember, its only been tested amongst a very few number of people and the rolling out happens to thousands residing in different parts of the world. If you think about it, what these updates are gonna deal with is a varied number of users, different carriers, sim make etc etc.
Take for example, for Indian users, the 4.4.2 update has been rolled out for quite a while. Lots of bugs were identified since then and the forum managers have been collecting data from the subscribers for quite a while now (Almost 4 months). Still the fix has not happened. And now 4.4.4 is out and issues persist.
I hvae been using 4.3, 4.4.2, then CM11, Mokee ROM etc etc, and now Im finally back to stock 4.3, coz thats the most stable version. So if you are someone who is interested in trying out new releases, please go ahead, but if you are someone who needs a stable ROM with no signal drop issues, please stick to 4.3.
totally disagree. I have european version Moto G with stock 4.4.2 and everything is working perfeclty. Try to wipe you Moto or flash any other rom.
seems like pebkac not buggy firmware . otherwise every single guy would be facing same problems and that's not happening .
ovitz said:
totally disagree. I have european version Moto G with stock 4.4.2 and everything is working perfeclty. Try to wipe you Moto or flash any other rom.
Click to expand...
Click to collapse
Just to clarify, did you receive an update package sometime after the primary update?
4.4.3 works fine on my US GSM moto G. But it might be different for others.
Also, add a warning to the OP that if you're already on 4.4.3+, you can't downgrade anymore. Motoboot from 4.4.3+ doesn't seem to like downgrading anymore, unfortunately.
4.2.2 works great, no signal drops or anything. Waiting for eupean 4.4.4. :good:
Sent from my XT1032 using Tapatalk
Question is whether downgrading is possible from 4.4.4 ?
I totally agree to ovitz. Updates are supposed to fix issues with older versions of the software. My moto came with 4.4.2 and i never had issues with signal drops. I am from India. Btw it's always better to reset phone after the update.
I agree with you OP on some extent. I also recently downgraded to 4.3 from 4.4.2 just for the lulz, because I was getting "image is too large" error but surprisingly today the flashing was successful. The battery timing has improved, dialer app is cooler than that of the 4.4.2. I'm finding these changes quite interesting because I didn't stay with 4.3 for too long; my Moto G received the KitKat update the moment I powered it on for the first time.
techpick said:
Simple answer - NO.
When a new software release is made for an OS, all the developers would have done is test it on a very few devices within the developers and then roll it out to testers. And after analyzing the bugs identified from these testers, the developers sit on fixing it and finally come up with a release. Now would this release be bug-less? Absolutely not! Remember, its only been tested amongst a very few number of people and the rolling out happens to thousands residing in different parts of the world. If you think about it, what these updates are gonna deal with is a varied number of users, different carriers, sim make etc etc.
Take for example, for Indian users, the 4.4.2 update has been rolled out for quite a while. Lots of bugs were identified since then and the forum managers have been collecting data from the subscribers for quite a while now (Almost 4 months). Still the fix has not happened. And now 4.4.4 is out and issues persist.
I hvae been using 4.3, 4.4.2, then CM11, Mokee ROM etc etc, and now Im finally back to stock 4.3, coz thats the most stable version. So if you are someone who is interested in trying out new releases, please go ahead, but if you are someone who needs a stable ROM with no signal drop issues, please stick to 4.3.
Click to expand...
Click to collapse
While I do agree with you for most of what you said, not everyone has bugs or issues with their phones on 4.4.3/4.4.4 upgrade. I myself has had one bug that came with the phone since 4.3 and it's worst now on 4.4.3 and ironically, I've gotten all the bugs on the 4.4.3 that others were getting on 4.4.2. I ended up putting on CM11 because it was getting to me.
P.S. It's impossible to downgrade from 4.4.3/4.4.4. I would love to downgrade back to 4.3. Never got the chance to see how it behaved on my phone because I updated to 4.4.2 the moment I booted for the first time.
Did I mention the "Sign in to WiFi" error on the 4.4.2? That's annoying as hell.
usertag said:
Question is whether downgrading is possible from 4.4.4 ?
Click to expand...
Click to collapse
It is possible!, download the 4.4 official ROM and do a fastboot and install all the IMG files.
Thats how I did it,
chrisdf said:
It is possible!, download the 4.4 official ROM and do a fastboot and install all the IMG files.
Thats how I did it,
Click to expand...
Click to collapse
but you can't downgrade the bootloader, so didn't you get any errors?
Not that guy, Don't touch the motoboot and you should be fine
There's no point of updating your phone unless youare receiving it over OTA. Doing it manually is risky. The only thing that you'll get is new AOSP dialer and few security fixes. There's no reward..no improvement in performance as well as in camera quality. People are reporting bugs all over the globe and they desperatly want to switch back to 4.4.2. Few have them are also facing downgrading issues.
And you want to go through all this for just a minor update? Android L could be a good reason as it is worth updating even after bugs. But a minor update is definitely not.
If some one will ask me which is best ROM for my moto g? I would say Stock 4.4.2. I tried all custom ROMs but no one was as smooth as stock 4.4.2.
Consequences be damn'ed.
Simple answer- yeah, well, that's just like your opinion man.
Indian user. Unlocker my bootloader, Converted to GPE while on 4.4.2. The GpE move was made partly because I had jo desire nor the use if a second sim and mostly because I wanted a clean OS. Period.
Got instant OTA update to 4.4.4 to the day it was pushed.
No issues so far, None in fact and it's been over a week or thereabouts(I admit to the likelihood of me being an isolated case)
Lastly, to each his own.
Android is meant to be taken care of AS WELL tinker every single detail or option if you have the cojones for it. Ciao.
:thumbup:
Sent from my XT1032 using XDA Free mobile app
I have just upgrade to 4.4.4 XT1033 (Malaysian), noted the missing 2 empty simcard icone and new rather flat dialer! nothing much has changed and certainly hasn't noticed any issue mentioned herein!
If one were to go by op opinion then they would be using 4.3 for the rest of the devices life ! I wonder what his comment would be once L comes to our device.
I have to disagree the OP as an xt1033 owner since march 2014.
Android 4.4.4 OTA for moto g helps fix various sw issues and increased performance,new baseband to aid the radio issues. Media playback is improved. The device is more of a swiss-tool now.
GPe edition of Moto G running KTU84P.M003 like a dream and eats more battery,too. I wish i could have flashed it earlier.
Semseddin said:
GPe edition of Moto G running KTU84P.M003 like a dream and eats more battery,too. I wish i could have flashed it earlier.
Click to expand...
Click to collapse
Just curious, if it eats more battery how come you call it a dream?
Apologies if this has been asked before or if this is a stupid question, but it appears there are no stock images of the XT1687 (US unlocked) version of this phone?
This makes the idea of unlocking the bootloader and trying out custom ROMs kinda iffy if there's no way to easily return to stock. My Nexus, HTC and Samsung phones, for example, could easily be restored to the stock OS with a computer. Only thing I can find for this phone is OTA updates that can be sideloaded... nothing that would enable me to return to stock everything (recovery, OS, etc.) easily in the event that I would want to.
Is there something I'm missing that's different with Motorola phones?
Yes, you can easily go back to stock, I've done it a few times already. You can find threads & info here on it if you search around. Check in settings to see which build you have and the official firmware for Moto G5 Plus (aka potter) is located here:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Some have received OTA upgrades but so far Moto hasn't officially posted those, so the above are what you originally got on your phone and any newer ones will appear there when available.
Dahenjo said:
Yes, you can easily go back to stock, I've done it a few times already. You can find threads & info here on it if you search around. Check in settings to see which build you have and the official firmware for Moto G5 Plus (aka potter) is located here:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Some have received OTA upgrades but so far Moto hasn't officially posted those, so the above are what you originally got on your phone and any newer ones will appear there when available.
Click to expand...
Click to collapse
I don't think any XT1687s have gotten updates to .67, and in fact when I flashed .67 to my phone VoLTE and T-Mobile wifi calling stopped working even though the software channel still says retus...I imagine there are updated binaries for said functions that is why we in the US haven't got the update
bakedpatato said:
I don't think any XT1687s have gotten updates to .67, and in fact when I flashed .67 to my phone VoLTE and T-Mobile wifi calling stopped working even though the software channel still says retus...I imagine there are updated binaries for said functions that is why we in the US haven't got the update
Click to expand...
Click to collapse
I'm running the debloated/deodexed .67-based stock ROM and mine also still shows retus in settings. Everything works identically well to my "assigned" .33 from before, but I'm on AT&T so don't use VoLTE.
Return to stock
I have a moto g5 plus xt1687, where can I download a stock rom. I am currently rooted and do not have a backup to the original rom. What are my options? Thanks.
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.
I'm trying to wrap my head around all this, but my head is spinning. In December I was looking to get my S7 flat to 7.0 rooted. I discovered that root can only be achieved with eng kernel and that has its drawbacks. I decided I don't need/want root at that cost of stability, performance and battery life. Somehow I settled on installing a "U" variant that seemed to work well with less Verizon bloat. I couldn't get the S Health app and monitors on the back of the phone working, but I figured I could live with that. Recently I tried casting my phone to a Amazon Fire Stick and discovered the "Smart View" button is missing and I couldn't figure out how to get it back, so I might've lost that too. I also discovered in the past nine months Oreo is out with additional features and I figure if I'm going to go through the hassle of reinstalling, I might as well upgrade.
So, I hear root with Oreo is better than it's been, but not perfect, so I'l like to upgrade to unrooted oreo, either stock or debloated (if such a version exists without tradeoffs). Is there a certain version I'm supposed to go to so there's some flexibility in reinstalling the OS? Like I know sometimes versions of software are released that upgrade little, but patch exploits.
Also, if I do get whatever version of Oreo installed, do I then ignore OTA updates going forward? Is there any advantage to that?
And I can use the mobile hotspot feature. I don't think I have any special plan to accommodate that, nor do I have an unlimited plan (with Verizon). Is that intended, or is that from the "U" variant. Would I lose that?
My phone's info is below, if anyone can decipher what I did:
Model #: SM-G930U
Android Version: 7.0
Baseband Version: G930UUEU4BQE2
Kernel Version: 3.18.31
Build #: NRD90M.G930UUEU4BQE2
I apologize, I know my nomenclature isn't up to snuff. I realize that this stuff isn't for the casual user, at least on this phone. It's very hard to figure out what's current if you're not in the loop.
Thank you for any help you can offer.
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
djh816 said:
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
Click to expand...
Click to collapse
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Umbra. said:
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Click to expand...
Click to collapse
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
djh816 said:
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
Click to expand...
Click to collapse
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Umbra. said:
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Click to expand...
Click to collapse
Woo, welcome back to the walled garden lol.. BTW I found in the themes/lockscreen app (can't recall where) they had the old lockscreen font I preferred as a clock option
Hello, I apologize for the noobish question in advance.
I don't have an LG V20 myself, my friend has one and wants to unlock the bootloader. Normally Verizon devices are NOT bootloader unlockable but when I looked on this site (could be fake but who knows till they ask) it appears the Verizon variant of the LG V20 is in fact unlockable. As someone who is unfortunately very familiar with Verizon variants of phones, this is unusual news to me. Usually Verizon locks their stuff down with no hope of unlocking.
Anyway, just wanted to ask if that site's guide was correct for how to unlock the bootloader on the LG VS995 variant from Verizon. His Android version is 8.0.0, build number OPR1.170623.032. Software version VS99520c. Security patch October 1st, 2018. Security software version MDF v2.0 Release 4. Do I need to downgrade the firmware at all or can I just do it?
Any help would be greatly appreciated. He wants LineageOS on that thing (to get the latest security patches) and I don't blame him.
It's not that easy unfortunately.
The first thing that would need to be done is to revert the phone back to Nougat 12a or 13a. I have not done this part (both my VS995 were on some version of Nogat, I reverted the version to 12a by flashing the kdz), but guides are available to revert to Nogat from Oreo on XDA in the
https://forum.xda-developers.com/v20/
Section.
Then what is on that site would most likely work. I would suggest using this guide instead as I have rooted two VS995 with it. It is less confusing that the Dirty Santa or Dirty Elf guides IMHO, but it is later and builds on those guides.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278.
Good luck, although if you plan to use the phone on Verizon, it's only a matter of time before a stock ROM with VoLTE is a requirement for using the phone. I guess he can switch back at that point (or go to one of the GSM providers).
Dread1111 said:
The first thing that would need to be done is to revert the phone back to Nougat 12a or 13a. I have not done this part (both my VS995 were on some version of Nogat, I reverted the version to 12a by flashing the kdz), but guides are available to revert to Nogat from Oreo on XDA in the
https://forum.xda-developers.com/v20/
Section.
Then what is on that site would most likely work. I would suggest using this guide instead as I have rooted two VS995 with it. It is less confusing that the Dirty Santa or Dirty Elf guides IMHO, but it is later and builds on those guides.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278.
Good luck, although if you plan to use the phone on Verizon, it's only a matter of time before a stock ROM with VoLTE is a requirement for using the phone. I guess he can switch back at that point (or go to one of the GSM providers).
Click to expand...
Click to collapse
Just to clarify this isn't just a root this is a full on bootloader unlock right? I assume it is because TWRP gets flashed, but then again there were custom recoveries in the past that were just Safestrap and weren't full on recoveries (still locked BLs). Because the end goal here is to install Lineage or something like that to the phone. I'm not interested in just rooting stock.
Also, wasn't aware about the stock ROM requirement thing for Verizon, I thought it was only VoLTE they were implementing. That's a bummer. Thanks for the heads up