Database Info

[Q] XT1034 US GSM Model, Need correct radio flash.

I have a XT1034 that I put the wrong lollipop update on (I think it was for an XT1032), and that led to it having no sim card detected.
I finally got it back in a usable state by going back to 4.4.4 and flashing the radio files I found in this file. (Sorry still can't post links.)
"Fix Modem issues for XT-1034 Moto-G.zip"
Then it was still glitchy (screen issues), So I've applied the 5.02 Canada AWS firmware, and everything seems to work except that I only get H or H+ for a connection.
I've not gotten 3g. I'm on Straight Talk with an AT&T sim, and My daughter has the exact same setup, but with stock roms/etc.
She has no problem getting 3g.
My goal is having the USA Lollipop back on here, with the correct radio flashed.
Any ideas?
Thanks.

dabone said:
I have a XT1034 that I put the wrong lollipop update on (I think it was for an XT1032), and that led to it having no sim card detected.
I finally got it back in a usable state by going back to 4.4.4 and flashing the radio files I found in this file. (Sorry still can't post links.)
"Fix Modem issues for XT-1034 Moto-G.zip"
Then it was still glitchy (screen issues), So I've applied the 5.02 Canada AWS firmware, and everything seems to work except that I only get H or H+ for a connection.
I've not gotten 3g. I'm on Straight Talk with an AT&T sim, and My daughter has the exact same setup, but with stock roms/etc.
She has no problem getting 3g.
My goal is having the USA Lollipop back on here, with the correct radio flashed.
Any ideas?
Thanks.
Click to expand...
Click to collapse
H/H+ is 3G, it's just that in America they only use the 3G icon.
If you want to restore back to USA firmware, flash this via fastboot https://drive.google.com/file/d/0B6RNTe4ygItBQUN1SXJxYWtuY2M/view Instructions are here on how to do it: http://forum.xda-developers.com/showthread.php?p=47820707#post47820707 When flashing the system sparcechunks keep note on the file name, it's named differently, so if you copy the command from the instructions it won't work because it's named differently on the zip.
After restoring to stock kitkat, update all the stuff on the playstore and then check for update, then you'll get the notification for lollipop. If you don't here is the OTA zip for lollipop, here is the Lollipop OTA for USA XT1034. https://drive.google.com/file/d/0B1zN8A3HtCVkdFF2b2dVU0hXUDQ/view?usp=sharing Copy it to your internal memory. Boot into stock recovery and follow the kitkat instructions to get the menu https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050 Select update from sdcard and select the ota zip and it will update to lollipop.
edit: I just noticed that the stock lollipop firmware for american xt1034 is available http://www.filefactory.com/file/149mdexndh9n/XT1034_FALCON-RETUAWS_5.0.2_LXB22.99-36_19_cid9_CFC_1FF.xml.zip You can skip installing kitkat and just flash the images via fastboot with the instructions I mentioned above.

edit: I just noticed that the stock lollipop firmware for american xt1034 is available You can skip installing kitkat and just flash the images via fastboot with the instructions I mentioned above.
Click to expand...
Click to collapse
Well I tried this first and it acted correctly, but never went past the unlocked bootloader screen. (I left it there for 15 mins or so.) So I did the downgrade to 4.4.4 again and was able to get into the os, and then copy the ota over and apply it using stock recovery.
Thank you very very much.
I've missed my Moto g.
Later,
dabone

dabone said:
Well I tried this first and it acted correctly, but never went past the unlocked bootloader screen. (I left it there for 15 mins or so.) So I did the downgrade to 4.4.4 again and was able to get into the os, and then copy the ota over and apply it using stock recovery.
Thank you very very much.
I've missed my Moto g.
Later,
dabone
Click to expand...
Click to collapse
I'm glad it worked! I think I know why your first attempt didn't work. There are 4 sparsechunk files in the zip and the link with the instructions only has commands for the first 3. You have have to copy the sparsechunk command again and change the number from 3 to 4 or .2 to .3 depending on how it's labelled in the zip.

CM13 unofficial obake radio wont turn on,sim detected no signals.

device: droid mini xt1030
what ive tried: clean install (wiped cache,data,system etc)
method of flashing: first flashed cm13 unofficial obake via twrp 2.8.4.0(clean) then gapps and reboot.
problem: everything works and rom is smooth, nightly dated sep 22 2017,but all nightlies have same problem. no sim signals,phone info says radio off wont turn on via *#*#4636#*#*. installed many times over,rsd lite-d to stock then tried again,same issue.

zeronexus said:
device: droid mini xt1030
what ive tried: clean install (wiped cache,data,system etc)
method of flashing: first flashed cm13 unofficial obake via twrp 2.8.4.0(clean) then gapps and reboot.
problem: everything works and rom is smooth, nightly dated sep 22 2017,but all nightlies have same problem. no sim signals,phone info says radio off wont turn on via *#*#4636#*#*. installed many times over,rsd lite-d to stock then tried again,same issue.
Click to expand...
Click to collapse
Hi Zeronexus,
Details please:
1] Which bootloader and baseband are you on?
2] What was the last stock firmware version you flashed?
3] Does your radio work on stock firmware?
4] Who is your carrier? GSM or CDMA?
5] Do WiFi, Bluetooth and GPS work?

pbarrette said:
Hi Zeronexus,
Details please:
1] Which bootloader and baseband are you on?
2] What was the last stock firmware version you flashed?
3] Does your radio work on stock firmware?
4] Who is your carrier? GSM or CDMA?
5] Do WiFi, Bluetooth and GPS work?
Click to expand...
Click to collapse
1]bootloader : 30.BA (unlocked) baseband : SU6-7.7_23255_132_81_03R
2]last stock firmware used CFC_obakem_verizon-user-4.4.4-SU6-7.7-release-keys0
3]radio works but needs to toggle airplane mode after restart,no issues afterwards.
4]Telenor Pakistan,gsm.
5]wifi Bluetooth and gps work,everything works except sim on cm13.

zeronexus said:
1]bootloader : 30.BA (unlocked) baseband : SU6-7.7_23255_132_81_03R
2]last stock firmware used CFC_obakem_verizon-user-4.4.4-SU6-7.7-release-keys0
3]radio works but needs to toggle airplane mode after restart,no issues afterwards.
4]Telenor Pakistan,gsm.
5]wifi Bluetooth and gps work,everything works except sim on cm13.
Click to expand...
Click to collapse
Hi Zeronexus,
The obake platform defaults to an expectation of a CDMA network that is configured like Verizon Wireless in the US.
To configure as a GSM phone, you need to issue the following command in bootloader mode:
fastboot oem config carrier gsm
I use Verizon in the US, so I've never tried it on GSM networks, but that's the instructions in the LOS obake README file:
https://github.com/pbarrette/android_device_motorola_obake
Hopefully that works for you.

pbarrette said:
Hi Zeronexus,
The obake platform defaults to an expectation of a CDMA network that is configured like Verizon Wireless in the US.
To configure as a GSM phone, you need to issue the following command in bootloader mode:
fastboot oem config carrier gsm
I use Verizon in the US, so I've never tried it on GSM networks, but that's the instructions in the LOS obake README file:
Hopefully that works for you.
Click to expand...
Click to collapse
tried the fastboot command,doesnt work even though it says ok in fastboot. in phone information it says gsm service: radio off (*#*#4636#*#*)

Anyone who can help?

zeronexus said:
Anyone who can help?
Click to expand...
Click to collapse
Hi zeronexus,
At this point, I'm not sure what you can do.
Basically, you have problems with the radio even using stock firmware. Granted, you have a workaround, but it's still not operating correctly.
So it could be that you have a hardware error.
Or, it could be that your SIM is giving bad instructions as to which radio configuration to enable.
That could be due to having a bad SIM card, or having some kind of incompatibility between your carrier and the phone's radio.
You could post the output of a "adb shell logcat -b all" and a "adb dmesg" performed immediately after a reboot.
I'll have a look at them, but I've never been that great at parsing logcat or dmesg files. Maybe someone else will also see them and have a better understanding.
The other thing you can try is finding the newest possible Pakistani ROM for the Moto-X (2013 model, code-named "ghost"), or for the Droid Ultra. You should be able to flash the radio for that to your Mini since they share the same hardware.
You could try different versions of radio firmware for the obake, obakem and ghost platforms and see if any of them work.
You would have to extract the "NON-HLOS.bin" and "fsg.mbn" files from the stock ROMs and do:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

Thanks a lot sir! Even though my issue didn't resolve I appreciate your timely response will try to do what u said,I'm quite familiar with flashing.

If it makes any difference, my device says "device unlocked status code 1" and says Motorola confidential property " on the top,no Verizon logo. These devices have been shipped a lot recently to Pakistan and I doubt these testing devices should be up for sale legally.

It also has a factory mode and some additional boot loader options not available in other droids,I flashed a normal stock ROM but the one it was shipped with had an "S" instead of the KitKat "K" when tapping on android version.

Fun variant on XT1039 'radio off' issue

A little over a week ago I started having the fairly common issue on my (hitherto completely unmodified XT1039 where the radio is turned off and can't be turned back on again.
Following advice from similar threads on this forum, I unlocked the bootloader, installed TWRP and flashed the stock 5.1 ROM found in this thread as Retail EU 5.1 ROM (Optimized) v1.1: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Didn't get anywhere so I flashed the radio firmware provided in that thread. Symptoms remained the same:
5.1: SIM reads fine, WiFi works, radio off, IMEI reads fine
Following another thread, I tried downloading the stock 4.4.4 ROM from https://firmware.center/firmware/Motorola/Moto G (1st gen-2013)/Stock/XT1039/
Being a beginner, I ran into difficulties with manually flashing the xml.zip ROM - but on a hunch I tried flashing the radio firmware only.
Surprisingly, this worked - kinda. Having done that, I had a system where the radio worked - but the SIM wouldn't read, and the WiFi wouldn't turn on. I quickly figured out that I could switch between the two states by flashing the 5.1 or 4.4.4. radio firmware:
5.1: SIM reads fine, WiFi works, radio off, IMEI reads fine
4.4.4: No SIM, no WiFi, radio on, IMEI reads fine
Running out of ideas, I tried flashing LineageOS, only to get yet another configuration:
Lineage: No SIM, WiFi on, radio on, IMEI won't read
However, with Lineage running, I could flash the relevant 5.1 or 4.4.4 radio firmware to get those states back.
Finally, tried installing 4.4.4 from https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
This gives me the same set of symptoms I had originally (SIM reads fine, WiFi works, radio off, IMEI fine), whatever radio firmware I flash.
I am at this point pretty stumped - this is my personal phone so would be pretty pleased to get it up and running again. Any kind souls have useful ideas on what my next steps should be?

Where can I get the proper radio band for China version?

In order to use the Taiwanese system, I have done as this post says on my Chinese version of u11+, but the TW Radio band here doesn't match my China Telecom SIM card. Previously there were "Global" and "Cellular 800" in the "Select Radio Band" menu, but now the two options are gone. So could anyone please tell me how to fix this, or where to find the correct radio band to flash? Thanks a lot!

Now the major problem is I can't reboot to download mode, which means I can't flash anything with fastboot. Previously I replaced twrp with an wrong version of official recovery, under which adb doesn't work. In system I'm able to use adb under usb debugging, but the dd command in adb shell fails. Seems that the only thing I can do now is to use the existing system, unable to flash or change anything else. Would anyone please have a fix for this? Thank you!

Help: incompatible radio.img caused sim slots to become non-functional

Hi
Right after the smashing success of my first request (TIGCA firmware), I have no other hope but to ask for help regarding the radio.img.
If I am not severely mistaken, my phone was XT2073-1 (one fusion 64gb rom) with android 10 from TIGCA channel (Latin America).
What happened is: I updated to android 11 using a verizon channel rom first ( I had no clue it was verizon, loli mirror never mentioned it). I found out it is verizon when the fastboot installation went awry and I was presented with the Verizon fastboot. Verizon is very jealous about its devices, more like the sultan's harem.
Anyhow, a reinstallation with RETAPAC channel version fixed everything except the sims...both sims are not working. Not working in the sense that the cellular company carrier is identified correctly but no signal.
I tried lots of things:
1- Reinstalling different roms: RETMEA, RETAIL, GSI PIXEL, nothing happened, same problem.
2- Enabling hidden menu *#*#4636#*#* and changing band frequency from there: it was always automatic, except with pixel 3 more options out of a long list, still didnt work.
3- Disabling CQATest, bp-tools startup. nothing.
My idea is; if I find TIGCA rom or at least TIGCA radio.img and install it this could fix the problem, but no sign of TIGCA for 2073-(1) yet.
If someone can put me in the right direction. Maybe how to edit the radio.img of TIGCA 2073-2? Or the right commands in shell to fix the bands maybe? I am clueless, any help would be appreciated.