Database Users

[FAQ] for Kit kat and How to prepare for it (All Carriers)

If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.
With the Verizon Kit Kat roll out, and now that there is an ATT Kit Kat soak starting soon, so undoubtedly they and the other carriers will start getting it, I wanted to summarize some of the information found in these two main threads ->
http://forum.xda-developers.com/showthread.php?t=2534060
http://forum.xda-developers.com/showthread.php?t=2525495 (start at the back and work your way front because of some of the fluff from before the OTA hit)
This might make it easier for those Verizon users who haven't received Kit Kat yet, or those of you on other carriers as Kit Kat starts rolling out. These are the most common issues and questions I've seen asked....
You will lose root when you take the KitKat OTA.
There is no way to retain root while upgrading to Kit Kat Updated Root for KitKat released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
If your phone has a LOCKED BootLoader, you will not be able to root KitKit at this time. UPDATED Root for KitKat 4.4 has been released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Note: If you have an unlocked boot loader, or developer edition, root is obtainable. (see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP )
You must be unrooted, reverse the impacts of PwnMyMoto and/or RockMyMoto or you will be stuck in a boot loop when the OTA. (how to fix posted later)
Once on Kit Kat, you can't flash back to past firmware, unless you have an unlocked boot loader. (see the updates section below, and the SlapMyMoto threads)
You must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
there are several options to get back to "stock" without loosing your data. (posted later in this thread), some are more techincal, some are more noob friendly.
If you want to thether "for free", FoxFi doesn't work. Any past hacks that require root wont work, unless your phone has been Rooted update:see the EDITS & UPDATES section at the bottom of this post)
Kit Kat brings some style and status bar changes to be aware of. Like everything being WHITE, no more blue, no data traffic arrows, etc For more info please see -> http://www.androidpolice.com/2013/1...nd-only-shows-connectivity-in-quick-settings/
Note: If you have flashed your phone with another carrier's ROM, or have tried the previously leaked T-Mobile or ATT pre-release roms, these steps may not work!!
Motorola Fastboot, mFastboot, and android SDK fastboot... what's the difference?
When you install the ADB and Platform Tools from the AndroidSDK, you will also get a fastboot.exe. This standard fastboot.exe is compatible with most, if not all, Android devices to flash parts or partitions with. Unfortunately, that standard fastboot is limited on how big of files it can properly flash. In recent android devices, Motorola has surpassed the limits of fastboot, as such they have an "upgraded" or "tweaked" fastboot.
Having two fastboot.exe files, one that comes with the AndroidSDK install, and one from Moto, can get confusing, and presents a challenge. You can't put the Moto one into your PlatoformTools folder with the AndroidSDK one due to the same name. If you overwrite the AndroidSDK one with the Moto one (keeping the same file name of fastboot.exe) it could be overwritten with a future update of the Android SDK. Because of this, some have renamed the Moto fasboot.exe to mfastboot.exe. So if when you see reference to mfastboot.exe, they are talking about the Moto tweaked version of fastboot.exe that has been renamed so as to not overwrite the one included with AndroidSDK. Simple, right??
So, where can you get the Moto Fastboot.exe, or mfastboot.exe?
You can grab the Moto Fastboot.EXE from -> https://www.dropbox.com/s/kyqjzpjgamrepf1/fastboot.exe (Thanks to Cell Zealot) Note: you will want to rename this one before putting in your PlatformTools folder so future updates to the Android SDK doesn't overwrite it. Alternate download -> http://forum.xda-developers.com/showpost.php?p=47191012&postcount=115 Another way to get it is to request the GSM Developer Edition recovery image directly from Motorola (HERE) as they recently added the updated fastboot.exe along with minimal ADB support.
I take no responsibility for any issues, errors, problems, etc. you encounter while attempting to unroot, get back to stock, etc or using these instructions. Please backup your data BEFORE you attempt anything below!!
How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8 users have had issues.
You will need...
To know what version ROM is on your phone before you touch anything. On Phone... App Drawer -> Settings -> About... Make note of the build number.
Motorola Device Drivers -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Adb Drivers, Android Platform Tools from the Android SDK, some good tutorials -> http://forum.xda-developers.com/showthread.php?t=1830108 or see -> http://www.xda-developers.com/android/lightweight-adb-and-fastboot-installer/
Updated Moto fastboot if you will be doing things manually See above!
MicroUSB Cable.
NOTE: the GSM Moto X Developer Edition recovery image available by request from Motorola (HERE) has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need for the Adb Drivers and Android Platform Tools from the Android SDK.
NOTE2: The T-Mobile XT1053 Retail and Moto Maker versions use the same Rom/Recovery Image as the GSM Developer Edition X. The Verizon XT1060 Retail and MotoMaker versions use the same Rom/Recovery Images as the Verizon Developer Edition phones. The the recovery images are available by request directly from Motorola (HERE). Unlockibility of the bootloader is NOT part of the ROM or Recovery Images that we can flash, so flashing the Developer Edition ROM/Recovery images will NOT have an impact on unlocking your bootloader. This tip is just in case you would feel more comfortable downloading the ROM files directly from Motorola, or if sbf.droid-developers.org has problems again.
Then select from one of the following options...
Option 1 The "Moto X Tool Kit"
See -> http://forum.xda-developers.com/showthread.php?t=2477132
It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for yor phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.
Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).
Option 2 Fastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept the KitKat OTA without losing data/apps.
You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.
You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.) See above.
Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)
steps would be... (mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you unziped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and and be ready for the update.
NOTE: to combat a 401 ERROR while doing the update, some users have also had to flash do the following
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings
NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.
Follow this guide -> http://forum.xda-developers.com/showthread.php?t=2446515 using the latest ROM from your carrier. HOWEVER, before as part of STEP 4, while editing the XML file, also remove the line that says...
<step operation="erase" partition="userdata" />
Failure to remove this line will result in your data/apps/settings being erased from your phone.
Option 4... Fully flash your phone using RSDLite
Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.
Follow this guide -> http://forum.xda-developers.com/showthread.php?t=2446515 using the latest ROM from your carrier.
Option 5 Using mFastboot to manually flash your phone's firmware (without wiping data).
This is the same as using option 3, but usese Moto fastboot instead of RSD. This will not erase your data and apps.
You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.
You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.)
Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)
steps would be... (note: mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)
Unplug phone
Power down phone.
Hold Volume Down button and Power button.
After a few seconds release Power, you should be in fastboot menu on phone.
Connect phone to PC.
open command prompt and change to the folder you unziped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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 erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready for the update.
Main issues encountered during the Kit Kit upgrade install...
Boot loop while trying to install the update. This is usually caused by having used PwnMyMoto or RockMyMoto to root. Those tools replace the stock recovery which is needed to install the OTA. You must re-install the stock recovery with one of the above options.
Error 252 reported by the "update". Again this is related to having been rooted but not restoring to Stock
Error 401. One of your files still isn't stock. See the NOTE in option 2 above, or see -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315
Some apps haven't been upgraded to be Kit Kat Compatible... Foxfi, HBOGo, and others. You have to wait for the app vendor to update.
Some apps partially work.. WellsFargo app, I can't deposit a check via camera, but rest of app works. Again, we have to wait for the vendor to update it.
Hope this helps!!
EDITs & Updates: Here are a few more things found since the initial posting...
For those running the T-Mobile Pre-Release leak, I just wanted to link to this thread here -> Oficial tmobile KK over tmobile leak It pretty much summarizes the ability of using Option 3 and/or 4 above to flash TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip over the leaked T-Mobile pre-release rom. (Thanks beelzebu)
There are reports of Verizon Moto X (non-developer) users who took the KK 4.4 update yet were able to flash back to the previous 4.2.2 w/camera fix rom. Please see -> [Q] Return to JB from kitkat on Verizon Moto X (locked) for more details.
Be sure to keep up on the [BOUNTY/PLEDGE/NON-DEV VARIANTS] ROOT 4.4 for MOTO X ($325) as there is some rumblings that a root for Non-Developer Edition KitKat 4.4 might be being worked on.
Tethering options for ROOTED KitKat 4.4 (currently limited to unlocked bootloader)... so far there are two....
On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
(per -> http://forum.xda-developers.com/showthread.php?t=2449534 )
See -> Native tether for VZW DE 4.4 <- This works for rooted with locked boot loader too!!
Root for KitKit users who have a locked bootloader has been released. See -> SlapMyMoto 0.5c Beta (4.4 root, RW to system) (thanks Jcase!!)
When I re-downloaded the GSM Moto X Developer Edition KitKat recovery image recently, available by request from Motorola (HERE) I noticed it has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need to download the Adb Drivers and Android Platform Tools from the Android SDK.
If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.

well done sir! hopefully people actually read this because it will clear up a lot of the clog going on in the threads about kit kat. It was getting ridiculous trying to answer the same simple question a dozen times. Good write up.

thread Title changed. (forgot I had to be in advanced mode..)
Thanks, I stole your idea for thread title.

KidJoe said:
Looking at the thread title I wish I would have called it... Some lessons learned while preparing for and taking the kit kat update.
Click to expand...
Click to collapse
change it then ha. you can change your thread title sir.
i would call it something different personally. Like FAQ for Kit kat and How to prepare for it or something. there is a lot more than just lessons learned. This is a answer to all your simple questions thread. Or call it Read This before Asking Any questions about kit kat ota lol

Should help many people
Sent from my XT1058 using Tapatalk

fyi there are reports that you can downgrade to 4.2.2 on a locked bootloader from 4.4. I didn't think you could but i haven't tried but others are saying on another thread that you can
http://forum.xda-developers.com/showthread.php?p=47698477#post47698477

jayboyyyy said:
fyi there are reports that you can downgrade to 4.2.2 on a locked bootloader from 4.4. I didn't think you could but i haven't tried but others are saying on another thread that you can
Click to expand...
Click to collapse
My understanding is...
After taking OTA KK, there is no way (with locked bootloader) to revert to 4.2.2.
If you used T-Mo or ATT leaked pre-release 4.4, it depends on what/how you flashed it. i.e. Full Flash, used RSDLite to flash entire FXZ, or just used fastboot to flash "parts"
I am sure there were other posts discussing it. Just too busy at work right now to search for them.

KidJoe said:
My understanding is...
After taking OTA KK, there is no way (with locked bootloader) to revert to 4.2.2.
If you used T-Mo or ATT leaked pre-release 4.4, it depends on what/how you flashed it. i.e. Full Flash, used RSDLite to flash entire FXZ, or just used fastboot to flash "parts"
I am sure there were other posts discussing it. Just too busy at work right now to search for them.
Click to expand...
Click to collapse
thats what i thought as well but the link i posted in there shows someone saying he was on locked vzw which to my knowledge, they could only have taken the 4.4 ota from verizon, because the tmobile variants out there are not flashable with a locked bootloader.

jayboyyyy said:
thats what i thought as well but the link i posted in there shows someone saying he was on locked vzw which to my knowledge, they could only have taken the 4.4 ota from verizon, because the tmobile variants out there are not flashable with a locked bootloader.
Click to expand...
Click to collapse
So it seems. Weird. And totally not what I remember. But I don't mind being wrong about this one!!

Can I consider option 4: Factory Reset (in settings ) before install kit Kat OTA? (Bootloader locked and no root)
Enviado de meu XT1058 usando Tapatalk

rod.gui said:
Can I consider option 4: Factory Reset (in settings ) before install kit Kat OTA? (Bootloader locked and no root)
Enviado de meu XT1058 usando Tapatalk
Click to expand...
Click to collapse
If you are not rooted, and therefore haven't used any root needing apps to remove or otherwise mess with system files, there is no need to do anything.

KidJoe said:
So it seems. Weird. And totally not what I remember. But I don't mind being wrong about this one!!
Click to expand...
Click to collapse
flip side it seems that we will be able to have root since verizon may be the only carrier that allowed you to downgrade back to 4.2.2 and jcase is putting something together for it. I WILL BE SO STOKED. Verizon does a quick release, and royally screws up hahaha

this post saved me from wiping my phone :3

jayboyyyy said:
flip side it seems that we will be able to have root since verizon may be the only carrier that allowed you to downgrade back to 4.2.2 and jcase is putting something together for it. I WILL BE SO STOKED. Verizon does a quick release, and royally screws up hahaha
Click to expand...
Click to collapse
You do know that VERIZON has nothing to do with the security, boot images, or system files on the device. Though I could care less if people can go back/forth or if jcase releases a root. Also I love to bash Verizon as much as the next but in this instance, well, you seem to be barking up the wrong tree.

jimmydafish said:
You do know that VERIZON has nothing to do with the security, boot images, or system files on the device. Though I could care less if people can go back/forth or if jcase releases a root. Also I love to bash Verizon as much as the next but in this instance, well, you seem to be barking up the wrong tree.
Click to expand...
Click to collapse
ya i have no idea. didn't try to sound like i did. Just assumed since i thought that ATT couldn't go back to 4.2.2 that meant that the carrier must have something to do with it if Verizon's release of 4.4 does allow you to go back to 4.2.2. I used logic not knowledge so I really don't have an idea at all.

Added a few more things to the Initial post.. See.. Edits & Updates...

What if you have an unlocked rooted GSM Developer Edition with TWRP installed? There is an update available, but I can't find a flashable version yet nor a stock ROM or recovery to revert to so I can accept the OTA.

KidJoe said:
Added a few more things to the Initial post.. See.. Edits & Updates...
Click to expand...
Click to collapse
Non developer edition on 4.4 now has root
And it is possible to downgrade to 4.2.2. I've done it multiple times already when testing.

Added a couple updates to the OP

jayboyyyy said:
ya i have no idea. didn't try to sound like i did. Just assumed since i thought that ATT couldn't go back to 4.2.2 that meant that the carrier must have something to do with it if Verizon's release of 4.4 does allow you to go back to 4.2.2. I used logic not knowledge so I really don't have an idea at all.
Click to expand...
Click to collapse
AFAIK, u can downgrade the ATT phone back to 4.2.2, but the post-camera ota one.
robsw said:
What if you have an unlocked rooted GSM Developer Edition with TWRP installed? There is an update available, but I can't find a flashable version yet nor a stock ROM or recovery to revert to so I can accept the OTA.
Click to expand...
Click to collapse
The GSM DE uses the Retail (TMO) ROM.

[IMG][5.0.2][Lollipop]RETCN XT1085 LXE22.92-18

The IMG is made for Moto X 2nd Gen sold in China mainland aka " XT1085" which was released a week ago. Major retailers in China have started to sell since Feb 5.
I can confirm the system also works well on my XT1095 pure edition,however Moto engineers have removed almost all of the google apps and services and implemented some key features with native chinese apps,like Moto Voice. Most of the bloatwares can be easily removed except a security app of lenovo and a voice assistant named Linxi.
You can get the full IMG from a mirror server in china or file factory
Mega
md5sum: 95306D8D80B1F60285E14D2A6FD7F4F0
XT1095 pure edition users can flash the boot.img and system.img via Fastboot utility.(1.Please backup your data before doing this!
2. Just flash the boot.IMG and all system image chunk files. Don't flash other partitions especially GPT and Bootloader,otherwise you would upgrade BL to 0x6012.)
As the Google apps, we can find many flashable zips in the forum,like @TKruzze's PA Gapps packages.

This work in xt1097? And how about root?

xarcom said:
This work in xt1097? And how about root?
Click to expand...
Click to collapse
It should work since there is almost no big difference in android system between 1095 and 1097. However, you should unlock BL first.
As the ROOT, chainfire's CF-Auto-ROOT image still works or you can flash TWRP recovery to your device via fastboot, and flash the root binaries from within TWRP.

I downloaded but how install? Sorry i'm noob , i have unlock bl

xarcom said:
I downloaded but how install? Sorry i'm noob , i have unlock bl
Click to expand...
Click to collapse
0.Backup your personal data.
1.Unzip the image.
2.Put your phone in AP fastboot mode.
3.fastboot flash boot boot.img
4.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
5.fastboot -w
6.fastboot reboot

Does the Moto Voice works in other languages? Also the system is all in Chinese or we can change it to English or in my case Spanish.? Thanks.
Auto reply
Nop, the moto voice is not working with any language besides chinese, what I did was to uninstall via Titanium the moto voice, reboot and install the normal apk and everything is great now

No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?

alexfiorani said:
No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?
Click to expand...
Click to collapse
5.0.1 has fixed the memory leak bug.

purejoy said:
5.0.1 has fixed the memory leak bug.
Click to expand...
Click to collapse
Memory bug is still present
And Google knows about it
They are set to fix it in 5.1.

I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735

mercado79 said:
I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735
Click to expand...
Click to collapse
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.

purejoy said:
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.
Click to expand...
Click to collapse
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.

zhangyang_haha said:
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.
Click to expand...
Click to collapse
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error

juliospinoza said:
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error
Click to expand...
Click to collapse
each time i flash, it says that the image is too large. I tried different times but it doesnt work

zhangyang_haha said:
each time i flash, it says that the image is too large. I tried different times but it doesnt work
Click to expand...
Click to collapse
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.

juliospinoza said:
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.
Click to expand...
Click to collapse
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.

zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.

zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
we have to wait till some 5.0.2 version is released, in the meanwhile the OP should warn all the users about upgrading the bootloader
thanks

Steve-x said:
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.
Click to expand...
Click to collapse
except for the boot loader? Do you mean that motoboot.img?

zhangyang_haha said:
except for the boot loader? Do you mean that motoboot.img?
Click to expand...
Click to collapse
Don't flash the bootloader partition otherwise you would upgrade BL to 0x6012. Just flash the boot.IMG and all system image chunks.

SOLVED: Flashed TruPureXMM rom in Indian dualsim XT1572 and now No sim detection

I was on indian_mm_deodexed_rooted then flashed TruPureXMM as one of my friends suggested trying it out as it is smooth etc.
I didn't knew that it is Pure single sim version and after flashing no network and then i checked only single sim showed :crying: then i again formated and flashed back indian_mm_deodexed_rooted and modem_indian_mm_fixed but this time it shows two sims with no network atall and Emergency calls on both... In settings SIM cards its SIM 1 emty and SIM 2 empty :crying::crying: tried flashing with indian modem again and also tried lp modem but nothing is working, please help :crying::crying:
Both IMEI Unknown status.
I didn't even took back of my stock as i didn't knew about it before
Bootloader is unlocked and TWRP is installed.
Note: My x style came with lollipop and then i did official update with marshmallow and then i wanted to root so flashed.
Please help me get back dual sim with network if possible
EDIT: Solved the issue now and here is the solution:
Download Stockrom from this link according to your exact model and follow the commands exactly:
[Firmware] Moto X Style/Pure Stock Software by lAndroXl
I just ignored command fastboot oem lock begin as told by @dj_ooms so boot loader is still unlocked and also i have installed TWRP and rooted by flashing SuperSu.
Also very important thing is take nandroid backup after installing TWRP i.e backup your stock rom by selecting backup in TWRP... please also take backup your EFS partition also, thanks
@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies and thanks to lAndroXl uploader and thread... really helped :angel:

Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.

bw03 said:
Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.
Click to expand...
Click to collapse
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??

desiaddict said:
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??
Click to expand...
Click to collapse
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.

bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.

bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.

Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355

bw03 said:
Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355
Click to expand...
Click to collapse
I will try it out... downloading now and will let you know later when dl and flashing finishes and hope i get it working this time, fingers crossed.

If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572

You may need to do the Indian LP modem from the first linked thread too.

http://forum.xda-developers.com/mot...-eu-single-t3297051/post64888714#post64888714
I have posted up more DUAL Sim modems for you to try. Hope it helps and you get it sorted

Unicornzz said:
If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572
Click to expand...
Click to collapse
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
bw03 said:
You may need to do the Indian LP modem from the first linked thread too.
Click to expand...
Click to collapse
Yes i will LP modem flash.
Just one question to all : when i got moto x style in dec it was having Lollipop then i did marshmallow update and then flashed for rooting so now if i again flash to lP stock rom will it get bricked or work?? As i am not getting signals so i will try it later when nothing else works

desiaddict said:
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
Click to expand...
Click to collapse
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you

Unicornzz said:
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you
Click to expand...
Click to collapse
Guys still no luck... nothing worked. I tried both DS modem but did not got sim detection.
I hope somehow who might have faced same issue and got solved will see and reply the thread and save me.
You guys tried to solve my problem... Thank you to both.

Stock ROMs
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms

dj_ooms said:
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8

Did you backup your efs partition? Your imei is inside that partition...

desiaddict said:
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8
Click to expand...
Click to collapse
To be honest, I left the lock bit out. These are the commands I used when I did it:
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.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 reboot
Click to expand...
Click to collapse
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms

dj_ooms said:
To be honest, I left the lock bit out. These are the commands I used when I did it:
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Oh GOD that totaly worked out great :good::good:
Everything is working fine now
Also rooted again without any problem :cyclops:
Thank you buddy.

@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies... really helped :angel:

After flashing phone changed from G4 Plus to G4

I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.

You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695

That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.

Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.

GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.

sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.

Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !

sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...

bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.

bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar

gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.

echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes

gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.

gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch

gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.

echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands

[HELP]SIMs missing (baseband suffix changed to DFLT_FSG) Fingerprint revived

Hi all I have unfortunately lost the proper baseband for my device (XT1643-indian model g4 plus 3gb/32gb)
Prior to posting this, I had my fingerprint lost too. My stupidity was flashing the june fastboot firmware I found on one of the links for motorola rsd cloud clients. :/ With the help of @echo92 i was able to revive the missing fingerprint by pushing hw.img to /dev/block/mmcblk0p43 but still the SIMs won't show up as the baseband has changed to MSM8952_70030.25.03.62.01R DFLT_FSG
I have tried flashing the modem and fsg partitions from the March 1 ROM but still no solution
Any kind of help would be appreciated

Update SIM card recognized but no network at all

tywinlannister7 said:
Update SIM card recognized but no network at all
Click to expand...
Click to collapse
Flashing the modem file for you device didn't change the baseband version? Meaning it didn't remove the suffix at the end...
What happens if you flash a complete stock ROM via fastboot for you device? One that includes all of the files...

Jleeblanch said:
Flashing the modem file for you device didn't change the baseband version? Meaning it didn't remove the suffix at the end...
What happens if you flash a complete stock ROM via fastboot for you device? One that includes all of the files...
Click to expand...
Click to collapse
Bro I already flashed the firmware again..tried the march and june firmwares both

tywinlannister7 said:
Bro I already flashed the firmware again..tried the march and june firmwares both
Click to expand...
Click to collapse
What about this FSG backup (SS, in TWRP) ? Do you have any old backups ?

____Mdd said:
What about this FSG backup (SS, in TWRP) ? Do you have any old backups ?
Click to expand...
Click to collapse
I actually had made these backups specifically for such conditions but i'm unable to find them as of now. I have been able to get the Sims working somehow with @Droidphilev 's flashable modem zip (Available here: https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ). But the baseband I have after flashing this zip is M8952_70030.25.03.62.01p ATHENE_EMEA_DSDS_CUST . Let's see what can be done to revive my phone fully.

tywinlannister7 said:
I actually had made these backups specifically for such conditions but i'm unable to find them as of now. I have been able to get the Sims working somehow with @Droidphilev 's flashable modem zip (Available here: https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ). But the baseband I have after flashing this zip is M8952_70030.25.03.62.01p ATHENE_EMEA_DSDS_CUST . Let's see what can be done to revive my phone fully.
Click to expand...
Click to collapse
your signal is back?

Droidphilev said:
your signal is back?
Click to expand...
Click to collapse
Yes but since the baseband version is different at all, unable to use VoLTE and hence no calls from one of the SIM cards (Jio 4G).
Sent from my Moto G4 Plus using Tapatalk

Please help
tywinlannister7 said:
Yes but since the baseband version is different at all, unable to use VoLTE and hence no calls from one of the SIM cards (Jio 4G).
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I FLASHED THE MODEM FILE SPECIFIED ABOVE, BUT STILL BASEBAND SUFFIX IS DFLT_FSG
I'M ON INDIAN XT1643
HELP PLEASE
My problem started as i was using 7.1.2 AOSP custom rom
then i switched back to MM Stock rom
Everything was fine till i received June Nougat Update
during update my phone went blank
Somewhere with the help of XDA i found a blankflash file and got bootloader back
then i flashed TWRP and wiped full system, cache, and everything
then through fastboot i installed nougat xt1643, xt1626-40-41
i tried every possible firmware, every modem file available.
Still my fingerprint and SIMs are not working
my bootloader is B1.06
I cant downgrade bootloader and gpt.bin even with unlocked bootloader, my model is switched to g4 i think
i can only flash bootloader and gpt of june update
rest all firmwares give Security Downgrade error
Help me please!!!

How did you solved the fingerprint problem.

rajatgupta1998 said:
Yes but since the baseband version is different at all, unable to use VoLTE and hence no calls from one of the SIM cards (Jio 4G).
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Try this link. I was having same problem. Solved it successfully.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

If u hav Imei num and only required baseband u try this it will work for sure has it corrected mine and others https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270/page2

I cant flash hw.img file
rajatgupta1998 said:
Hi all I have unfortunately lost the proper baseband for my device (XT1643-indian model g4 plus 3gb/32gb)
Prior to posting this, I had my fingerprint lost too. My stupidity was flashing the june fastboot firmware I found on one of the links for motorola rsd cloud clients. :/ With the help of @echo92 i was able to revive the missing fingerprint by pushing hw.img to /dev/block/mmcblk0p43 but still the SIMs won't show up as the baseband has changed to MSM8952_70030.25.03.62.01R DFLT_FSG
I have tried flashing the modem and fsg partitions from the March 1 ROM but still no solution
Any kind of help would be appreciated
Click to expand...
Click to collapse
When I push the hw file.it got struck the boot loader.and the adb command prompt struck on 100%.

rajatgupta1998 said:
I actually had made these backups specifically for such conditions but i'm unable to find them as of now. I have been able to get the Sims working somehow with @Droidphilev 's flashable modem zip (Available here: https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ). But the baseband I have after flashing this zip is M8952_70030.25.03.62.01p ATHENE_EMEA_DSDS_CUST . Let's see what can be done to revive my phone fully.
Click to expand...
Click to collapse
i tried the above mention procedure but it didn't help me and i am also facing the same problem my baseband is changed to european variant 'ATHENE_EMEA_DSDS_CUST" please help me.

rajatgupta1998 said:
Hi all I have unfortunately lost the proper baseband for my device (XT1643-indian model g4 plus 3gb/32gb)
Prior to posting this, I had my fingerprint lost too. My stupidity was flashing the june fastboot firmware I found on one of the links for motorola rsd cloud clients. :/ With the help of @echo92 i was able to revive the missing fingerprint by pushing hw.img to /dev/block/mmcblk0p43 but still the SIMs won't show up as the baseband has changed to MSM8952_70030.25.03.62.01R DFLT_FSG
I have tried flashing the modem and fsg partitions from the March 1 ROM but still no solution
Any kind of help would be appreciated
Click to expand...
Click to collapse
How to revive fingerprint?
Helpme please

Baseband, Dual Sim and FP Issue
BORNIOS said:
How to revive fingerprint?
Helpme please
Click to expand...
Click to collapse
Originally Posted by anon10041998
Steps u should follow :
1. Download stock rom from this link androidfilehost.com/?fid=890278863836286757
2.Flash the stock rom
3. Restart your phone in bootloader and flash TWRP, do not boot system. Restart in TWRP
3. Download these files from drive.google.com/drive/folde...mymw-UNe9KtRNm
4. copy the files to your adb or miniboot folder.
4. Flash using the following commands
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
5.Go to ur bootloader again. with fastboot. and flash with that same latest stock rom and check. ur baseband once.
6. I think this baseband will come as EMEA_CUST. But it will get signal network.
7. Now download this zip cloud.mail.ru/public/2Xrm/3vbzbxX5U
8. unzip pws is lenovo-forums.ru
9. Copy all files in ADB folder and delete all previous files
10. Put device into bootloader mode
11. Run programutags --> select APAC --> select INDIA
12. Done

Urgent help
I'm unable to recover sim card and fingerprint (after rooting) option in setting on my Moto g4 plus XT1643 3/32gb Indian version.unrooted successfully currently on stock rom. But no difference. Need help. Please email me on [email protected].

Anand9552 said:
I'm unable to recover sim card and fingerprint (after rooting) option in setting on my Moto g4 plus XT1643 3/32gb Indian version.unrooted successfully currently on stock rom. But no difference. Need help. Please email me on [email protected].
Click to expand...
Click to collapse
do you see any baseband
please share pic