Database Develop

Looking for XT1094 5.1 Stock Image

Hi,
I've given my minor daughter a Republic XT1094 with firmware version lpe23.32-39-R-28 (5.1). I rooted it and flashed TWRP so that parental control software could be installed (please don't address the ethics here as there was a child safety issue). Unfortunately, she managed to mess up the phone badly enough that I need to flash back to stock image to get the parental control software back on there. I grabbed a pds.img before this happened but, unfortunately, didn't get a NAND backup.
Any idea where I can find a stock image and how I can flash it?
Thanks,
Doc

Try https://firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1094/VICTARA_REPW_XT1094_5.1_LPE23.32-39-R-28_cid6_CFC.xml.zip using fastboot.
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash 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
Good luck.

Thanks. Worked perfectly.

datawrhsdoc said:
Hi,
I've given my minor daughter a Republic XT1094 with firmware version lpe23.32-39-R-28 (5.1). I rooted it and flashed TWRP so that parental control software could be installed (please don't address the ethics here as there was a child safety issue). Unfortunately, she managed to mess up the phone badly enough that I need to flash back to stock image to get the parental control software back on there. I grabbed a pds.img before this happened but, unfortunately, didn't get a NAND backup.
Any idea where I can find a stock image and how I can flash it?
Thanks,
Doc
Click to expand...
Click to collapse
Wait, how were you able to flash TWRP on XT1094 with 5.1 if the bootloader can't be unlocked?

Downgrade Pie To Oreo ?

I regret my English but I need your help update my X4 Oreo 8.1 Patch November to Pie 9.0, I have a da Fiio Q1 mark II which worked perfectly in Oreo 8.1 through OTG, after updating this stopped working normally , it connects and disconnects only until the smartphone restarts, is there a way to go back to oreo? It is not Fi project

Yes, the way is:
1. unlock bootloader (this erase all user data / internal storage)
2. flash Oreo full fastboot package

Comby_sk said:
2. flash Oreo full fastboot package
Click to expand...
Click to collapse
Someone might need to correct me, but I don't think you want to attempt to "downgrade" either of partition - gpt.bin or bootloader - bootloader.img (possibly others) so one doesn't potentially brick the device.
This is how it was on older Moto devices I owned.

jbaumert said:
Someone might need to correct me, but I don't think you want to attempt to "downgrade" either of partition - gpt.bin or bootloader - bootloader.img (possibly others) so one doesn't potentially brick the device.
This is how it was on older Moto devices I owned.
Click to expand...
Click to collapse
Flashing full fastboot package with correct script and unlocked bootloader doing this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
I downgraded many times my X4 from Pie to Nougat or from Pie to Oreo.

Comby_sk can I do it with this scribt?!
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot flash modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.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.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
PAUSE
fastboot reboot
RAW Paste Data

@tomtom_38 yes, you do.

many thanks

MetroPCS Moto e5 play xt1921-3 baseband / imei missing

Attempted to root & install TWRP, went to revert to stock, through about 6 different ROM variants for this phone, none of which have restored either the imei or baseband, some help/ insight would be amazing right about now

Did you ever figure this out, if not i can help you, i have had to restore both of them about 50 times, and i have an automated way of doing it, at this point. hit me up if you still need help.

for those having this problem, this is only for the MetroPCS variant xt1921-3 James model, flash back to stock build JAMES_T_OCP27.91-150-5-1_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC from the bootloader using these commands -
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
fastboot reboot
- after you flash and reboot, it will boot up normally, setup up a wifi connection on it and it will tell you there is a new security update. Let it download and install the update, once finished, it will boot up and your baseband and IMEI will be working again.

What did you do to mess those up? I just got this phone, used to love doing this stuff, but it's become such a pain in the a$$ to just use a device I paid for like I want. I don't want that kind of problem. On a Samsung, that problem woud occur if your baseband and modem didn't match properly and the fix was to reflash the correct ones. Might not help you in this case tho.
Sent from my [device_name] using XDA-Developers Legacy app

Touchscreen not working after flash, Ali Moto G6

Hello,
I followed the steps to install TWRP correctly, and then flashed ALI_RETAIL_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that i got from https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ and the process worked correctly. However, I foolishly thought I had flashed the wrong build and then flashed ALI_OPS27.82-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that I got from https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
Now my phone boots fine, but the touchscreen does not work at all, neither in TWRP nor when booted into the firmware. Is there any hope?
Model is ali XT1925-6
If I burnt out a part, what parts are they and how difficult will it be to replace them?
Edit: I now realize that my carrier channel is retus, and I installed retail. However, the touchscreen did not fail on that rom

II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works

madbat99 said:
II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works
Click to expand...
Click to collapse
Thanks for your response,
I installed androidfilehost.com/?fid=818222786056029922 from the second thread.
I tried reflashing the first rom, but the touchscreen does not work there either. I've just downloaded and installed the correct rom, still no dice
Is it possible that the second rom burnt my digitizer?
Edit: the fingerprint sensor doesn't respond on the setup screen either, although I'm not sure if thats because it isn't working or it doesnt do anything on the setup screen

I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
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 bluetooth BTFM.bin
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

fisher_1 said:
I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
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 bluetooth BTFM.bin
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Download the "newest" firmware for your device with matching SKU and software channel. Don't use someone else's script. The commands for flashing the firmware are in the flashfile.xml in the firmware zip. Extract it and check the commands. You can use XML to batch program to create your own batch script if you must use a script.
It's unlikely that flashing a firmware broke your hardware.
If it's software related, flashing the correct firmware should fix it.
If it's a hardware problem, then it won't. But official firmware isn't likely to cause hardware failure
The firmware package in the first post of that thread is pretty old.

Unfortunately it still is not working. I used the commands from flashfile.xml and flashed XT1925-6_ALI_RETUS_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, the correct firmware, but nothing has changed.
On a side note, when I flash a file, I get the message (bootloader) is-logical: (partitionName) not found, althought I get an OKAY response so I'm assuming it flashes correctly.

I'm having the same issue, got the phone on July 12 and immediately started the unlocking/rooting process (that's what I bought the device for) following dejello's guide. Everything went perfect, phone was working all right for 2 days then on Monday morning after using the device for a while, I placed it in an upper pocket of my backpack drove home and next thing I know the touch screen isn't working, not even on TWRP . Hardware damage seems very unlikely on my case. I did a factory reset using a mouse, but I haven't been able to flash stock back. I'll try that later today and see what happens.
UPDATE: It was a hardware issue. Came home and flashed back to stock, still had no touch response. Since my software troubleshoot had no success I decided to give hardware a shot. I followed this video to disassemble the phone. I started tweaking the digitizer connector. With the phone still disassembled I turned it on and still no touch. Disconnected it again and blew some air with a hair dryer to it trying to remove any debris, connected it again and still no touch. Repeated the process a couple times and eventually the screen was responsive again. I think this specific device came with something loose or some dirt on it.

Failed to verify Hab Image Boot

First im trying to reinstall stock firmware on a model XT1925-3, from a friend.
It was stuck at Moto Logo, i tried everything you could imagine to make it work. Nothing happens. The things I tried:
-It have locked bootloader (i cant unlock because i cant boot to "Allow OEM").
-Tried all 8 RETBR firmwares (https://mirrors.lolinet.com/firmware/moto/ali/official/RETBR/) and none worked.
-Trying the following commands:
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 flash recovery recovery.img
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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
It goes very well, but after restart, it backs to fastboot screen and cant boot.
-Tried another cable, tried another PC, tried another port
-Attached the screen it is now
If theres anything you can do to help me. I appreciated

There's nothing wrong with your cable, your PC or something else! Otherwise you can't even process the first the command in fastboot.
So first thing I would do is booting into recovery. Although it's the stock one it will be very useful to get detailed information in your case.
Once in fastboot mode use the Vol -/+ keys to navigate to reboot to recovery and press power. Then have a look at the logs provided by the recovery. There should be two different kinds of logs - the kernel log and the recovery.log. Choose kernel.log (maybe it's called last_dmsg.log or sth like that). It provides the most detailed information on Android and why you're stuck in a bootloop. Be aware that it has more than one page which will be shown up. Have a look at the left corner on the bottom. Don't expect to find the major error on the last lines, but somewhere in the last 150 lines.
That's one thing you can do.
Another advise is to give the repair tool a chance which is mentioned in your screenshot. This is a really good option in your case.
Good luck!!