Unable to upgrade baseband - Moto G 2015 Q&A, Help & Troubleshooting

XT1541 Android 6.0.1 MPIS24-107-55-2-5
Phone upgraded using @lost101 factory image.
Flashing done manually excluding erase of userdata and upgrade of bootloader.
Everything is working fine, except upgrading of modem partition (NON-HLOS.bin).
If I upgrade modem partition, phone boots, Android starts without issues but, when I enter PIN of SIM and it registers network, after some minutes, phone resets.
To fix the issue, I must restore dd image of previous modem partition.
So, I'm stuck with baseband M8916_2020610.17.03.21.26R OSPREY_EMEA_CUST.
Inspecting in logcat, I see that last messages before reboot are coming from Widewine processes.
Any suggestions?
Keep in mind that I DON'T WANT to factory reset and/or wipe data partition.

Modem stack (NON-HLOS.bin and fsg.mbn, along with clearing modemstX partitions) must be done as a set and must match the kernel... You can't just flash a different baseband, it must match your ROM is stock, although you could try with a third party kernel.

I've cleared modemst1 and modemst2 partitions.
Also, my actual fsg.mbn is the latest.
With original and unchanged NON-HLOS.bin, I've upgraded system to Marshmallow without troubles and I've used various kernels (stock and 3rd party) without issues.
The problem relies only with the newest NON-HLOS.bin after LP. I'm unable to flash ANY of these.

Related

Sim Card Error after flashing GPE

Hello, I have a XT1032 from Tesco Mobile.
I unlocked the bootloader and flashed the GPE Firmware GPE_XT1032_KOT49H.M004_CFC.xml
I used mototool at first and tried manually using fastboot.
Everything works except I keep getting some random error about my SIM card been removed and added (attached).
I tried to flash the fsg.mbn from stock but it makes no difference.
I did get some errors on fastboot but everything complete with the OKAY message.
any suggestion please?
thanks in advance
I realise its happened since you flashed so probably software related. But is it worth actually physically removing the sim and reinserting just to rule out a genuine dodgy/dirty sim connection.
Also I'm thinking of flashing GPE over my UK retail phone. Did you flash all files inc modem and gpt.bin etc. I am wondering if its worth me just flashing system and boot partitions and nothing else. No harm in me trying that I guess.
scott_doyland said:
I realise its happened since you flashed so probably software related. But is it worth actually physically removing the sim and reinserting just to rule out a genuine dodgy/dirty sim connection.
Also I'm thinking of flashing GPE over my UK retail phone. Did you flash all files inc modem and gpt.bin etc. I am wondering if its worth me just flashing system and boot partitions and nothing else. No harm in me trying that I guess.
Click to expand...
Click to collapse
Yes, I actually went to my carrier and got a replacement card but since it didnt work I went back to Stock and it works fine so it must be GPE related.
This is what I used ( I am on Mac osx):
./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_sparsechunk1
./fastboot flash system system.img_sparsechunk2
./fastboot flash system system.img_sparsechunk3
./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 got some warnings but all commands gave "okay"
I wonder if its worth you keeping non-gpe for modem partition and fsg and just try flashing gpe system and boot partitions. Maybe as gpe is for USA really its causing some issues to use gpe modem bits and pieces.
scott_doyland said:
I wonder if its worth you keeping non-gpe for modem partition and fsg and just try flashing gpe system and boot partitions. Maybe as gpe is for USA really its causing some issues to use gpe modem bits and pieces.
Click to expand...
Click to collapse
Just tried that. Flashed back stock and confirmed everything was working fine. I then reflashed GPE without modem and fsg keeping the stock ones but got the same. Not sure the problem is on the radio at this point.
Sent from my XT1032 using Tapatalk
If anybody has the same problem, I was able to fix it by flashing the latest Radio 355.66.00R from the latest stock update.
I yesterday flashed GPE on my XT1032 (Germany Retail).
But i flashed it using the *.bat /eu file.
No SIM Card error.
Flashed gpe on french moto g, there is no errors.
only radio apps is missing.
It is not missing. It is simply not a feature of GPE.

[Q] How can I update my rooted XT1032 GPe 4.4.4 to 5.0, since I had to flash non-GPe

Hello,
TL;DR: My question: where can I find a stock 4.4 GPe firmware compatible with XT1032 devices? (cid: 0x00DE
I had a rooted Moto G GPe 4.4, which prompted me yesterday about updating to Lollipop (OTA update, is that right?). Of course, it didn't work. Seriously, for newbies like me reading this, don't accept this, wait for something stable to be available.
So, yesterday, it downloaded everything and started updating. It hanged right in the middle with an error screen. I tried a reboot, same thing (in french it was written "Aucune commande". I guess the proper translation would be no command available or something). I tried a recovery, I had the little android logo lying on the ground with a scary warning on his belly. I tried a factory reset, same thing.
So, I went on this forum, started following this guide, however I was on Linux so I didn't use his .bat script, instead I manually used fastboot and mfastboot.
I downloaded the image named XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip (the CID don't match but it worked) available at this address. For information, the link http://sbf.droid-developers.org/phone.php?device=14 is dead since yesterday at least, which is annoying given the bandwidth of filefactory.
Using mfastboot, I launched these commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Everything was fine. My phone booted, prompted me to install the device and download my apps. Aside from the fugly Motorola boot animation and stock apps, great. However, I couldn't get the Lollipop update, since apparently it is only available to 4.4 GPe edition. I thus got even dumber than normally and started to follow this guide. Beware, the sound is very loud on this video, and doing a video for this kind of info is pretty dumb anyway. The process is written down in the description.
I downloaded the 4.4 GPe firmware linked and started to flash it using mfastboot, same process as above. However, upon rebooting I had only a prompt to decrypt my data. WTF? I used my Google Account password to no avail. Rebooted in fastboot mode, tried recovery and factory reset. Nope. So, I flashed again the XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF firmware. I booted fine, and it is currently restoring my system.
Anyone could explain exactly why it did it? Do I have to worry about anything (I don't care about my data, everything is backed up securely. But I critically need my phone and can't afford to brick it).
I am unable to find a stock 4.4 GPe firmware. Anyone got a link? If possible from a reputable source? I'd like to stay on a GPe phone, I hate bloated and ugly designs. And I'd like to update to Lollipop.
Edit: Okay, the flashing did work, however the CID mismatch is more of a problem than I thought. My CID as printed by fastboot is 0x00DE (and NOT 0x000DE as sometimes indicated in some guides). My image CID is 0x0007. I can't speak on the microphone and I don't have any tone when I call. It is a problem. FFS, is there any ROM I can flash working with this CID?
lknr said:
Hello,
TL;DR: My question: where can I find a stock 4.4 GPe firmware compatible with XT1032 devices? (cid: 0x00DE
Anyone could explain exactly why it did it? Do I have to worry about anything (I don't care about my data, everything is backed up securely. But I critically need my phone and can't afford to brick it).
I am unable to find a stock 4.4 GPe firmware. Anyone got a link? If possible from a reputable source? I'd like to stay on a GPe phone, I hate bloated and ugly designs. And I'd like to update to Lollipop.
Click to expand...
Click to collapse
GPE 4.4.x uses ext4 /data partion whereas Retail-XX versions use f2fs. Hence when we restore the /data partition from a different filesystem type it gives that 'enter encryption password' screen. So probably you had restored your /data partition on GPE device from your non-GPE /data backup. Wihout that it should work fine.
nbansal said:
GPE 4.4.x uses ext4 /data partion whereas Retail-XX versions use f2fs. Hence when we restore the /data partition from a different filesystem type it gives that 'enter encryption password' screen. So probably you had restored your /data partition on GPE device from your non-GPE /data backup. Wihout that it should work fine.
Click to expand...
Click to collapse
Okay, that mush be linked indeed. However I didn't restore my backup (I didn't have much files, and by backup I mean my documents were uploaded on the cloud so I don't care about anything on the device. If I launch fastboot erase userdata before flashing the GPE firmware I downloaded, will it still do the enter encryption password screen ? Is there a guide to flash a GPE firmware somewhere?
lknr said:
Okay, that mush be linked indeed. However I didn't restore my backup (I didn't have much files, and by backup I mean my documents were uploaded on the cloud so I don't care about anything on the device. If I launch fastboot erase userdata before flashing the GPE firmware I downloaded, will it still do the enter encryption password screen ? Is there a guide to flash a GPE firmware somewhere?
Click to expand...
Click to collapse
Okay, it seems you didnt wipe data partition when you flashed GPE over Retail version. So when it booted into GPE, GPE cannot interpret f2fs /data partition and thinks its encrypted and prompts for the password. If needs a blank/wiped /data at first boot. In general its a good idea to 'erase userdata' (if via fastboot) or wipe data partition (if using recovery) when flashing any ROM.
nbansal said:
Okay, it seems you didnt wipe data partition when you flashed GPE over Retail version. So when it booted into GPE, GPE cannot interpret f2fs /data partition and thinks its encrypted and prompts for the password. If needs a blank/wiped /data at first boot. In general its a good idea to 'erase userdata' (if via fastboot) or wipe data partition (if using recovery) when flashing any ROM.
Click to expand...
Click to collapse
That was it, simply. Thanks. I followed this guide (incidentally using the very same files I downloaded in my OP), stopped right before the OTA sideload step. It is no downloading the system update on its own, everything seems to be working.

[Q]Moto G - XT1031 - Boost Mobile - CyanogenMod Troubles!

**Bear with me as this is my first unlocking/rooting endeavor!**
I bought a brand new Moto G (XT1031) for Boost Mobile. It came with KitKat 4.4.4 pre-installed. I researched/followed guides and was able to unlocked it.
More research was done. I flashed the recovery software TWRP v2.8.6 via ADB fastboot. I then flashed SuperSU v2.46 via TWRP(zip file). Back up was created with TWRP. Attempted to install CyanogenMod 12.1, however, my bootloader version is "4113" so it said it was not supported. It seemed like changing the bootloader was a bad idea, so I did not pursue that idea. I tried to install CM 12, it was successful. I proceeded to install the gapps version for CM12. I rebooted the system.
It stayed on the boot screen(blue robot head) for a hour. I shut off and restarted the phone, it sat on the boot screen for about 30 minutes. It would not load. At this point I messed something up and had to clear everything and install a clean KK 4.4.4 image. I then tried CM12 all over again, but I was still stuck on the loading screen..
So my question is what can I do? Should I try CM11?(I could not find a DL link anywhere!!)
ANY help is appreciated, I have been at it all day..
MeLoDyz said:
**Bear with me as this is my first unlocking/rooting endeavor!**
I bought a brand new Moto G (XT1031) for Boost Mobile. It came with KitKat 4.4.4 pre-installed. I researched/followed guides and was able to unlocked it.
More research was done. I flashed the recovery software TWRP v2.8.6 via ADB fastboot. I then flashed SuperSU v2.46 via TWRP(zip file). Back up was created with TWRP. Attempted to install CyanogenMod 12.1, however, my bootloader version is "4113" so it said it was not supported. It seemed like changing the bootloader was a bad idea, so I did not pursue that idea. I tried to install CM 12, it was successful. I proceeded to install the gapps version for CM12. I rebooted the system.
It stayed on the boot screen(blue robot head) for a hour. I shut off and restarted the phone, it sat on the boot screen for about 30 minutes. It would not load. At this point I messed something up and had to clear everything and install a clean KK 4.4.4 image. I then tried CM12 all over again, but I was still stuck on the loading screen..
So my question is what can I do? Should I try CM11?(I could not find a DL link anywhere!!)
ANY help is appreciated, I have been at it all day..
Click to expand...
Click to collapse
First of all format data, system, cache, delvic cache and install the zip
pradeeppk said:
First of all format data, system, cache, delvic cache and install the zip
Click to expand...
Click to collapse
I have always went into advance wipe on TWRP and wiped the dalvik cache, data, cache, & system before each install of CM. I even wipe the cache in-between the install of CM and gapps.
I have never formatted before.
So I tried it and it deleted my zip files and my back up..
Now I have no OS so I cannot put new zip files of CM/gapps on the phone. I cannot back up because that was deleted -.-
EDIT: was able to flash a stock 4.4.4 OS back and get it to boot.. no idea what to do now ..can someone link me to CM11?
**UPDATE**
Tried lots of things..ended up updating the bootloader to 4119..which enabled me to finally install CM 12.1. BUT..CM would not boot again! Tried putting the stock rom back on, but failed, would not boot..
Now I cannot load any OS, I get stuck on the "warning your device is unlocked" screen. I can still get to the boot loader and recovery though..
I tried to flash back to stock with multiple guides I found via google, but none worked...
calling anyone to extend some help, or is my phone dead?
That's why flashing a "soak test" - scratch that - "test drive" bootloader is a bad idea.
You'll need to flash the KitKat firmware with mfastboot and skip gpt, motoboot, and logo img/bin's.
Sent from my XT1031™
ATTACK said:
That's why flashing a "soak test" - scratch that - "test drive" bootloader is a bad idea.
You'll need to flash the KitKat firmware with mfastboot and skip gpt, motoboot, and logo img/bin's.
Sent from my XT1031™
Click to expand...
Click to collapse
are you referring to steps like this:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
if so I have tried that and it fails
Yes, flash everything but "gpt", " motoboot" and "logo".
Sent from my XT1031™
ATTACK said:
Yes, flash everything but "gpt", " motoboot" and "logo".
Sent from my XT1031™
Click to expand...
Click to collapse
ah I see, thanks!
I was able to boot stock 4.4.4, however, the screen is a bit glitchy with a line constantly coming down. From what I have read it seems that is caused by the bootloader version 41.19 (that I upgraded to). Is there anyway to get 41.13 back?
..and I guess putting CM on this phone is a no go for whatever reason?
MeLoDyz said:
ah I see, thanks!
I was able to boot stock 4.4.4, however, the screen is a bit glitchy with a line constantly coming down. From what I have read it seems that is caused by the bootloader version 41.19 (that I upgraded to). Is there anyway to get 41.13 back?
..and I guess putting CM on this phone is a no go for whatever reason?
Click to expand...
Click to collapse
Nope - cant downgrade bootloaders.
As far as CM goes, I really wouldn't know, I don't use it. I prefer stock AOSP or Paranoid Android. There's a really nice build of Paranoid Android at Android Forums by Seraph08
http://androidforums.com/index.php?threads/851868/
Sent from my XT1031™
I have the same device as you, and I decided to upgrade my bootloader, and I was able to successfully get CM 12.1 latest nightly installed and working. Here's what I did:
First I started with full stock 4.4.4, flashed TWRP and upgraded my bootloader.
Then afterwards I installed one of the CM11 snapshots and then from there I flashed the latest CM12.1 nightly and everything seems to be working except data breaks sometimes, it usually fixes itself with a reboot.
Ninja3047 said:
I have the same device as you, and I decided to upgrade my bootloader, and I was able to successfully get CM 12.1 latest nightly installed and working. Here's what I did:
First I started with full stock 4.4.4, flashed TWRP and upgraded my bootloader.
Then afterwards I installed one of the CM11 snapshots and then from there I flashed the latest CM12.1 nightly and everything seems to be working except data breaks sometimes, it usually fixes itself with a reboot.
Click to expand...
Click to collapse
That worked for me I am on CM12.1 now!, thanks
Any idea if it is possible to get CM12.1 on a boost XT1031 with 41.13 bootloader, WITHOUT upgrading the bootloader?

moto xt1543 won't reconise the sim card CM12.1

Hey, so today I was trying to go to stock room and failed, when I got back to the CM12.1 the sim wont be recognized.
I tested with another phone and the sim still works.
I don't really now what to do., I've tried to fastboot erase modemst1
and fastboot erase modemst2, but no success.
I'm really stressed about this
polvoraan said:
Hey, so today I was trying to go to stock room and failed, when I got back to the CM12.1 the sim wont be recognized.
I tested with another phone and the sim still works.
I don't really now what to do., I've tried to fastboot erase modemst1
and fastboot erase modemst2, but no success.
I'm really stressed about this
Click to expand...
Click to collapse
Umm... why would you erase the modem firmware???
You need to get the correct firmware image that matches your boot loader and perform:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
To be honest, your device is in an "unknown state" at this point, I would do a factory reset in the ROM (in Android, not TWRP), then flash the full factory image, boot fully, and make sure everything is working before continuing.
acejavelin said:
Umm... why would you erase the modem firmware???
You need to get the correct firmware image that matches your boot loader and perform:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
To be honest, your device is in an "unknown state" at this point, I would do a factory reset in the ROM (in Android, not TWRP), then flash the full factory image, boot fully, and make sure everything is working before continuing.
Click to expand...
Click to collapse
I've found this room, but i'm not sure if my cellphone is LPI23.72-16.4 or LPI23.72.43.
I should flash this room just like i've flashed CM ?
polvoraan said:
I've found this room, but i'm not sure if my cellphone is LPI23.72-16.4 or LPI23.72.43.
I should flash this room just like i've flashed CM ?
Click to expand...
Click to collapse
No... Red the thread on how to flash factory images... If you do it wrong you can brick
Sent from my MotoG3 using Tapatalk
Never change mobile data option to SIM2 !!!
I'm in the same situation with Moto G 3rd gen XT1543 with Andoird 6.0:
I'm using two UK sim's: Three (Sim1) and EE (Sim2).
When I changed the mobile data to Sim2.... THE HELL !!! Sim1 appears in the list but signal is not available anymore.
I tried to switch both ones, and nothing.
I tried the Sim1 in another phone and it works perfectly!
When I take Sim2 off, Sim1 came back to life but just with voice, no data! Plus when I tried to switch mobile data to Sim1 (remember that I take Sim2 off at this moment), it do not ignites mobile for Sim1 anymore.
Conclusion: NEVER switch the mobile data to SIM2 !! Is a black role in the Motorola week software.
I tried everything you could imagine: turn off, enable and disable all possible combinations between sms, mobile data and voice options between both Sim's and nothing !!! Sheet Motorola !!!

lost signal moto xt1039, partition backup request

I've lost cellular signal in my xt1039 device. Tried many things including reflash firmware/ flash modem... with no permanent solution.
At last fellow brother @lost101 suggested to flash some partitions stated here http://forum.xda-developers.com/moto-g/help/story-lost-recovery-imei-0-t3414511 as a solution. But by searching in google i cant find any.
Can any of you be kind enough to take backup of "dhob" "fsc" "misc" and "hob" partitions from your xt1039 device and by sharing those help me fix my phone? I'll be greatfull forever.
Backing up partition is easy, just install partition backup in your rooted phone. Select raw partition image from setting menu. And its done.
promote
I'm posting this comment just to promote this post, please help me with those partitions if you can.
As far I know, these partition's contain very sensitive data unique to the device. So do not upload these files, and do not flash these partitions on another device. For example, it could cause you to have the same IMEI as someone else, or a multitude of other issues.
As for the actual issue, do your IMEI show up correctly in Android, or is it only the signal that is broken?
Professor Gibbins said:
As far I know, these partition's contain very sensitive data unique to the device. So do not upload these files, and do not flash these partitions on another device. For example, it could cause you to have the same IMEI as someone else, or a multitude of other issues.
As for the actual issue, do your IMEI show up correctly in Android, or is it only the signal that is broken?
Click to expand...
Click to collapse
My imei is intact. Its just my cellular signal that doesn't work. And its not only my issue, there are many with the same problem but no solution. So here I am requesting those partition to try as a solution as stated in this post http://forum.xda-developers.com/moto-g/help/story-lost-recovery-imei-0-t3414511 . I've tried everything else that i could find.
In my country wifi network isn't that available. So without cellular network a phone here is as good as dead. Can you suggest any solution?
Flashing those partitions most likely won't fix your network signal, and could make the problem much worse. In the OP you say you flashed the stock modem, so what method did you use to do this? Did you get the stock firmware and run:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Professor Gibbins said:
Flashing those partitions most likely won't fix your network signal, and could make the problem much worse. In the OP you say you flashed the stock modem, so what method did you use to do this? Did you get the stock firmware and run:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
did those, tried flashing full firmware and downgrading too... nothing worked. Any other suggestions?
Usually factory firmware would fix it, so it could be a hardware issue. Under what conditions did you lose signal - did you flash a ROM?

Categories

Resources