Database Users

Amazon XT1625 - Software status: modified

Hello, I am running stock image, unrooted, locked.. at one point I tried flashing the Nougat update from the Indian release but it failed with an error. I had no problems, wasn't bricked or anything, just wasn't able to install.
I now see it says software status modified and am wondering:
1. will this affect my ability to get the OTA update? I'm seeing people are getting the update but I don't have it available yet. I know it's rolling out in waves but I'm worried I might not be eligible even when it does reach.
2. How can I restore it to say not modified? I thought maybe flashing the stock image but I can't find the stock Amazon images. On the Moto website under relock instructions the XT1625 shows up with a .64 firmware but since I have the amz variant I don't know if that will work?
Any advise appreciated

Well won't you believe, I am now downloading official Nougat. modified software status doesn't affect it. phew!

Thanks for posting. I decided to check for an update on my non Amazon version and there was an update waiting. ?
I was on 139-48
Sent from my Moto G (4) using Tapatalk

Unlocked Amazon XT1625 to retail firmware?

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.

Questions about our dear potter.

Hello all, I'm new to the g5+ but have been rooting phones for a while but I'm a little hesitant with this phone for a couple reasons. I'm coming for a moto x pure edition "Clark" which had a lot less different firmware upgrades and a straight forward rooting process.
My first question is which twrp are most people using? I've found 4 different ones on here but not sure which one is best. Also not sure if me being on firmware version Npns25.137-33-5.
Which brings me to my next question. Has anyone successfully rooted retus potter npns25.137-33-5? I literally can't find any information about peoples success on this build number. Normally I would just try it but I can't find the factory firmware to flash the system partition back if no mess it up. The only 33-5 firmware I can find says nits for the amazon version but mine is non amazon xt1687 64gb model.
Any feedback would be much appreciated, really looking forward to aospa, might try crdroid too that was my favorite ROM on clark

There's a thread somewhere that has a program you can use to unlock bootloader and twrp etc. I don't think it matters which firmware you're on but the stock files are in that thread also. I used the program and everything worked fine. I think it's in the development section

redman321 said:
Hello all, I'm new to the g5+ but have been rooting phones for a while but I'm a little hesitant with this phone for a couple reasons. I'm coming for a moto x pure edition "Clark" which had a lot less different firmware upgrades and a straight forward rooting process.
My first question is which twrp are most people using? I've found 4 different ones on here but not sure which one is best. Also not sure if me being on firmware version Npns25.137-33-5.
Which brings me to my next question. Has anyone successfully rooted retus potter npns25.137-33-5? I literally can't find any information about peoples success on this build number. Normally I would just try it but I can't find the factory firmware to flash the system partition back if no mess it up. The only 33-5 firmware I can find says nits for the amazon version but mine is non amazon xt1687 64gb model.
Any feedback would be much appreciated, really looking forward to aospa, might try crdroid too that was my favorite ROM on clark
Click to expand...
Click to collapse
I've rooted 35-5. Works the same way.

Also came from Clark. Rooting Potter is easy and I even screwed up multiple times by trying to flash a zip file when I should have been flashing a .img
file so I can testify that the rooting process is robust enough to not brick immediately if something goes wrong.

Can anyone shed light on the TWRP app and it's functionality. Does it install image files correctly and so forth? I'm literally under 24 hours having unlocked and flashed AOSPA Sso still learning the device

How do I go from 7.0 with "U" software to 8.0?

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

[Q] VS995 Bootloader Unlock Question

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