Database Users

Diag Mode with G4 for QPSD?

Hello,
i really searched the whole web to bring my g4 in the diag mode to use QPSD but i find nothing. Maybe someone can help me?
i installed cm13 on a xt1622.
Greetz from Germany

Tyrantre said:
Hello,
i really searched the whole web to bring my g4 in the diag mode to use QPSD but i find nothing. Maybe someone can help me?
i installed cm13 on a xt1622.
Greetz from Germany
Click to expand...
Click to collapse
To enter diag mode, you need to put the phone into QCDiag mode. To do that you choose BPTools from bootloader (use up/down volume key) , then you press Start.
Once booted into BPtools, you will get 3 new unknown Moto G(4) devices in Windows Device Manager. You better have Mototrola's own software installed (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481). If you do, you just select the first Moto G(4) and update driver > Let me Pick > Ports and ... > Select Motorola from list of manufacturers and set the driver on the right pane to the "QCDiag" one, guess the 4th or 5th item.
BTW: if you do the process more than once, order of unknown Moto G(4) devices get scrambled, so you just update driver for all 3!

MK+2017 said:
To enter diag mode, you need to put the phone into QCDiag mode. To do that you choose BPTools from bootloader (use up/down volume key) , then you press Start.
Once booted into BPtools, you will get 3 new unknown Moto G(4) devices in Windows Device Manager. You better have Mototrola's own software installed. If you do, you just select the first Moto G(4) and update driver > Let me Pick > Ports and ... > Select Motorola from list of manufacturers and set the driver on the right pane to the "QCDiag" one, guess the 4th or 5th item.
BTW: if you do the process more than once, order of unknown Moto G(4) devices get scrambled, so you just update driver for all 3!
Click to expand...
Click to collapse
Thanks for your fast reply!
I also thought that it will work like you told me, but i cant see the devices in devicemanager... I only see 1 entry of" Moto G(4)" in "portable devices" and one entry in "Andoid Devices" named "Motorola ADB Interface" ...
Maybe it wont work on win7 64 bit ?
And if i select: "boot in BP tools", is it normal that it boots the os as normally?

Search for "Qualcomm QPST Diag drivers", something like this:
http://forum.gsmdevelopers.com/showthread.php?t=6396

I installed the drivers you linked. But no devices are in my devicemanager..
Could it be a problem that i have not the stock firmware? i tried cm13 and lineageos14. At this time im downloading the stock firmware to test it.
I think that the g4 is not getting in the diag mode. Is there the possibility to see if its in the diag mode? I plugged the device in a nother computer. Also no DIAG USB device is detected. I should see the device as usb diag device in devicemanager even if the drivers are not installed or?
do you get in the diag mode with the g4 on cm13 or any other os?

I forgot where I too my drivers from, try different ones, from here even. The diag mode is functional, at least with stock bootloader and stock OS (ElementalX rooted).
PS: I don't flash TWRP, when I need it, I just load it up for that instance. I don't do anymore CM (Lineage), too many problems for me.

Did you try "adb reboot edl" from os, or "fastboot reboot-edl" from bootloader ?

Get root access on the phone and adb working.
adb shell
$ su
$ setprop sys.usb.config diag,adb
Device will disconnect/reboot probably. Now reconnect and see if the diag mode works and your phone shows as a COM port.
Else try changing the selinux status via the build.prop file (Sorry forgot the code) and then repeating the steps

vache said:
Did you try "adb reboot edl" from os, or "fastboot reboot-edl" from bootloader ?
Click to expand...
Click to collapse
It works, i did it from the os and the device rebooted. dont know what this mode is for, but i get in "Device Manager": Qualcomm HS-USB QDLoader 9008 (COM4).
But if i try to make a backup in QPST i got an error: "There is no Phone connected to the selected Port".. so i think its still not in diag mode. What is that mode for?
I also tried "setprop sys.usb.config diag,adb" but nothing happens in the phone.
Now i flash the original os and try it aggain. If it wont work, im at the end with my nerves :laugh:
EDIT:
Ok, i think to flash to stock rom with this guide:
3. Reboot your Moto G4 into the Bootloader Mode. To do so, turn off your phone and then press and hold the Volume Down & Power buttons simultaneously for a few seconds.
4. Connect your phone to your PC via USB cable.
5. Now, launch a command window from inside the ADB folder (where firmware files are saved). To do, click shift key, right click and select open command window here option).
6. In the command window, issue the following commands one by one:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
8. And, finally, reboot your device by issuing the below command:
mfastboot reboot
Your Moto G4 will reboot now. If you have unlocked Bootloader warning, then do the following:
Click to expand...
Click to collapse
but i got a bit fear because the command erase modemst1... isnt then my imei gone? ok, i first try to flash a custom stock rom from here
Else try changing the selinux status via the build.prop file (Sorry forgot the code) and then repeating the steps
Click to expand...
Click to collapse
ok, idont know what you mean with this :/

@Tyrantre what are you actually trying to accomplish using QPSD?

tywinlannister7 said:
@Tyrantre what are you actually trying to accomplish using QPSD?
Click to expand...
Click to collapse
Nothing special, just doing some backups and playing around with some things because last time i bricked my phone complete So for other software i need the diag mode too, and honestly it just get my angree that it not work on my phone.
EDIT:
Maybe you know a kernel or rom where you are sure you can load in diag mode?

tywinlannister7 said:
$ setprop sys.usb.config diag,adb
Click to expand...
Click to collapse
That doesn't work on Moto. Only the boot menus work.
PS: I use this mode to change the LTE bands (add band 20 on the US). It "took" the required change (not like Asus Zenfone Laser 2), but when tested in EU, it didn't really work. You need QXDM also, besides the QPST.

SoNic67 said:
That doesn't work on Moto. Only the boot menus work.
PS: I use this mode to change the LTE bands (add band 20 on the US). It "took" the required change (not like Asus Zenfone Laser 2), but when tested in EU, it didn't really work. You need QXDM also, besides the QPST.
Click to expand...
Click to collapse
Thanks!
now i figured out that the Diag mode seems to work only in the "stock rom" by choosing BP TOOLS.. I got the 3 unknown devices now. I test arround and will make an update if i get it to run. But it looks better now

Ok now it works till the point where i can do a backup in qpst. But if i want to restore the backup it just dont start and gives an error that it became a error.
could it be that there is a write protection on the modem partition and i have first to clean the modem partition? Or is it a bad idea?
Ok, im now a bit sure that there is a write protection. So if i want to change/add bands to the modem in NV Manager or try to recover a qpst backup, it wont work. Is there a way to make the partition writeable?
i reade in an other guide, that there is a way to restore the qpst backup. I have to delete some modem partitions:
This is the inside of your Snapdragon 820/821 based Xiaomi. Only 3 part form here matters for us, modemst1, modemst2 and fsg, those the partititions hosting your baseband and imei info (not all Snapdragons, but most Chinese made Qualcomms). Please keep in mind, this is very important, numbers are variable depending on the phone model, so names are important for us, not numbers, don’t try these numbers on a phone other then Mi 5 series, just list your parititon table and look for modemst1, modemst2 and fsg. Let’s zero/emty these 3 partitions :
dd if=/dev/zero of=/dev/block/sdf3
dd if=/dev/zero of=/dev/block/sdf5
dd if=/dev/zero of=/dev/block/sde28
reboot
Click to expand...
Click to collapse
after this it should works. But i fear to try this, because i fear to loose my imei ect. for ever. Is there a way to backup the whole phone with all partitions up just to get save if something happens?
@SoNic67 , how do you changed the lte band? do you didnt got a error by writing to the phone with qpst? Do you done it with moto g4?
EDIT;;
Ok, deleting the modem Partitions works, but flashing after with qpst doesnt. and flashing with flashfire works too. But why no qpst? why can falshfire flash the partition and qpst cant?

I think you have to allow the writing in QPST. Never messed up with flashing the whole modem in QPST, just used it as as server (QPST Configuration) for changing the LTE with QXDM.

Ok, thanks for all help, i think its not possible becaus i couldnt find a way to to make those writeable..

tywinlannister7 said:
@Tyrantre what are you actually trying to accomplish using QPSD?
Click to expand...
Click to collapse
repair imei as an example. isnt there a way to make it writeable?

Tyrantre said:
repair imei as an example. isnt there a way to make it writeable?
Click to expand...
Click to collapse
Actually I tried using QPSD for writing the IMEI on my mum's (apparently mine) Xiaomi RedMi Note 4G (dior) usong that .qcn file method. But it failed to write. Another thing what I tried was flashing CM 13 on it amd followed by Xposed Framework...using a module for changing IMEI I was able to write the IMEI successfully. But alas, the baseband of the phone was lost too, so IMEI writing was useless in my case.

IMEI change is illegal. And unethical because it affects other people phone too (the one that you clone the IEMI).

SoNic67 said:
IMEI change is illegal. And unethical because it affects other people phone too (the one that you clone the IEMI).
Click to expand...
Click to collapse
Ok, i thought and just waited for the point when someone post that this is illegal. It´s just illegal if i change it to an other number, just repairing it and changing it to its own imei is not. So second, why everybody makes such a big deal that it is illegal to change the imei? In times where you are so fast a political enemy in some countrys i think it could be usefull for many people. (not in my case, Germany best country in the world )
Im at the point where i thinks that there is no way to "restore" the imei of the moto g4 without using somekind of flashbox ect. So i look out to buy an other phone to play around with Thanks for al the help, learned much

XT1642: IMEI show as 0 (even after reflashing to original unrooted)

Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!

bauss1 said:
Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat

BlackBeats said:
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat
Click to expand...
Click to collapse
Yes. Did exactly that. Flashed the files of XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip ... with the commands
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 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 fb_mode_clear
fastboot reboot
Showed some "errors" at fastboot at some, but I think that was normal. And flashing worked.
But in the end, both IMEI are still 0.
Even reflashed the NON-HLOS.bin. IMEI numbers are still 0.

Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Edit: not sure if the imei and wifi errors accured since MPJ24.139-23.4, or after the OTA update file, or sometime inbetween because i deleted something in TWRP.

bauss1 said:
Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Click to expand...
Click to collapse
Try flashing nougat I guess downgrade created a problem

BlackBeats said:
Try flashing nougat I guess downgrade created a problem
Click to expand...
Click to collapse
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility

bauss1 said:
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility
Click to expand...
Click to collapse
Try removing oem fb set command
If it doesn't work then flash nougat then use 6.0.1 custom ROM
Edit fb_mode_set

Flashed everything again, without the fastboot oem fb_mode_set (MPJ24.139-48). Both IMEIs are still 0, everything else is fine though, original wifi mac.
---
Then took original over the air update it offered me (NPJ25.93-14). Installed without problems.
But, guess what.... it made things worse.
Now i am on NPJ25.93-14, the IMEIs still are 0, and the wifi mac address is at 02:00:00:00:00:00 again.
What I noticed is, in settings it shows the IMEI SV (Slot1) and IMEI SV (Slot2). They both changed to 08. I think they were 03 or so before.
Edit: In the boot recovery thing it says the usual stuff:
Battery OK (Charging)
flashing_unlocked
Software status: Official
...
So... updating to Nougat did not help, made things worse (wifi mac weird again, IMEI still 0).
Any other ideas?

Anyone looking for the solution to this problem, it has been fixed here: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue

FYI: recovered G5 XT 1676 to stock and updated. :)

Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.

where do you get the stock firmware?

Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.

We're you able to revert to a locked bootloader after this, I am looking forward to do so

We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.

astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts

ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing

TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier

downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance

distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order

Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good

thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.

distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions

Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks

astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition

I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan

[STOCK][ALJETER]Firmware Moto G6 Play - OPP27.91-87

DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO G6:
Download Moto G6 Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
THANKS MOTOROLA FIRMWARE
Moto G6 Play: Drive (password : MotorolaFirmwaresLB )
ALJETER_OPP27.61-14-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.rar
Moto G6 Play: AFH
ALJETER_OPP27.61-14-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.rar
Moto G6 Play: Drive (password : MotorolaFirmwaresLB )
ALJETER_OPP27.91-87_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.rar
adb fastboot
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp dspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse

Hi @lohanbarth,
Please change the title of the thread to "[STOCK][ALJETER]Firmware Moto G6 Play".
The reason is to be consistent with the other two threads for "G6" and "G6 Plus".
With this change will be more easy to distinguish for users of the "G6 family".
And thank you for provide theses firmwares! :good:

Sorry if this is a dumbass question but can I flash this on the boost/Sprint variant since it can be bootloader unlocked? And will it remove the bloatware downloading from boost/Sprint. Again sorry if it's a dumb question.

ninjakira said:
Sorry if this is a dumbass question but can I flash this on the boost/Sprint variant since it can be bootloader unlocked? And will it remove the bloatware downloading from boost/Sprint. Again sorry if it's a dumb question.
Click to expand...
Click to collapse
This is the ALJETER device. The sprint/boost version is the JETER.

moto g6 play xt1922-4
I tried to relock bootloader in my moto g6 play xt1922-4 but i had a problem with boot.img.
( bootloader) Still require signed boot.img bad key
do you have the original rom for xt1922-4? please help

kwiksi1ver said:
This is the ALJETER device. The sprint/boost version is the JETER.
Click to expand...
Click to collapse
Can we get stock firmware for the JETER?
I have one tell me what you need and I'll help the best I can

zindak335 said:
I tried to relock bootloader in my moto g6 play xt1922-4 but i had a problem with boot.img.
( bootloader) Still require signed boot.img bad key
do you have the original rom for xt1922-4? please help
Click to expand...
Click to collapse
sounds like i ran into same thing with my xt1922-9 bad kay when i unlocked bootloader

hello
none of these firmwares seem to work on my moto g6 1922-9 when i flash through adb i get meany errors, i think it all started when i unlocked boot loader . any help would be great

FizzyAps said:
Can we get stock firmware for the JETER?
I have one tell me what you need and I'll help the best I can
Click to expand...
Click to collapse
That’s what we boost mobile phone owners are looking for.

Yeah
suicidedoordavid said:
That’s what we boost mobile phone owners are looking for.
Click to expand...
Click to collapse
I have a unrooted on if some could walk me through the steps to get it off the the phone it’s self I would

I have tried this a hundred times and it's simply will not flash on the Moto G6 play

timelessxiii said:
I have tried this a hundred times and it's simply will not flash on the Moto G6 play
Click to expand...
Click to collapse
If you have a bricked boost mobile variant and need a jeter rom u can try this backup: https://drive.google.com/open?id=1pHiR6fssHOTJ-13-yttipMdB-DBNv_IM
Just unzip it and put it inside the TWRP folder on your phone and click Restore with twrp. It should flash. I tested it twice on my G6 Play (boost mobile variant) (jeter)

I actually got it flashed through twarp it said it was a success but when I reboot my phone it stays on the Motorola splash screen
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
I've got to admit that's closer than I've ever been
---------- Post added at 07:00 AM ---------- Previous post was at 06:12 AM ----------
steveg322 said:
If you have a bricked boost mobile variant and need a jeter rom u can try this backup: https://drive.google.com/open?id=1pHiR6fssHOTJ-13-yttipMdB-DBNv_IM
Just unzip it and put it inside the TWRP folder on your phone and click Restore with twrp. It should flash. I tested it twice on my G6 Play (boost mobile variant) (jeter)
Click to expand...
Click to collapse
bookmobile is cdma the one i have xt1922-9 is a gsm that probley why it wont go a passed the Motorola splash screen after flashing

I followed all the steps, but at the time of restart, I sent back to the boot manager, I had to install the previous firmware

Bty I found the right firmware for the Moto g6 play 1922-9 and it works flawless

if at the end of flashing it is returned to the bootloader...
1 clarification about the firmware opp27.91-87.. in the command lines, one of the system lines is missing:
fastboot flash system system.img_sparsechunk.4
If they add it to the .bat, or if they include it manually, it should start without problems

problem with sound
i flashed my xt1922-4 a few hours ago, but first problem that i found, was the calls, speaker no sound when make or receive calls, only handset and can't install magisk (boot loop after boot moto sequence)

Wid_w said:
i flashed my xt1922-4 a few hours ago, but first problem that i found, was the calls, speaker no sound when make or receive calls, only handset and can't install magisk (boot loop after boot moto sequence)
Click to expand...
Click to collapse
I have the same model and I noticed that one of the lines in the bat file is wrong, the dspso.bin is actually adspso.bin (line 5), just edit it and it should work fine:
fastboot flash dsp adspso.bin
In addition, add the line that Wid_w mentions:
fastboot flash system system.img_sparsechunk.4
I attach my edited .bat file, I just 've flashed mi phone and everything seems to work without problems.

Thansk for guide, but i cant install Magisk on this OPP27.91-87, stay in M Logo. Any Help? (my poor english)

Wrong IMEI in zui com?

Hi,
I put all information into "zui.com/iunlock" correctly, but I get a "Please enter the correct IMEI1" error, and I'm entering it correctly
Please help...

If it's a brand new phone, the imei is not registred by the website at the start.
After a couple of day of use it must work.
Same problem for me at the start and after two day of using the phone my imei is working on the website.

Thanks for the reply
Do I need to put my sim in the phone?
Or is it enough just to connect to wifi?

I used my sim for about 3h, and I got the site to take my IMEI!
Now my bootloader is unlocked
Thanks

Your welcome

I received my smartphone for 10 days. but my emei is still not recognized.
I installed a firewall and everything is blocked except the browser and the messages. I have to authorize a specific program for zui to integrate it?

hello, after 25 days of waiting my imei still did not pass. yesterday I sent an email to devworld and today I had my file
YES :good:

lecomte_jean said:
hello, after 25 days of waiting my imei still did not pass. yesterday I sent an email to devworld and today I had my file
YES :good:
Click to expand...
Click to collapse
Good to know, thank's for the feedback

Bypass
I had the exact same issue and for some weird reason the weirdest glitch ever helped my bypass ZUI all together:
I made a little .bat file to automate all the adb and fastboot commands once I'd get the bootloader unlock file
I didn't know for sure if I had referred to the subfolders in my adb map correctly so I wanted to test it out:
adb reboot bootloader
fastboot flash unlock ".\Z6 Pro\Bootloader.img"
fastboot oem unlock-go
fastboot reboot
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta ".\Z6 Pro\vbmeta.img"
fastboot reboot bootloader
fastboot flash recovery ".\Z6 Pro\twrp.img"
that's what it was gonna be^
but to test out if I had referred correctly I changed vbmeta.img's name into bootloader.img since it was the first path and I expected it to fail but this way I'd at least find out if I got a file not found error or a incorrect boot loader unlock file error.
It flashed correcty, the os is stable and I just installed TWRP.
Idk if this can be done with any img, but the vbmeta file shouldn't have done that. XD