Database Develop

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

Moto G 2014 LTE ( XT1079 ), How to relock bootloader

I downloaded Android Marshmallow after reading news about it through settings/about/system updates.
After downloading, the phone restarted but updatation was stuck after flashing TWRP screen (error screen photo attached)
My phone is
bootloader unlocked,
recovery TWRP
rooted
ROM is stock.
It seems the OTA update will be completed once I have stock recovery,
I have following queries
Is it necessary to revert to stock recovery to complete OTA update?
If yes, how to achieve it, what i learnt through search, I need to find Stock ROM zips and extract recovery (boot.img) and then flash it through adb?
where to look for thea stock rom and is there any easier method

It's risky, a lot of users here for some reasons got stuck whit locked/unlocked bootloader unable to boot and flash anything.
Here you can find all the motog stock roms http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
You should wait for the complete rom image for your country/model to pop there instead doing that risky thing you want do.

Thanks
Recently stock rom for xt1079 has been added to the list.
But I m trying to download from filefactory since yesterday but due to some reason, it stops in between and resume isn't supported.
Are there any other hosts

Are you sure the region of that xt1079 is right for your phonr ? check the phone box and the info inside settings to know which region/carrier you have, you must use the same identical 100% stock to avoid problems
And, do no relock bootloader !!!

yes i bought this through online retailer in India.
It is xt1079 Asia
I see in xda forum of moto g 2nd gen most of the time ppl are talking about xt1078.
What's the difference between xt1078/1079 and can't I use xt1078 ROM.
Rooting procedure meant for xt1078 worked fine for me
And Sir is relocking bootloader very risky ? suppose something goes wrong wont I be able to unlock or restore nandroid backup.

Thanks to support from Dr.nic I am finally on android 6.0
Although I have relocked my bootloader, but it is recommended to leave as it is.
If anyone stumbles here with same problem like mine i.e. unable to upgrade to android 6.0 just because of custom recovery, then pls download the firmware from filefactory.com link and flash. I'll add flashing commands as well to this post in near future.

if you have already done this rom change etc, the you must already be having fastboot, adb etc.
after connecting in fastboot mode holding VolDown and Power for few secs
run following commands
[this is for android 6.0 firmware]
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I am not great expert, do this only if you have some idea, I may not be able to help you much if something goes wrong.
I can only say it worked for me

GPS doesn't work-TWPR not wipe/restore cache and others partition

How to fix this? what file I should flash in fastboot or recovery?
Maps and others apps not recognize mi GPS
2-When I wipe cache partition or restore, twrp says error
(3.0...)
I have a moto x xt1058 with rom epsilon project (flashed over 5.1 stock) *When I flashed stock 5.1 with fastboot, fastboot give some errors.
sorry for my bad english

As to the GPS, clearing the modem using fastboot worked for me.
fastboot erase modemst1
fastboot erase modemst2
You might need to your device's stock NON-HLOS.bin as modem before issuing these commands. Download your device's latest stock firmware, extract the requisite file and flash it with the following command.
fastboot flash modem NON-HLOS.bin
I do not know how to help you with issue number two. Maybe just try flashing the official TWRP image again.

Flashed Stock MM, now can't complete setup wizard

I was on 5.1, bootloader unlocked by sunshine. I rooted to enable tethering, and after did a full unroot. Once the OTA MM update came it couldn't install. Android on back and then rebooted. Instead of trying to fix the software, I decided to get MM from XDA. I flashed TWRP, updated bootloader from computerfreek's thread and flashed his rom for non-verizon.
Now once it turns on I can choose language. At the next page it says select wi-fi netowork, but no wifi networks show up and the Skip button is grayed out.
I followed the directions again and reflashed a few times, but the same result.
I then tried the Brazilian MM from iiwoodstock but with the same result. I flashed his with and without the linked kernal, but again, with the same results.
Any ideas? I was hoping to avoid flashing the stock images, but if that's my only option....

Well I got irritated enough and flashed stock. All is working now.
It was a pain because I only have Windows 10, so RSDLite was being irritating.
Here are the steps I wish someone had put together for me.
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Having ADB Everywhere helps. Just install this:
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Make sure your drivers are installed. I needed to go to motorola to download their software to get fastboot drivers to work:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/103535/p/30,6720,9277
Have a copy of fastboot.exe
(Google it or just do a search on your computer. You probably have a copy of it somewhere if you've ever done anything to a phone)
Here is a link to the .bat file I made that will flash it without needing RSD.
https://nofile.io/f/sh00er98rzM/servicefile.bat
In case someone finds this thread and the file is no longer hosted, here it the text of the .bat file (use Notepad++ or something):
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_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 erase clogo
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
(Have phone connected in fastboot mode - power plus volume down)
1. Extract the stock image into a folder
2. Put the .bat file in that folder
3. Put a copy of fastboot.exe into the folder as well
4. double click the .bat file
(wait for it to finish. If there's errors, don't worry, it should be fine. Worry when it's worth it. This is not a big deal)
done
I figured this out primarily because of RootJunky.com's youtube video.
https://www.youtube.com/watch?v=njXQYn53SPc

gr8hairy1 said:
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334

ChazzMatt said:
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
Click to expand...
Click to collapse
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed

gr8hairy1 said:
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed
Click to expand...
Click to collapse
Release notes here:
https://www.verizonwireless.com/support/droid-turbo-update/
Sent from my carrier unlocked LG V30+ US998

LOOSING IMEI AND BASEBAND VERSION / SIM showing NO SERVICE

Whenever I try flashing a custom ROM i either loose my IMEI numbers and baseband version or simply get a NO SERVICE. The most recent custom rom i tried was Pixel Experience android 10, for this ROM i had my IMEI numbers and baseband version but got a "no service" - it did however detect my service provider.
Also when i flash the stock ROM back i don't get data(imei and baseband) immediately, i have to perform 2 OTA updates to get them.
So here's what i tried, flashed stock ROM did the 2 OTA updates to get my SIM to work and took a TWRP backup of EFS. Then flashed custom ROM and restored EFS but still didn't get the SIM working
I also took an entire backup of the stock ROM but when i try restoring it i get an error " Extract tar fork 255" in TWRP - now i believe this has to do with the fact tht i'm unable to flash TWRP recovery when on stock ROM (i keep getting a "no command" when i boot to recovery like this) but instead i have to directly boot into twrp every time - fastboot boot twrp.img and when i do it this way TWRP asks for a decrypt(?) password for which i press cancel.. which leads me to believe the backing up doesn't work properly because of this.
Any idea of to fix any of this?

Try to flash validus rom then back to stock.
While flashing stock skip
fastboot erase modemst1
fastboot erase modemst2
Then flash whatever you want.
And also in twrp try to repair data partition. Decrypt message could be bad disk sign.
I faced this issue, can't get 4G signal and speaking myself "how can validus rom solve this problem, nah just another silly solution"
But it solved!

flashe stock (august19 ROM) using codes
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash 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 oem oem.img
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
then after first boot again flash this coades
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
baseband and imei showing
sushiada said:
Whenever I try flashing a custom ROM i either loose my IMEI numbers and baseband version or simply get a NO SERVICE. The most recent custom rom i tried was Pixel Experience android 10, for this ROM i had my IMEI numbers and baseband version but got a "no service" - it did however detect my service provider.
Also when i flash the stock ROM back i don't get data(imei and baseband) immediately, i have to perform 2 OTA updates to get them.
So here's what i tried, flashed stock ROM did the 2 OTA updates to get my SIM to work and took a TWRP backup of EFS. Then flashed custom ROM and restored EFS but still didn't get the SIM working
I also took an entire backup of the stock ROM but when i try restoring it i get an error " Extract tar fork 255" in TWRP - now i believe this has to do with the fact tht i'm unable to flash TWRP recovery when on stock ROM (i keep getting a "no command" when i boot to recovery like this) but instead i have to directly boot into twrp every time - fastboot boot twrp.img and when i do it this way TWRP asks for a decrypt(?) password for which i press cancel.. which leads me to believe the backing up doesn't work properly because of this.
Any idea of to fix any of this?
Click to expand...
Click to collapse

lynxrz said:
Try to flash validus rom then back to stock.
While flashing stock skip
fastboot erase modemst1
fastboot erase modemst2
Then flash whatever you want.
And also in twrp try to repair data partition. Decrypt message could be bad disk sign.
I faced this issue, can't get 4G signal and speaking myself "how can validus rom solve this problem, nah just another silly solution"
But it solved!
Click to expand...
Click to collapse
which version can you share the link of Which version orpost link or download link

[email protected]!vam said:
which version can you share the link of Which version orpost link or download link
Click to expand...
Click to collapse
Trying it out on a Moto G5s plus. Validus to stock to dot OS. Let's see if it brings back the baseband and IMEI. Fingers crossed
Editidn’t work