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
Related
Pre-requisites:
a) Download and install Motorola Moto EDrivers
b) Download and extract the stock Firmware of your choosing
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot View attachment 2427667 (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
d) Get ADB (if you don't already have this, I suggest downloading and installing Minimal ADB and Fastboot by shimp208:
Direct Download
Disclaimer:
Follow these instructions at your own risk. If something goes wrong don't blame me!
These are the original stock signed image files from Motorola it should work on all Moto E Variants.
Steps to restore stock firmware:
1) Reboot the phone into bootloader mode. There are 2 ways to do this.
I) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
II) The 'software' way.
a) Enable developer mode on the Moto E (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open "Minimal ADB and Fastboot". Type:
Code:
adb reboot-bootloader
You should see the Moto E bootloader screen with the following options:
Code:
Normal Powerup
Recovery
Factory
Switch Console [NULL: null]
Barcodes
BP Tools
2) Open a command prompt / terminal (Start -> cmd.exe in Win7) and browse to the folder with the extracted firmware.
In my case:
Code:
cd c:\falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB
3)
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
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 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 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 oem config carrier vzw
mfastboot oem fb_mode_clear
If you want to skip typing these commands one by one use MOTOEFLASHALL.bat. Place the .bat file inside the extracted firmware folder and run it.
4) Wait, you should now be rebooted into a fully stock Moto E firmware.
Original Thread
Creditstbon3
@lohanbarth for instructions and firmware images
FAQ
Q1: Will this work on locked bootloaders?
Ans: Yes as stock firmwares are digitally signed by Motorola.
Reserved
nice job!,
edit
iB4STiD said:
nice job!, but links aren't working
Click to expand...
Click to collapse
Are stock images even available yet?
iB4STiD said:
nice job!, but links aren't working
Click to expand...
Click to collapse
qbking77 said:
Are stock images even available yet?
Click to expand...
Click to collapse
The stock firmware aren't up yet
Lucas Eugene said:
The stock firmware aren't up yet
Click to expand...
Click to collapse
ah, thought they were thats why u made the thread.. this will come in handy tho in the future thanks :good:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
lohanbarth said:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
Click to expand...
Click to collapse
Hi thanks for the link I've created a new thread to manage Firmware
any stock firmware for the XT1527?
Stock firmware, non carrier
I tried following the steps to restore the firmware, but no luck since I got Preflash validation failed, which I take it to mean the boot.img is not the right one for the moto e2 (bought it from motorola online store). I had everything working, but decided to re-lock the phone, and forgot to check allow oem unlock. When i ran fastboot oem lock it sat there, and then on reboot it didn't start up, just stayed on fastboot screen. No matter what I do I can't get it past it and trying again to unlock it it says:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
So now I am stuck in a fastboot loop. Any suggestions for things to would be great.
Thanks.
Useful subject
https://www.youtube.com/watch?v=S1myrGuMCQg
lohanbarth said:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
Click to expand...
Click to collapse
@lohanbarth
can you provide stock rom for moto e 2015 3g variant
has moto released source or the firmware from the US lte gsm varient? what you have posted is for the EU model.
i'm wondering if the EU model is maybe the international version? which could in fact be used in the US.
Hi all
Stocks firmwares repository:
http://forum.xda-developers.com/showpost.php?p=60154569&postcount=21
Thanks if you help
With the Verizon model still having a locked bootloader, is there a possible chance that restoring the stock images from Motorola would allow you past that, or even the bootloader from the same model with a different carrier, this is my only device right now but I would like to test it but can't. Has anyone else thought of this?
Edit: Figured this out... made new post.
Dangerous waters ... and questions
Hi, I own a currently unlocked/rooted XT1524 (LTE/4G) which came with stock rom LXI22.50-24.1 (retde = German retail version).
At the moment I'm running @scritch007's latest rom (cm-12-20150418-UNOFFICIAL-surnia) on it and I'm thrilled to bits that someone made this happen so soon on the device. - Boundless joy, thank you so much.
But now, I'm wondering:
Lucas Eugene said:
[...] Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot oem fb_mode_set
[...]
mfastboot oem config carrier vzw
[...]
Click to expand...
Click to collapse
1. Carrier VZW
What does the "... config carrier vzw" line exactly trigger/do when being applied on an European model?
Isn't VZW = Verizon Wireless?
Shouldn't this line read something like "... config carrier gsm"?
Couldn't we omit this line?
What were the consequences?
2. Risks
After unlocking/rooting I made a TWRP Backup (mfastboot boot <twrp>, didn't touch the original recovery) and also did I dd'ing all partitions living in /dev/block/platform/soc.0/by-name/ via adb root shell.
But regarding the soft-brick issues (oem re-lock) described by @Top_Quark and @squid2 here, I'm not sure (and feeling very uncomfortable with my limited knowledge) if I could re-lock the device without problems without my/any fitting original firmware (which one?). - There is only the one mentioned in the start posting (reteuall but with older LXI22.50-13, same cid 7). - So, can I re-lock my device after a TWRP restore/adb dd ... without flashing the mentioned original signed firmware (euretall)? - Or will I being "surprised" by a nice brick?
Checklist of preconditions to re-lock and go back:
Developer options: active
USB-Debugging: active
Enable OEM unlock: active
TWRP, adb, (m)fastboot set up and working
reteuall firmware: downloaded and at hand (retde firmware still has to show up somewhere yet)
_
Then processing @Lucas Eugene's flashing list
Is this right or am I missing something?
Thank you for your time reading and your replies.
Regards
Hi! I need your help... I bought a moto e xt1524 .... This phone isn't compatible with the frequencies using in Argentina... In my country works the xt1527 version... The question is if I can flash the 1527 firmware in the 1524...
People need help. Sorry if'm posting in the wrong place, I'm new here.
I have a Moto X Play (XT1563) And after I flash it to the stock rom 6.0 he installed it right more at the time of restart he did not call more, no charges and no starts in fastboot.
The bootloader it was unlocked, and the battery was at 20% load.
When I plug it in the PC it is recognized as UNKNOWN DEVICE. What I do to try to recover it? as seen videos of people recovering MOTO G1 AND 2, MOTO X 1 and 2. Thank you in advance!
Rwaan said:
People need help. Sorry if'm posting in the wrong place, I'm new here.
I have a Moto X Play (XT1563) And after I flash it to the stock rom 6.0 he installed it right more at the time of restart he did not call more, no charges and no starts in fastboot.
The bootloader it was unlocked, and the battery was at 20% load.
When I plug it in the PC it is recognized as UNKNOWN DEVICE. What I do to try to recover it? as seen videos of people recovering MOTO G1 AND 2, MOTO X 1 and 2. Thank you in advance!
Click to expand...
Click to collapse
1st thing is please Charge your moto x play First ,it must be charged at least 50%
2nd I cant understand what u want to say .
So, Please calm Down and Explain It.
xpectedme094 said:
1st thing is please Charge your moto x play First ,it must be charged at least 50%
2nd I cant understand what u want to say .
So, Please calm Down and Explain It.
Click to expand...
Click to collapse
My bike x play does not turn over and not charge or enter the fastboot mode, I was in the custom rom RR 6.0 went back to the stock and the battery was only 20% used the following commands FlashFile file in cmd ...
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 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.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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 reboot
* q in the last command is to restart it hung up and did not care anymore.
Rwaan said:
My bike x play does not turn over and not charge or enter the fastboot mode, I was in the custom rom RR 6.0 went back to the stock and the battery was only 20% used the following commands FlashFile file in cmd ...
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 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.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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 reboot
* q in the last command is to restart it hung up and did not care anymore.
Click to expand...
Click to collapse
If its not charging then there might be problem in your Charging Jack.
First press power Button ( Around 10 sec ) When Screen Off Immediately press Power and Volume less Button.
Bootloader Mode opens .
Connect Your Charger and Check whether Charger Connected or Not ??
Now
I
Came To Your Question * q in the last command is to restart it hung up and did not care anymore. ??
When You Command " fastboot reboot " it hang up to " Bootloader unlock Screen" Its Because might be While Flashing TWRP You by mistakely Remove Your "Boot Image" and Thats Why your Mobile Hang Up.
You should Also Note That All Moto X Play dont have same Boot Image .
You First Need To Download Boot Image Flash It Then Your Problem will sohrtout For Sure.
xpectedme094 said:
If its not charging then there might be problem in your Charging Jack.
First press power Button ( Around 10 sec ) When Screen Off Immediately press Power and Volume less Button.
Bootloader Mode opens .
Connect Your Charger and Check whether Charger Connected or Not ??
Now
I
Came To Your Question * q in the last command is to restart it hung up and did not care anymore. ??
When You Command " fastboot reboot " it hang up to " Bootloader unlock Screen" Its Because might be While Flashing TWRP You by mistakely Remove Your "Boot Image" and Thats Why your Mobile Hang Up.
You should Also Note That All Moto X Play dont have same Boot Image .
You First Need To Download Boot Image Flash It Then Your Problem will sohrtout For Sure.
Click to expand...
Click to collapse
Yes, he hung up and did not care anymore. when I command "Fastboot reboot" he simply hung up and now does not care and neither starts in fastboot and also does not charge. It kind "put out the fastboot mode system" and is being recognized the computer as "unknown device" and has no way gives the flash rom stock because does not start in fastboot mode. He got hardbrick.
more where I download the boot image of it? 're Almost impossible to find a solution to this problem.
* Very need your help, Thank you!:crying:
Rwaan said:
Yes, he hung up and did not care anymore. when I command "Fastboot reboot" he simply hung up and now does not care and neither starts in fastboot and also does not charge. It kind "put out the fastboot mode system" and is being recognized the computer as "unknown device" and has no way gives the flash rom stock because does not start in fastboot mode. He got hardbrick.
more where I download the boot image of it? 're Almost impossible to find a solution to this problem.
* Very need your help, Thank you!:crying:
Click to expand...
Click to collapse
Try Flashing Firmware through RSD Lite ( Note RSD Lite Cant support Window 10)
and Please Give me Some more information .
1. Do Bootloader Mode Open or Not.
2. What Command You Exactly use when your cell Bricked .
and please reply fast.
xpectedme094 said:
Try Flashing Firmware through RSD Lite ( Note RSD Lite Cant support Window 10)
and Please Give me Some more information .
1. Do Bootloader Mode Open or Not.
2. What Command You Exactly use when your cell Bricked .
and please reply fast.
Click to expand...
Click to collapse
1. He does not enter the bootloader mode. You can not use RSD Lite to be able to give him the flash, the RSD does not recognize him because he does not enter the fastboot mode, moto x play he does nothing're completely off. when I connect the computer it is always recognized as "unknown device" so I can not give it flash or the cmd and not by RSD Lite.
2.I used all of the commands but did not pay attention had given error in any command more in the last it is simply reset the device he hung up and did not care anymore. Ai can not do anything it just know that he ta working as it appears on the computer when I connect it, the following NOTIFICATION ...
"USB Device Not Recognized,
* installing drivers ... failure.
* Unknown device. "
Every time I connect it to the computer appears such reports and have all the drivers installed and already uninstalled and installed back more not decided.
someone there gives me the file "bootloader singleimage.bin" Moto X Play (XT1563) and drivers "Qualcomm HS-USB qdloader 9008 (com12)" for me to recover my device a Hard Brick. Thanks in advance.
I have the same problem
Rwaan said:
someone there gives me the file "bootloader singleimage.bin" Moto X Play (XT1563) and drivers "Qualcomm HS-USB qdloader 9008 (com12)" for me to recover my device a Hard Brick. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem, Can you send me the files? please. do you advance with the thing? (sorry for my poor english)
laloraptor said:
I have the same problem, Can you send me the files? please. do you advance with the thing? (sorry for my poor english)
Click to expand...
Click to collapse
I have the files that can fix my machine, since'm two months without any solution. I need the files to resurrect my Moto X Play With HardBrick.
Who has the files please makes a uploud and I send. My Gmail is [email protected].
thank you!
I have same problem, my moto x play is hard bricked and gets only detected as qdloader Q9008. I am looking for the blank flash files, something like prog_emmc_firehose_8939.mbn
i also have hard bricked ( Qloader 9008 )
Did someone find a solution? Mine is also hard bricked the exact same way.
hi there I am in the same situation! any solution? any ideas?
gilbertoperezx1 said:
hi there I am in the same situation! any solution? any ideas?
Click to expand...
Click to collapse
It can be revived either by Blank flash files or by easy jtag emmc flash.. Unfortunately no one is having blank flash files.. Hopefully someone will come up with a blank flash file.. If you want to fix it quicky, then only way is flashing emmc by easy jtag box.. Like the video below..
https://www.youtube.com/watch?v=t7ZzeRGOoEw&feature=youtu.be
Moto x play hard brick
Moto x play turned off after an update and did not turn on nor does it give a precise signal of the files BlankFlash for XT1563
alexmota00 said:
Moto x play turned off after an update and did not turn on nor does it give a precise signal of the files BlankFlash for XT1563
Click to expand...
Click to collapse
Its hard bricked and no blank files aren't working as of now.. We have started a telegram group of those who got their MXp's hard bricked.. You can join too if like.. Here is the link : https://t.me/Unbrick_MXP
i have the same problem hardbrick please send me file. my mail [email protected]
david livingstone said:
i have the same problem hardbrick please send me file. my mail [email protected]
Click to expand...
Click to collapse
There is no working files available as of now..
share to me please have the same problem
Have the same problems please share to me this files
[email protected]
Hi everybody...I'm in trouble with my Yotaphone YD201.
I done format data with TWRP.
Then, I run these commands with Win10 for clean flash of RU144:
Code:
fastboot flash boot {Directory_firmware/boot.img}
fastboot flash -S 512M system {Directory_firmware/system.img}
fastboot flash recovery {Directory_firmware/recovery.img}
fastboot flash cache {Directory_firmware/cache.img}
fastboot flash modem {Directory_firmware/radio/NON-HLOS.bin}
fastboot flash sbl1 {Directory_firmware/radio/sbl1.mbn}
fastboot flash rpm {Directory_firmware/radio/rpm.mbn}
fastboot flash tz {Directory_firmware/radio/tz.mbn}
fastboot flash userdata {Directory_firmware/userdata.img}
fastboot flash aboot {Directory_file__emmc_appsboot.mbn}
fastboot reboot
After the last one, Screen gone black and nothing appends...
Now, adb and fastboot can't contact with Yota ("adb devices" give "<waiting for devices") .
Now, In Win devices, I can find " QHSUSB_BULK".
After some search, I found out that my phone is in a recovery mode of Qualcomm. Does anybody know how to unblock it? Problably I need of specific driver to contact with this phone. Thanks so much!
P.S.: do not esitate to contact me if my english is not clear =)
How about a method like this https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/ but use Yotaphone files instead?
evilracer123 said:
How about a method like this (...) but use Yotaphone files instead?
Click to expand...
Click to collapse
This discussion uses Msm8974DownloadTool.exe from the directory of ColorOS but the wire connection does not work (the file is no longer available, from Mega).
Also, not sure if I can use Msm8974DownloadTool.exe with Yotaphone. Alternatively, what can I use?
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
kidbao said:
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
Click to expand...
Click to collapse
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
madbat99 said:
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
Click to expand...
Click to collapse
Hi thanks for responding! I have the E4 XT1765. It's Qualcomm. MetroPCS. I tried the PERRY_METROPCS_C and PERRY_METROPCS_C_7.1.1 from from here: firmware. center/firmware/Motorola/Moto%20E4/Stock/
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Flash aokp latest build
beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
Yeah same. I tried everything :\
nayan deka said:
Flash aokp latest build
Click to expand...
Click to collapse
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
kidbao said:
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
Click to expand...
Click to collapse
There's an unofficial one here in the forum
https://forum.xda-developers.com/mo...aokp-rom-oms-substratum-t3748033/post75529247
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
kidbao said:
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
Click to expand...
Click to collapse
I don't know. I was just pointing out that we had one, lol. Not sure it will help you.
I see you "solved" it, lol
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
Not for me. As we've said, re-installing stock ROM doesn't seem to solve the problem for some people, but it's cool it did for you. Other forums are peppered with people experiencing the same SIM issue, some even apparently happening at random.
beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin...
Scholeggo said:
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
Click to expand...
Click to collapse
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
Scholeggo said:
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin..
Click to expand...
Click to collapse
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
beachfl said:
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
Click to expand...
Click to collapse
So, basically, to get back to original ROM, flash the following:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Compared to the original:
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
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
Yup, that list all looks exactly like what I did.
'sudo -s' .... no, you don't include that when running fastboot from Windows, it's a Linux thing. I'm not sure you have to, but I do always run adb/fastboot from a command prompt with admin priveleges when I'm using WIndows. which is kinda the same thing as 'sudo' on Linux.
Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Go to Android programs and scroll down to rsdlite 6.2.4
Edit: link corrected
madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Davey126 said:
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Click to expand...
Click to collapse
For sure. Comfort in fastboot is a must
madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Like some others, RSDLite couldn't see my E4 from Windows 10
Just download the Zip
Uncompress and install via Fastboot.
https://rsdsecure-cloud.motorola.co...190729&Signature=b98aq6ZhoCermo9Do/FI1FpK0cg=
Grom9A said:
Just download the Zip
Uncompress and install via Fastboot.
https://rsdsecure-cloud.motorola.co...190729&Signature=b98aq6ZhoCermo9Do/FI1FpK0cg=
Click to expand...
Click to collapse
Link is expired.
Spaceminer said:
Link is expired.
Click to expand...
Click to collapse
works fine here
dougdoindaia said:
works fine here
Click to expand...
Click to collapse
Definitely not working for me. Still says expired. It started to download but failed after a few seconds saying "forbidden".
Spaceminer said:
Definitely not working for me. Still says expired. It started to download but failed after a few seconds saying "forbidden".
Click to expand...
Click to collapse
ok for me, and still downloading
dougdoindaia said:
ok for me, and still downloading
Click to expand...
Click to collapse
It's weird. I tried using Firefox and got the same error. If I try to start the download on my mobile data it starts, but fails saying forbidden, and if I try on WiFi it doesn't even pull up the link.
Spaceminer said:
It's weird. I tried using Firefox and got the same error. If I try to start the download on my mobile data it starts, but fails saying forbidden, and if I try on WiFi it doesn't even pull up the link.
Click to expand...
Click to collapse
try use some download manager.
Im using free download manager
dougdoindaia said:
try use some download manager.
Im using free download manager
Click to expand...
Click to collapse
I think it has something to do with my network. I just tried Android Download Manager and got the forbidden error again. It looks like it'll download over LTE but not WiFi. I'm not about to use all my data trying to grab it though. I'll wait on a mirror I guess.
Working using desktop browser
I finally managed to grab it. Network was the problem. To anyone with the Jeter, this is also a no go. The bootloader won't accept the Pie boot.img. We're still waiting.
Spaceminer said:
I finally managed to grab it. Network was the problem. To anyone with the Jeter, this is also a no go. The bootloader won't accept the Pie boot.img. We're still waiting.
Click to expand...
Click to collapse
Try installing the last Oreo ROM for aljeter and then this rom
ok so i posted something here that was cause by a complete mess i made cus i mistakenly flashed oreo instead of pie, hahahhaha... i dont know how it didnt hard brick my phone but everything's ok now
---------- Post added at 03:01 AM ---------- Previous post was at 02:21 AM ----------
ok but now i have flashed the Pie stock and my phone only boot into bootloader. and baseband not found. everything is not ok at all...
blowingoff said:
ok so i posted something here that was cause by a complete mess i made cus i mistakenly flashed oreo instead of pie, hahahhaha... i dont know how it didnt hard brick my phone but everything's ok now
---------- Post added at 03:01 AM ---------- Previous post was at 02:21 AM ----------
ok but now i have flashed the Pie stock and my phone only boot into bootloader. and baseband not found. everything is not ok at all...
Click to expand...
Click to collapse
So this message goes out to you and all wanting Stock 9.0 Pie on Moto G6 Play.
I went looking for this update / flash for my G6. After a bit of searching, found it with great help from XDA forums
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%.
I recommend creating a backup of all your important files before beginning with this process.
I also recommend removing your Google account in the phone settings prior to doing all of this...
STOCK FIRMWARE MOTO G6 PLAY LINK HERE
Find appropriate one for your phone and region. For example - mine was in Official --> Retail --> ALJETER_RETAIL_9.0_PPP29.55-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip <-- this is the file I downloaded.
Your firmware MAY NOT be for download. It is upto you to find the correct one for your phone and region. I do not know all the codes for different regions. I know that aljeter = MOTO G6 Play. I have the Retail UK version - hence I used the Retail firmware. You may need to find somewhere other than the provided link for your firmware...
Please bear in mind that once you upgrade, you cant go back. So please make sure this is what you want to do.
Some notes;
1 - You can only flash a firmware that either exactly matches or exceeds your version. You cannot downgrade flash.
2 - the bit thats says _PPP indicates it is Pie 9.0. Look at different available downloads and you can see in contrast _OPP which means Oreo.
3 - Pie 9.0 fixed my problems I had with Oreo, namely the fingerprint scanner not working in Banking apps.
Install Motorola Driver - I used Motorola_Mobile_Drivers_v6.4.0 from HERE.
You will need adb and fastboot installed. A quick and easy way to sort is to install minimal_adb_fastboot_v1.4.3 - Download HERE or Google minimal_adb_fastboot_v1.4.3_setup.exe and you will find elsewhere to download.
Once you have downloaded your .zip firmware and have Moto Drivers and adb / fastboot all setup, you need to extract the contents of the zip file to the folder where minimal_adb_fastboot_v1.4.3_setup.exe was installed. For me this was C:\Program Files (x86)\Minimal ADB and Fastboot.
Download flash_rom_fixed.zip Attachment at the end of this post - Kudos / All thanks to the user vortrum, here on XDA.
Extract the flash_rom_fixed.bat from inside the zip file and place it into the same folder you extracted your .zip firmware into.
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.
Hopefully - on connection of the USB cable you will hear the Windows ding (or whatever noise you have) that lets you know USB device connected.
TIP!: To fully confirm - you can open a Admin (elevated) CMD window, navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder, and type in Fastboot devices -if USB connection is successful, then your phones Serial will be displayed. If nothing is shown, I would reboot Windows machine and try again.. Also, so you know, you can continue with the instructions below without USB connection confirmation. If there is no connection, then the below will fail anyway, without harm..
Run / open / double click the file flash_rom_fixed.bat and the firmware will be flashed to your phone - this will totally wipe your phone and reboot it once finished.
Alternative / similar instructions for install;
HOW TO INSTALL STOCK ROM IN MOTO G6:
Download Moto G6 Play Stock Firmware.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot install folder. (C:\Program Files (x86)\Minimal ADB and Fastboot or wherever you installed it if different)
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 (you can copy paste it all and then press Enter OR copy and paste a line at a time, then press Enter after each line, once each operation is complete. I highly recommend using the flash_rom_fixed.bat file to do this for you quickly and easily ):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.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 system system.img_sparsechunk.4
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
Hoped there will be one for reteu so still either wait or root and install GSI like treble or somethimg.
Dead link
alchemist83 said:
So this message goes out to you and all wanting Stock 9.0 Pie on Moto G6 Play.
I went looking for this update / flash for my G6. After a bit of searching, found it with great help from XDA forums
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%.
I recommend creating a backup of all your important files before beginning with this process.
I also recommend removing your Google account in the phone settings prior to doing all of this...
STOCK FIRMWARE MOTO G6 PLAY LINK HERE
Find appropriate one for your phone and region. For example - mine was in Official --> Retail --> ALJETER_RETAIL_9.0_PPP29.55-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip <-- this is the file I downloaded.
Your firmware MAY NOT be for download. It is upto you to find the correct one for your phone and region. I do not know all the codes for different regions. I know that aljeter = MOTO G6 Play. I have the Retail UK version - hence I used the Retail firmware. You may need to find somewhere other than the provided link for your firmware...
Please bear in mind that once you upgrade, you cant go back. So please make sure this is what you want to do.
Some notes;
1 - You can only flash a firmware that either exactly matches or exceeds your version. You cannot downgrade flash.
2 - the bit thats says _PPP indicates it is Pie 9.0. Look at different available downloads and you can see in contrast _OPP which means Oreo.
3 - Pie 9.0 fixed my problems I had with Oreo, namely the fingerprint scanner not working in Banking apps.
Install Motorola Driver - I used Motorola_Mobile_Drivers_v6.4.0 from HERE.
You will need adb and fastboot installed. A quick and easy way to sort is to install minimal_adb_fastboot_v1.4.3 - Download HERE or Google minimal_adb_fastboot_v1.4.3_setup.exe and you will find elsewhere to download.
Once you have downloaded your .zip firmware and have Moto Drivers and adb / fastboot all setup, you need to extract the contents of the zip file to the folder where minimal_adb_fastboot_v1.4.3_setup.exe was installed. For me this was C:\Program Files (x86)\Minimal ADB and Fastboot.
Download flash_rom_fixed.zip Attachment at the end of this post - Kudos / All thanks to the user vortrum, here on XDA.
Extract the flash_rom_fixed.bat from inside the zip file and place it into the same folder you extracted your .zip firmware into.
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.
Hopefully - on connection of the USB cable you will hear the Windows ding (or whatever noise you have) that lets you know USB device connected.
TIP!: To fully confirm - you can open a Admin (elevated) CMD window, navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder, and type in Fastboot devices -if USB connection is successful, then your phones Serial will be displayed. If nothing is shown, I would reboot Windows machine and try again.. Also, so you know, you can continue with the instructions below without USB connection confirmation. If there is no connection, then the below will fail anyway, without harm..
Run / open / double click the file flash_rom_fixed.bat and the firmware will be flashed to your phone - this will totally wipe your phone and reboot it once finished.
Alternative / similar instructions for install;
HOW TO INSTALL STOCK ROM IN MOTO G6:
Download Moto G6 Play Stock Firmware.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot install folder. (C:\Program Files (x86)\Minimal ADB and Fastboot or wherever you installed it if different)
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 (you can copy paste it all and then press Enter OR copy and paste a line at a time, then press Enter after each line, once each operation is complete. I highly recommend using the flash_rom_fixed.bat file to do this for you quickly and easily ):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.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 system system.img_sparsechunk.4
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
actually i forgot to mention, i somehow got confusex and on that day i tried to flash Oreo stock rom and that was the problem hahanaja
G6 play Jeter OTA update to Pie is out. Finally!!!
Thanks!!
i had my moto g6 play RETLA stored, finally with your instructions i have android 9.0
alchemist83 said:
So this message goes out to you and all wanting Stock 9.0 Pie on Moto G6 Play.
I went looking for this update / flash for my G6. After a bit of searching, found it with great help from XDA forums
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%.
I recommend creating a backup of all your important files before beginning with this process.
I also recommend removing your Google account in the phone settings prior to doing all of this...
STOCK FIRMWARE MOTO G6 PLAY LINK HERE
Find appropriate one for your phone and region. For example - mine was in Official --> Retail --> ALJETER_RETAIL_9.0_PPP29.55-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip <-- this is the file I downloaded.
Your firmware MAY NOT be for download. It is upto you to find the correct one for your phone and region. I do not know all the codes for different regions. I know that aljeter = MOTO G6 Play. I have the Retail UK version - hence I used the Retail firmware. You may need to find somewhere other than the provided link for your firmware...
Please bear in mind that once you upgrade, you cant go back. So please make sure this is what you want to do.
Some notes;
1 - You can only flash a firmware that either exactly matches or exceeds your version. You cannot downgrade flash.
2 - the bit thats says _PPP indicates it is Pie 9.0. Look at different available downloads and you can see in contrast _OPP which means Oreo.
3 - Pie 9.0 fixed my problems I had with Oreo, namely the fingerprint scanner not working in Banking apps.
Install Motorola Driver - I used Motorola_Mobile_Drivers_v6.4.0 from HERE.
You will need adb and fastboot installed. A quick and easy way to sort is to install minimal_adb_fastboot_v1.4.3 - Download HERE or Google minimal_adb_fastboot_v1.4.3_setup.exe and you will find elsewhere to download.
Once you have downloaded your .zip firmware and have Moto Drivers and adb / fastboot all setup, you need to extract the contents of the zip file to the folder where minimal_adb_fastboot_v1.4.3_setup.exe was installed. For me this was C:\Program Files (x86)\Minimal ADB and Fastboot.
Download flash_rom_fixed.zip Attachment at the end of this post - Kudos / All thanks to the user vortrum, here on XDA.
Extract the flash_rom_fixed.bat from inside the zip file and place it into the same folder you extracted your .zip firmware into.
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.
Hopefully - on connection of the USB cable you will hear the Windows ding (or whatever noise you have) that lets you know USB device connected.
TIP!: To fully confirm - you can open a Admin (elevated) CMD window, navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder, and type in Fastboot devices -if USB connection is successful, then your phones Serial will be displayed. If nothing is shown, I would reboot Windows machine and try again.. Also, so you know, you can continue with the instructions below without USB connection confirmation. If there is no connection, then the below will fail anyway, without harm..
Run / open / double click the file flash_rom_fixed.bat and the firmware will be flashed to your phone - this will totally wipe your phone and reboot it once finished.
Alternative / similar instructions for install;
HOW TO INSTALL STOCK ROM IN MOTO G6:
Download Moto G6 Play Stock Firmware.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot install folder. (C:\Program Files (x86)\Minimal ADB and Fastboot or wherever you installed it if different)
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 (you can copy paste it all and then press Enter OR copy and paste a line at a time, then press Enter after each line, once each operation is complete. I highly recommend using the flash_rom_fixed.bat file to do this for you quickly and easily ):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.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 system system.img_sparsechunk.4
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