july update on fi version - Moto X4 Questions & Answers

i am using rooted phone on fi version. i see a recent rom on mirrors.lolinet for this update. the file has 'no erase modem' in its title. does this mean that the lines 'erase modemst1' and erase modemst2 should be removed from the flash-all.sh script ? if anyone knows. i am getting the annoying update attempts that will fail on the rooted phone. thanks.

The quick way to get rid of that message is using Titanium Backup's Freeze! option and freezing the Motorola Update Services app (I think that's what it's called. I do this when I don't have time update right away.
Otherwise, you can leave the flash script the same.

thanks for reply. i took a look at the flashfile.xml inside the zip and there is no modem file there. so i think probably its best to remove the erase modemst lines from the bat/sh file to flash with. this is in fact different from the previous contents of the flashfile.xml in previous releases. i'll get to it over the weekend and report back how it goes.

glenb77 said:
thanks for reply. i took a look at the flashfile.xml inside the zip and there is no modem file there. so i think probably its best to remove the erase modemst lines from the bat/sh file to flash with. this is in fact different from the previous contents of the flashfile.xml in previous releases. i'll get to it over the weekend and report back how it goes.
Click to expand...
Click to collapse
There is a modem file included in the firmware package. It's called NON-HLOS.bin and is flashed to the modem partition:
fastboot flash modem NON-HLOS.bin
You are correct that modemst1 and modemst2 should not be erased during installation.

i did the update over the weekend and commented out the lines to erase modemst as above and phone seems fine. it's great to have an image up on the mirror so quickly, thanks to all responsible for that. in the past i flashed backed to earlier images and went through the ota update process which takes a long time.

glenb77 said:
i did the update over the weekend and commented out the lines to erase modemst as above and phone seems fine. it's great to have an image up on the mirror so quickly, thanks to all responsible for that. in the past i flashed backed to earlier images and went through the ota update process which takes a long time.
Click to expand...
Click to collapse
I used the same flash-all script that I always used which I had commented out the data wipe. I DIDN'T comment out there modem wipe lines, and it worked without any issues. ?
I agree, it is great that I didn't have to bother with the OTA part!

glenb77 said:
i am using rooted phone on fi version. i see a recent rom on mirrors.lolinet for this update. the file has 'no erase modem' in its title. does this mean that the lines 'erase modemst1' and erase modemst2 should be removed from the flash-all.sh script ? if anyone knows. i am getting the annoying update attempts that will fail on the rooted phone. thanks.
Click to expand...
Click to collapse
Ouch, wish I would've seen this before the flash. Lol. I may have service still. Now I can't figure out how to get it back

Related

[Q] xt1056 Sprint, wont connect to network please help

while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.
I attempted the slapmymoto method in the motoxtool kit and selected verizon
bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?
bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device
i restored completely to stock and am still having the same issue. please help
bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.
I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied
ok sorry i left out a command i think i know what is going on
Code:
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
dray_jr said:
ok sorry i left out a command i think i know what is going on
Code:
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old
sorry but how do I remove the var line?
ive got it figured out thank you for your help

[IMG] LXE22.46-11 Pure Edition Stock Boot, Recovery and System.img [Lollipop 5.0]

Here is the fully stock Boot.img, Recovery.img and System.img. There are no modifications to any of these. This is all we have until Motorola releases full factory images for Lollipop 5.0.
For the XT1095 Pure Edition ONLY
BUILD: LXE22.46-11 (22.21.11)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.21.11_BOOT_RECOVERY_SYS.zip
md5: 43888F4EAB74600E6D6DF41FF202C9BA
here's a mirror
https://mega.co.nz/#!a9hymLCD!ek2VVQNPGmUpNHFl6WIQe8znsFtUBjbsvTu0-TyORnM
Previous builds
BUILD: LXE22.39-6 (22.11.6)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.11.6_BOOT_RECOVERY_SYS.zip
md5: 6A527AFB1DEED2248AE2D3B4ACCF04ED
here's a mirror
https://mega.co.nz/#!H0wn2LoT!hHqhasTUnLjxMxACvODWcRIrtm3jTGjg1MEqxZfP5lo
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, catches on fire or it starts WWIII. Use at your own risk.
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
godutch said:
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
Click to expand...
Click to collapse
you are doing it wrong...
mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
ok, how can we do it?
thx
overon37 said:
ok, how can we do it?
thx
Click to expand...
Click to collapse
by using mfastboot. this is for advanced users...
yes, i got it, but, can i flash it over XT1092 with Kitkat?
^^I have a conversion guide, that'd help you for sure
mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
so how i am supposed to flash this then?
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Can someone provide the bootanimation file in system/bin?
Links dead?
Devans32 said:
Links dead?
Click to expand...
Click to collapse
Nope. they both seem to work here.
updated
for the official 22.21.11 Build.
mirror up shortly
Ok now I am getting a parse invalid file error when I try to flash the system image.
Edit; fixed. Found right files and up and running.
Sent from my Nexus 6 using XDA Free mobile app
Chronzy said:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Kallb123 said:
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Click to expand...
Click to collapse
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Chronzy said:
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Click to expand...
Click to collapse
Yes, got the new mfastboot, but I've tried with old as well as mfastboot v1. I was trying to flash .11 but I got this error, so I came here to use these files but also got this error :/
EDIT: Flashed KK and upgraded .11 from there. Can't get a signal though, even after flashing my modem back..
EDIT2: erase modemst1 and modemst2 and then flashing my fsg and modem worked
Chronzy said:
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Click to expand...
Click to collapse
You did this from -6 rooted? With stock recovery or TWRP?
zgroten said:
You did this from -6 rooted? With stock recovery or TWRP?
Click to expand...
Click to collapse
That was the method I used to upgrade from KK to .6. I don't understand your recovery question. All this is done in bootloader.
I think you guys would benefit from SolarTrans' guide in the "general" section... http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Anyone else have issues
I'm on 22.39-6 and I am having issues when the phone. Anyone else have the issue where the home and menu buttons randomly disappear? Or text messages don't appear? The only fix was to reboot the phone. I also have unresponsive issues randomly when the phone is plugged to AC power and charging. Just wondering if I'm the only one with these issues. I'm going to flash the new build, but just wondering.

Telus XT1097 moto x --- Missing my baseband! Help!

Soooo i was a big dumby and i wrote over the modem in order to get the update.
Now i have no signal/service available , or compatible baseband flashed.
Wifi works, everything else is amazing !!
Currently
Android 5.0
Baseband: Unknown <------
System version: 22.11.6.victara_tmo.tmo.en.US tkpca
Build Number: LXE22.39-6
If any one successfully backs up the telus baseband could you please post it ?!!?
So screwed at the moment
If you can tell me how to do so I would be happy to.
---------- Post added at 03:32 PM ---------- Previous post was at 02:51 PM ----------
pipesdl said:
If you can tell me how to do so I would be happy to.
Click to expand...
Click to collapse
I might have figured it out, use at your own risk.
https://drive.google.com/file/d/0B5ErTnQGFRMaVjRaWDV2dFlqMzg/view?usp=sharing
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Ah, didn't realize two files were needed. Links below.
FSG
https://drive.google.com/file/d/0B5ErTnQGFRMaN0JjLUx1RDVZakk/view?usp=sharing
NON-HLOS
https://drive.google.com/file/d/0B5ErTnQGFRMaWHVXZEhwS2UwU2M/view?usp=sharing
pipesdl said:
Ah, didn't realize two files were needed. Links below.
FSG
NON-HLOS
[
Click to expand...
Click to collapse
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
I think I did extract it with an mbn extension, don't know if it will make a difference but I'll upload shortly.
Let me know if it works.
https://drive.google.com/file/d/0B5ErTnQGFRMaQk9fcC05amJvTDg/view?usp=sharing
OscarAlert said:
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
Click to expand...
Click to collapse
You need the following commands. Just keep your mbn file.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I would love to know if those modem files work for the Telus phone after flashing, as the only thing holding me back is that it currently won't let me back up my own. If it does then lollipop here I come!
Those two files worked! Thanks so much to everyone who helped out in this thread. Successfully running Lollipop on my Telus Moto X now!
Awesome, can you let me know what steps you followed in addition to the steps above?
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Kodiak1 said:
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Click to expand...
Click to collapse
I'm pretty sure that in order to make an image of your baseband files, you need to be rooted. Root access is granted by SuperSU. As for the extensions on the fsg file, it doesn't matter what you call it. You just have to be consistent when copying it or applying it back to your device. I think someone posted on the forum using mbn and then used bin for applying it, which for obvious reasons wouldn't work.
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Take pity on me
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Update on xt1092 worked! I did this:
1. Downloaded the 4.4.4 system image from xt1905 (first post for download link)
2. Extracted the zip
3. flashed over mfastboot.exe
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
4. sideloaded the OTA update from first post
5. reboot
6. flashed back the original modem and fsg from xt1902, without erasing modemst1 and modemst2 -> https://www.androidfilehost.com/?fid=95784891001608300
Click to expand...
Click to collapse
Then realising I had no signal I followed this post:
YES!
I finally have Lollipop on my XT1092!!
I followed steff999's guide but encountered several problems with the modem and data connections etc.
I just couldn't figure out why flashing the XT1092 modem files didn't work.
Then I went back to my original firmware and did the procedure again.
But now I did not let it boot after the OTA Update and directly booted into fastboot mode and flashed the modem and fsg files.
Then after reboot I immediately had mobile service. IMEI and Baseband is back again.
I use Linux and it is very easy with Linux.
In a terminal just go to the folder with the files (no matter where they are!!).
After getting Android SDK I did:
Code:
$ sudo apt-get install android-tools-fastboot <<-- to install fastboot
$ cd /directory with your files...<<--- choose your folder
$ fastboot flash logo logo.bin
etc
after flashing the files put OTA.zip on phone. Go in recovery mode and apply update.
Then when it reboots directly go in fastboot mode and type:
$ cd /directory with your XT1092 modem files/
$ fastboot flash modem NON-HLOS.bin
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
now it boots into lollipop and it should recognize your sim card.
This is how it worked for me with Linux. Should be similar with Windows but I think the files for flashing have to be in fastboot directory then.
I did not use erase modem commands
I hope this will give hope back to people who encountered similar problems with the modem. I was about to give up but decided to give it a last try.
Click to expand...
Click to collapse
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
THE-M1GHTY-BUKO said:
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Then realising I had no signal I followed this post:
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
Click to expand...
Click to collapse
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
drolgnir said:
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
Click to expand...
Click to collapse
My problem is now fixed, thankyou.
For future reference for others, how did you fix the problem?
Sent from my XT1095 using Tapatalk
halfez said:
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Click to expand...
Click to collapse
Any chance you have a copy of the modem files for your moto x 2014 (XT1097 ) on Wind? I flashed the T-Mobile 5.0 xt1095, and don't think I properly backed up my files.
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
halfez said:
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
Click to expand...
Click to collapse
Come on, just do it!

baseband missing

Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.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 system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi

Soft bricked XT1052

Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?
I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...
OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed
varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?
Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.

Categories

Resources