Database Users

Complicated problem, never came across in the whole lifetime of my android usage.

TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.

@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.

strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!

whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:

UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.

strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working

whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?

strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.

whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?

strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.

whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.

I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.

echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks

MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.

whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...

Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.

UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.

Stuck in Bootloop

I'm currently stuck in a bootloop with a rooted (Prime Exclusive) Moto G5 Plus. Every time I turn on the phone or restart the phone, I keep getting sent to TWRP Recovery, and can't boot into the system. What I want to do is just restore this phone to the stock firmware and factory reset my device. Please help me.

FamilyGuy0395 said:
I'm currently stuck in a bootloop with a rooted (Prime Exclusive) Moto G5 Plus. Every time I turn on the phone or restart the phone, I keep getting sent to TWRP Recovery, and can't boot into the system. What I want to do is just restore this phone to the stock firmware and factory reset my device. Please help me.
Click to expand...
Click to collapse
Download your actual firmware, unpack it into your fastboot folder (recommend: Minimal ADB & Fastboot), bring your device in fastboot mode and flash everything one after the other:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Sent from my Moto G5 Plus using XDA Labs

@Wolfcity Can you be more clear as to what you mean by my "actual firmware"? I'm not sure what firmware version my device is on, nor can I find any repository on the Internet to download said firmwares for the (Prime Exclusive) Moto G5 Plus.

FamilyGuy0395 said:
@Wolfcity Can you be more clear as to what you mean by my "actual firmware"? I'm not sure what firmware version my device is on, nor can I find any repository on the Internet to download said firmwares for the (Prime Exclusive) Moto G5 Plus.
Click to expand...
Click to collapse
As you have flashed a TWRP you must have your bootloader unlocked. You need the firmware that your device was on when you did that.
Downgrading i.e. flashing an older firmware can brick your device.
The newer firmwares for reteu/retus are ending on 93-x, like
POTTER_NPNS25.137-93-4 (january security patch)
POTTER_NPNS25.137-93-8 (march security patch)
POTTER_NPNS25.137-93-10 (april security patch)
Earlier ones had another number scheme.
Firmware for India, Brazil and Asia Pacific is ending on 92-x.
I don´t know the Prime exclusive edition but I don´t think that it uses another firmware. But I heard of a Amazon version with ads and an unlockable bootloader?
How did you unlock then? Or are there different versions?

@Wolfcity I really don't know how to respond, but I can't figure this out. I don't know what firmware version to install, I don't know where I can find the firmware version, and whenever I try to run a fastboot command through adb I get stuck on an infinite "waiting for device" message. Can you please help me with step-by-step instructions on how to fix this?

FamilyGuy0395 said:
@Wolfcity I really don't know how to respond, but I can't figure this out. I don't know what firmware version to install, I don't know where I can find the firmware version, and whenever I try to run a fastboot command through adb I get stuck on an infinite "waiting for device" message. Can you please help me with step-by-step instructions on how to fix this?
Click to expand...
Click to collapse
Here are some firmware sources:
https://androidfilehost.com/?a=show&w=files&flid=171014
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1
I can´t tell you on which firmware you were when you unlocked your bootloader. And the next problem is that you can´t run any fastboot commands, you need fastboot to flash the stock firmware with the commands I posted above.
Have you the latest Motorola drivers and something like Minmal ADB & Fastboot installed?

1) from TWRP run "Bootloader reboot"
2) send the command "fastboot devices" receive the serial number of the phone. Once you have obtained the serial download "POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt" and execute the commands as suggested.

@Wolfcity, @antonio52 Thank you guys SO much! I finally got around to doing this, and my device is running perfectly well now! I couldn't have done it without you!

FamilyGuy0395 said:
@Wolfcity, @antonio52 Thank you guys SO much! I finally got around to doing this, and my device is running perfectly well now! I couldn't have done it without you!
Click to expand...
Click to collapse
You're welcome. Nice to hear you got it working again.
Sent from my Moto G5 Plus using XDA Labs

Nexus Player Rom help

Hi im having problems here with my nexus player
i purchased and used this since 3year with custom AOSP android lollirock that i found on this forum how to install in the begining when i purchased it now since there are newer version of android and app stop working correctly on it i wanna return to the stock rom
what it did is after booting into fastboot and running those command using google official rom
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase cache
fastboot flash bootloader (bootloader filename)
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache (there were no cache.img in the google official rom package so i leave it like this)
fastboot reboot
my nexus bootloader is in UNlocked state, i remeber unlocked it the first time i flash the original rom to install the lollirock one
the device rebooted and now im stuck in the bootloop of circle turning in the screen
i did the exact samething trying to install a older version of the rom (after i read on the internet that the 8.00 was sending people who never messed around with fastboot and just using OTA to update into this samebootloop)
i got the same exact problem using an older version of the google official rom 7.1.2 i try i think
then i tried to reinstall AOSP custom 7.1 of android that i found on the forum of zulu99 he tell to
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w (and i noticed that when i run this fastboot return me and error saying that the file is missing (cannot generate image for userdata)
anyone know what i can do from here ?
im able to get into fastboot no problem holding the button under the device before i plugged in the power cord
im pretty a beginner using ADB and flashing android roms so i have no clue what im missing here but i guess its something due to the fact that ivd run fastboot erase cache.img in the begining !?!?
Please any help would be greatly appreciated

I always used the nexus root tool kit for everything.
http://www.wugfresh.com/nrt/

Bootloader - Amazon Moto G7 with Alexa Hands-Free – Unlocked – 64 GB – Clear White

Took a gamble and purchased a G7 through Amazon, fast shipping and easy returns.
It showed XT1962-1 and came with all of the Amazon apps pre-loaded. I went to the motorola bootloader unlock page and attempted to unlock it. ***IT WORKED!!!!!***.
After bootloader was unlocked, I took a bigger chance and attempted to patch the boot.img from the XT1962-1 retus stock rom. Patched appeared to be successful so I copied it back over to desktop and then flashed it back to the g7. Uh oh, now it is stuck on unlocked device screen followed by a very brief motorola splash screen then back to device is unlocked.
Tried flashing stock boot.img back with the same results. Decided to go ahead and flash full stock room back using the commands from flashflile.xml.
Rebooted and back working. Shut it down and attempted to put the patched boot.img back on and this time IT BOOTS.
installed magisk app and confirmed root. SUCCESS!

Can you please explain to a beginner what you did, and what do you mean by "flash full stock room back using the commands from flashflile.xml"?
Thanks for your time

steps
I can only tell you what worked for me and can't offer any advice or assistance if you try this and run into trouble. If you aren't comfortable with flashing or don't have a spare backup phone in-case you run into trouble then I wouldn't recommend this.
I grabbed the stock XT1962-1 retus stock image from here:
https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/
unzipped it to a folder and then dropped adb/fastboot into the same folder. I did NOT erase the modem or userdata/ddr since it was a new phone that wasn't setup to begin with.
From command prompt in the folder with the unpacked stock rom in it, run these commands. I would recommend one at a time to watch for errors.
Let it reboot once to make sure it worked. The first boot may take a while.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
rem fastboot erase modemst1
rem fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

does hands free alexa still work though after flashing? Supposedly the hands free alexa option only works with the amazon rom.

I followed this procedure on a moto g7 power and it worked as well. I didn't have any issues booting up the first time after patching the patched boot image that magisk created like you did. I'll comment over on the g7 power board, but wanted to thank you for your instructions.

Can I safely assume that after flashing the stock rom, the phone is not converted to a stock g7 instead of Amazon branded one
Thanks.
Sent from my MI 8 Lite using Tapatalk

rootuser11 said:
Can I safely assume that after flashing the stock rom, the phone is not converted to a stock g7 instead of Amazon branded one
Click to expand...
Click to collapse
I can only say what I have experienced on my phone. It is stock, hands free alexa does appear to work. I have a buddy at work with stock g7 and the installed apps appear the same. I can't visually tell a difference between the 2 phones other than under about phone my software channel shows amazon. Others with more experience may have more information to offer you however it worked for me and I haven't had any issues and great battery life so far.

timecutter said:
I can only say what I have experienced on my phone. It is stock, hands free alexa does appear to work. I have a buddy at work with stock g7 and the installed apps appear the same. I can't visually tell a difference between the 2 phones other than under about phone my software channel shows amazon. Others with more experience may have more information to offer you however it worked for me and I haven't had any issues and great battery life so far.
Click to expand...
Click to collapse
Hmm ok. It seems like Amazon stuff still resides somewhere to indicate that the phone is related to Amazon. Ugh..
Sent from my MI 8 Lite using Tapatalk

I cannot find Netflix in Google play store
timecutter said:
I can only say what I have experienced on my phone. It is stock, hands free alexa does appear to work. I have a buddy at work with stock g7 and the installed apps appear the same. I can't visually tell a difference between the 2 phones other than under about phone my software channel shows amazon. Others with more experience may have more information to offer you however it worked for me and I haven't had any issues and great battery life so far.
Click to expand...
Click to collapse
Hi timecutter,
I have a Moto G7 (US version) with Amazon Alexa Hands-Free – Unlocked, with its firmware totally replaced with the Stock US retail firmware. Everything is fine except I cannot run Netflix. I cannot find Netflix from Google play store. I tried to download several netflix apk files from apkmirror.com and install them but all of them failed to run with the message that the version of Netflix is not compatible with my phone.
Does this happen to you? Which version of netflix did you use? Where did you get it?
Thanks.

Moto G4 xt1625 Amazon variant bricked with Oreo

Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?

meolivares06 said:
Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?
Click to expand...
Click to collapse
You cannot root with a locked bootloader.

i have the same issue, wondering if any solution out yet ?

henser said:
i have the same issue, wondering if any solution out yet ?
Click to expand...
Click to collapse
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs

sd_shadow said:
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i've just tried, tried rescue but i got an error when trying to install flashboot flash error. Says Flash failed, try again. stuck at 68 Percent

Currently looking in to flashing this.
Did you all try to flash the rom as a single file in twrp or similar or did you try to flash individual files to individual partitions?
With fastboot like:
DO NOT USE FOR THIS PHONE, SHOWN AS EXAMPLE!
sudo fastboot flash bluetooth BTFM.bin
sudo fastboot flash dsp dspso.bin
sudo fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
I used this kind of code for flashing new software to my G7
(Sudo is for using these commands in linux)

Restore
Just follow those steps, doesn't matter if you have the bootloader locked.
Important:
Next time, unlock the bootloader and install a custom recovery, twrp is the most common. After that flash the 8.1, it will reboot several times like if it has a problem but thats just the android config. Don't panic if you see it reach the homescreen and reboot, 3 or 4 times. It will do that untill you see the finishing progress bar prompt when it boots to homescreen

will give a try with this to see if it works.
edit tried, with 7.0 and the second command says preflash validation failed, with 8.1.0 the phone says okay all the commands but when i reboot the phone gets stuck on the blue m logo