So I just bought an LG V20 US996 (not US Cellular version). I have TWRP installed, and then I installed LineageOS nightly 20170825 and found that the battery meter is stuck at 50% regardless of charge, but more importantly, the touch screen no longer works. Same thing with nightly 20170901. However, after downloading all the nightlies and trying them, I found that the July ones work just fine (ie 20170728, 20170714, and 20170707). Someone on reddit suggested it might be an issue of not having the latest firmware. I did find here at lg-firmwares.com/lg-us996-firmwares that lists the US996 kdz files. It looks like the US Cellular version is more updated than the regular USA version. Is it safe to flash a US Cellular version onto a not US Celllular version even though they're both US996 ?
There are several things to take into account.
First, is you boot loader unlocked using the unlock.bin, or are you using the engineering aboot?
Nevermind. Someone already posted a regression ticket for this. It should be fixed eventually. The person who did it flashed a different kernel and it worked. It appears it might be an issue with the stock kernel.
* UPDATE * I just flashed 20170908 and then flashed the 20170728 kernel and it works. So it must be the more recent stock kernels that are the issue.
Related
I have read so many threads about Nougat that I have gotten myself a bit confused, I think.
I am running an XT1644 in the US on the Verizon network. My device has an unlocked bootlader and is running stock software, albeit rooted (i like adaway), build number MNPJ24.139-48.
I am quite interested in trying out some of the Nougat-based ROMS, and each of them suggest flashing the soak test first. As I read the threads for the soak test, they seem to suggest that they are all for India or variants other than mine.
At the risk of making myself out to be an idiot, I'd like some clarification/confirmation as to how I can get the correct soak test for my variant. I have no issue with following directions, however, the sheer amount of directions and variations for this model just make me want to be extra cautious before flashing.
Thanks
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
SoNic67 said:
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
Click to expand...
Click to collapse
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
The .64 update for the MM works fine on my phone, but I am on ATT network (GSM) so... Idk for Verizon.
myk.robinson said:
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
Click to expand...
Click to collapse
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
So, I have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.
i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.
di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.
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.
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