Database Users

No Baseband No IMEI

Hi
While trying to install the Pure rom on my XT1572...I was facing this issue that I couldnt get any network...during the installation I didnt face any issues which I am aware of...but now when I checked it it says both are missing...am not sure what to do now...did I ruin my phone? Is there any way to check what can be done?
1. I had used the adb to install twrp on the device today itself...and then iinstalled everything using it

Doing some more research I found out that my issue might have been due to not selecting read only in twrp...is that a possibility? any workarounds?
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)

msankadi said:
Doing some more research I found out that my issue might have been due to not selecting read only in twrp...is that a possibility? any workarounds?
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Click to expand...
Click to collapse
Could you please tell me as to how you recovered your IMEI and Baseband?

Flash your efs backup.

lafester said:
Flash your efs backup.
Click to expand...
Click to collapse
If you don't have the phones original efs backup?

WhyKRUM said:
If you don't have the phones original efs backup?
Click to expand...
Click to collapse
Then send it in for repair. Those are the only options allowed here.

Flash the correct modem .

Thank you for the replies/advice
Found the correct modem for my phone, but even after manually flashing with the usual prescribed commands of:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
My MXP/S was still showing "Unknown" baseband and IMEI
I then retried the process with an additional flash modem command (eg. below) and have since had full LTE/4G coverage and perfect Wifi.
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
Hopefully this info helps anyone else.

@ECHO OFF
ECHO.
ECHO. Script by @evogp ...
ECHO.
ECHO.
ECHO. Flashing Bootloader ...
ECHO.
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
ECHO.
ECHO. Flashing System ...
ECHO.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
ECHO.
ECHO. Flashing Modem SW ...
ECHO.
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
ECHO.
ECHO. Wipe Cache and Data ...
ECHO.
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
ECHO.
ECHO. Installation Complete!
ECHO.
PAUSE
mfastboot reboot
EXIT /b 0

I also have problems with the network, no signal, plus my appears the normal imei, Moto X Style Brazil.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

WhyKRUM said:
Thank you for the replies/advice
Found the correct modem for my phone, but even after manually flashing with the usual prescribed commands of:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
My MXP/S was still showing "Unknown" baseband and IMEI
I then retried the process with an additional flash modem command (eg. below) and have since had full LTE/4G coverage and perfect Wifi.
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
Hopefully this info helps anyone else.
Click to expand...
Click to collapse
It did, thanks a lot!

https://www.xsfirmware.com/motorola-moto-x-force-xt1580-firmware-flash-file/
Solution to no baseband xt1580

Phone Bricked, Flashboot failed.

Hello,
Last night I tried to root my new moto x play
the root failed and it went to bootloader, where after much looking around I found a website through here that showed me how to flash, used to correct latest firmware.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
my current error message is failed to validate system image and this shows when I try to access recovery as well.
Any advice would be greatly appreciated.
Model XT1562
Edit, I have motorola device manager installed, both rsd lite and verizon wireless softwear upgrade cannot detect phone.

If you were flashing the most up to date firmware then you definitely missed a couple of sparsechunks. Use fastboot to flash everything (check flashfile.xml for proper fastboot commands)

minimale_ldz said:
If you were flashing the most up to date firmware then you definitely missed a couple of sparsechunks. Use fastboot to flash everything (check flashfile.xml for proper fastboot commands)
Click to expand...
Click to collapse
Cheers for the help mate.
all sorted just missed number 8.

Restore G5 Plus to Stock (But Rooted) Questions

My questions are at bottom.
Context:
I recently tried to go back to my stock from lineageos. I successfully did it through this youtube video but I've run into a couple of problems.
Youtube Video Titled: MOTO G5 PLUS STOCK ROM FLASHING | UNBRICK/UNROOT MOTO G5 PLUS
(I'm not allowed to post links)
I used firmware NPN25.137-35
after I flashed twrp, no-verity-check and magisk v14
After mistakenly tried to apply an OTA update(I know better now) my phone always boots into recovery. I discovered this when the updated tried to restart to install. I have to boot to bootloader and press the power button when the selection is on "start". I'm not sure if the OTA had anything to do with that.
The fastboot commands I used where this to install the stock ROM
Code:
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Questions:
1. If I want to download the stock image directly from the "firmware.center" which one do I choose and how do I know? There are 9 of them..
2. Do I ever need to unlock my bootloader again or is that a one time thing?
3. Do those fastboot commands and the stock image bring my moto g5 plus back to the way it was completely when I unpackaged it (minus unlocked bootloader)?
4. Can I run those fastboot commands without unzipping the stock *.xml.zip?
5. Where did these commands come from? Is it common knowledge that they work? Or is a fastboot sequence provided by motorola?
6. Does "just" attempting an OTA update mess stuff up on a rooted android?

Flashed a stock ROM, can't lock bootloader, OTA updates working anyway

So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?

badtlc said:
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
Click to expand...
Click to collapse
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.

Wolfcity said:
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Click to expand...
Click to collapse
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?

badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Try locking again with the updated firmware. If the boot.img failed to write then it would have shown error in cmd.

badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Agree, if there was no error in the fastboot log it was ok. If you want to relock the bootloader (there's no good reason for it unless you want to sell the device) here are the locking and flashing commands. You need the exact same firmware you're on for locking!
For Oreo the whole sets of commands are for
Locking:
-----------------
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 fastboot flash system system.img_sparsechunk.1 fastboot flash system system.img_sparsechunk.2 fastboot flash system system.img_sparsechunk.3 fastboot flash system system.img_sparsechunk.4 fastboot flash 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
-----------------------------------
The same commands for Nougat:
Flashing:
-----------------------------------
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
--------------------------
Locking:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock

I will try those. They look very similar to what I tried already. I always got a fastboot write error for the boot.img and of course the can't OEM lock error.
If the boot.img didn't write properly, would I even be able to boot into the stock ROM? The fact it is working just has me paranoid I'm missing something and about to brick my phone by mistake.

badtlc said:
If the boot.img didn't write properly, would I even be able to boot into the stock ROM?
Click to expand...
Click to collapse
No

[GUIDE] Moto Z Play (XT1635-02) Flashing signed stock image + Relocking bootloader

Hello fellow XDA enthusiasts!
I have been scavaging the forums on how to relock my bootloader after flashing this custom rom and a custom TWRP recovery.
Nothing worked to get me back to STOCK! (Sources):
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621
However... I managed to modify existing methods to make one that DID work… for me. (XT1635-02)
Here it is:
DISCLAIMER: I HAVE NO RESPONSIBILITY IN ANY WAY IF SOMETHING GOES TERRIBLY WRONG WITH YOUR DEVICE.
Step 1:
Install Motorola Drivers.
Step 2:
Install ADB Minimal.
or
ADB Tiny.
Step 3:
Download this latest signed image (Oreo, August 1, 2018).
Copy all of its contents into the directory where you installed your ADB Minimal (C:\ if portable).
Mirror ( only if AFH down use this link! )
Step 4:
Plug the Moto Z Play into your computer and HOLD DOWN 'volume down' + 'power' buttons.
Open up ADB Minimal and type ​
Code:
cd..
cd..
cd ADB
fastboot devices
(you should see your device!)
Alternatively, if you are booted on your phone, make sure ADB is enabled in developer mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(see here)
and device is authorized on PC, type:​
Code:
cd..
cd ADB
adb reboot bootloader
adb devices
Once confirmed you see your device. Copy & paste the following commands:​
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash boot boot.img
fastboot oem lock
Step 5:
You will may have to manually press 'enter' on your keyboard to enter the last command which will reboot your device and Voilà La!
You should have relocked bootloader. ​

I've tried this method, but on booting screen the problem is persistent that your device has been unlocked and not tusted please visit care center:; I'm hectic, even in my device oem lock option is under gray colour and it's not clicking. How i can get rid from this issue???