Database Develop

[Help! I just bought it] Please help me get WIFI and/or the any of my SIMs working!

Hi!
I have a Moto G dual sim and I recently updated my ROM to Lollipop XT1064 (biggest mistake in recent history!)
Things went really well for a day then I made two mistakes:
1- SU Binary required update so I told it I have TWRP recovery when I did not. that made my phone freeze and kept restarting before getting to the moto logo.
2- I then decided to flash back to 1068 to redo the whole thing, but I mistakenly used Moto x (it was a version that worked on Moto g single sim, I think.. not sure anymore)
Since then I have tried flashing 1068 4.4.4 stock ROM and every time i end up with no network signal (wifi NOR the both SIMs.)
I was able to flash modem files successfully and in my pursuit to fix wifi I had to flash other roms but now I cannot even fix the SIM signal.
Please note that I have no data that I care about, I want ANY ROM that make my phone more valuable than a paperweight.
To sum up:
- OEM is unlocked
- I get flash and get into custom recovery
- I am able to flash stock ROMs
- Was not able to get any ROM where WIFI works (not able to enable it. never worked since the problem started)
- Was able once to get the SIMs to work (were not ale to do it again although I repeated the same steps which were
Steps I used to flash stock ROMs:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.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 modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Steps to attempt to enable SIMs:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot reboot
I hope i provided enough info... if not, please let me know what to add.
Many thanks in advanced for helping or taking the time to read words of a desperate human being!

Moto X XT1052, Asia Retail Version, not showing any network.

Device: Moto X XT1052 Asia Retail
Bootloader Status: Unlocked
Current OS : Stock Lollipop ROM--XT1052 Retail Asia (Version: 222.27.5.ghost_row.AsiaRetail.en.03)--
Problem: Phone not showing any network signal
The problem started couple of weeks back. I went roaming, so put the phone in flight mode for a whole day and when I came back to non-roaming region turned the flight mode off. But then the network signal wouldnt come back. I'm not sure if this triggered the problem. But this is when it happened.
Ive been using CM12.1 OFFICIAL Nightly ROM then.
I tried changing the ROMs, RESULT : STILL NO NETWORK SIGNAL
I tried going back to STOCK( both kitkat and lollipop) RESULT : STILL NO NETWORK SIGNAL
I tried changing the radio firmware RESULT : STILL NO NETWORK SIGNAL
I cant even register on a network manually, no networks are shown when searched manually.
IMEI havent changed.
Now any help would be much appreciated, THANKS

I have same issue as yours too.
Contacted motorola,they asking me to send it to service centre.
Did all the step like downgrade and upgrade,change the modem etc etc,no success.seems like the modem hardware got problem.can read my sim card,but network not up.
Sent from my Moto X using Tapatalk

ershinadh said:
Device: Moto X XT1052 Asia Retail
Bootloader Status: Unlocked
Current OS : Stock Lollipop ROM--XT1052 Retail Asia (Version: 222.27.5.ghost_row.AsiaRetail.en.03)--
Problem: Phone not showing any network signal
The problem started couple of weeks back. I went roaming, so put the phone in flight mode for a whole day and when I came back to non-roaming region turned the flight mode off. But then the network signal wouldnt come back. I'm not sure if this triggered the problem. But this is when it happened.
Ive been using CM12.1 OFFICIAL Nightly ROM then.
I tried changing the ROMs, RESULT : STILL NO NETWORK SIGNAL
I tried going back to STOCK( both kitkat and lollipop) RESULT : STILL NO NETWORK SIGNAL
I tried changing the radio firmware RESULT : STILL NO NETWORK SIGNAL
I cant even register on a network manually, no networks are shown when searched manually.
IMEI havent changed.
Now any help would be much appreciated, THANKS
Click to expand...
Click to collapse
If you did
mfastboot flash modem NON-HLOS.bin
during your return to stock operation, then this shouldn't be happening unless you've got some H/W problem. Could you try doing the whole thing once again?
This (with some unnecessary steps) is what I used to get my phone back to stock when I had trouble.
mfastboot devices
pause
mfastboot oem fb_mode_set
pause
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
pause
mfastboot reboot-bootloader
pause
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
pause
mfastboot flash logo logo.bin
pause
mfastboot flash boot boot.img
pause
mfastboot flash recovery recovery.img
pause
mfastboot flash system system.img
pause
mfastboot flash modem NON-HLOS.bin
pause
mfastboot erase modemst1
mfastboot erase modemst2
pause
mfastboot flash fsg fsg.mbn
pause
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
pause
See if this works for you. CM12 etc won't work if your modem firmware isnt properly installed. They replace system, not the hardware related things.

soumen08 said:
If you did
mfastboot flash modem NON-HLOS.bin
during your return to stock operation, then this shouldn't be happening unless you've got some H/W problem. Could you try doing the whole thing once again?
This (with some unnecessary steps) is what I used to get my phone back to stock when I had trouble.
mfastboot devices
pause
mfastboot oem fb_mode_set
pause
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
pause
mfastboot reboot-bootloader
pause
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
pause
mfastboot flash logo logo.bin
pause
mfastboot flash boot boot.img
pause
mfastboot flash recovery recovery.img
pause
mfastboot flash system system.img
pause
mfastboot flash modem NON-HLOS.bin
pause
mfastboot erase modemst1
mfastboot erase modemst2
pause
mfastboot flash fsg fsg.mbn
pause
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
pause
See if this works for you. CM12 etc won't work if your modem firmware isnt properly installed. They replace system, not the hardware related things.
Click to expand...
Click to collapse
I did that before...
I think my one h/w already dead.
Haha
Sent from my Moto X using Tapatalk

raff28 said:
I did that before...
I think my one h/w already dead.
Haha
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Ah well, that sucks then. All the best!

It band problem Try dfs mode and install intall again new band from there Or put ur phone in rusim mode

XT1064 Bricked

Hello.
Lately my device has failed to stay on for long, and yesterday my phone is booting to the bootlogo while charging, and after five seconds it blackscreens and repeats.
I cannot boot into any state but fastboot, and I have already tried every option in the fastboot menu, including restoring to stock through fastboot using a Windows 10 PC.
The phone changed the bootlogo correctly to the unlock warning, but still fails to boot.
Any help is appreciated.

Flash a custom rom....
Youtube helps how to do

When my xt1064 bricked (rom stock) I installed Lineage.
You should try that.

I had a very similar thing on my Moto G2
Went totally flat using it in the car, while attempting to charge off the car and then off a powerpack
Just booted as far as the unlocked bootloader screen and then rebooted.
I could get into fastboot, but when I tried to get into recovery TWRP, it hung on the TWRP splash screen.
I tried all sorts of things, including disassembling and disconnecting the battery and charge it on a bench PSU (with current and voltage limiters)
Still no good, so I realised the battery was not the problem...
Eveuntually I gave up recovering the files, booted into fastboot, re-installed the stock rom, but it still didnt work
However if I erased the cache and the userdata partition it came back to life
So..
I'd initially suggest getting into fastboot and erasing the cache partition.
mfastboot erase cache
If its still no good, try erasing the user data partition as well
mfastboot erase userdata
If that still fails, get hold of the stock Lollipop ROMs, and flash the whole lot using mfastboot e.g.
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
mfastboot flash partition ROM_FILES/gpt.bin
mfastboot flash motoboot ROM_FILES/motoboot.img
mfastboot flash logo ROM_FILES/logo.bin
mfastboot flash boot ROM_FILES/boot.img
mfastboot flash recovery ROM_FILES/recovery.img
mfastboot flash system ROM_FILES/system.img_sparsechunk.0
mfastboot flash system ROM_FILES/system.img_sparsechunk.1
mfastboot flash system ROM_FILES/system.img_sparsechunk.2
mfastboot flash system ROM_FILES/system.img_sparsechunk.3
mfastboot flash modem ROM_FILES/NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg ROM_FILES/fsg.mbn

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.