Baseband

[dethrok]

I'm about at my wits end trying to figure out this problem of mine.

Here's a quick overview of my situation, so I don't have to go through it again:
http://forum.xda-developers.com/showthread.php?t=1301091



Anyways, I decided to take another shot late at night to see if I could get this working. I'm running on 3.2.2 right now, build HLK75D, with no 3G/4G connectivity. I looked at a screen shot of a stock updated 4G Xoom's settings and I noticed that my baseband is the only thing different.

Is there some way to change the baseband from what it is now (CDMA_N_03.1A.54P) to "CDMA_N_03.1A.52P ltedc_u_05.15.00"?

 

[Jewremy]

I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.

 

[dethrok]

I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.

Yeah, well, I don't have either 3G or 4G. My Xoom says activation successful over Wi-Fi, and I have full signal with the Verizon towers, but it just doesn't connect.

I still haven't heard anything back from Motorola regarding any way to get the baseband back to the LTE version.

 

[hammer4203]

Guys use Motorola stock imgs, but remove your sim card after you flash it. See if it connects to 3g then. If not look for the hlk75c stock root on here flash that with your sim in.

Sent from my Xoom using xda premium

 

[hammer4203]

HLK75C is the Verizon one. Try to flash this.

http://forum.xda-developers.com/showthread.php?t=1294824

Sent from my Xoom using xda premium

 

[Jewremy]

HLK75C is the Verizon one. Try to flash this.

http://forum.xda-developers.com/showthread.php?t=1294824

Sent from my Xoom using xda premium

We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.

 

[hammer4203]

Did you flash hri66? What kernels have you tried? Oh and are you in a 4g area, cuz that can cause an issue if your not.

Sent from my Xoom using xda premium

 

[hammer4203]

http://forum.xda-developers.com/showthread.php?p=18224270

AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.

Sent from my Xoom using xda premium

 

[dethrok]

http://forum.xda-developers.com/showthread.php?p=18224270

AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.

Sent from my Xoom using xda premium

I've tried AceXMachine's solution. Still no deal.

No matter what image I've used, I still have no option for LTE in my mobile network settings. My baseband still has never changed back to LTE.

I live in the dead center of a strong 4G area. My 4G was working fine prior to making the stupid mistake of flashing over what Motorola sent back.

We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.

And that is exactly what mine says when I power up BP.





I just received a total generic e-mail response from Motorola telling me to make sure to check for updates, etc.

I replied to them and told them that my baseband is the wrong version and that my LTE radio is turned off. Lets see if they can provide anything to help out.

 

[hammer4203]

Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.

Sent from my ADR6400L using xda premium

 

[dethrok]

Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.

Sent from my ADR6400L using xda premium

I think it involves pulling your build.prop?

http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/

 

[Jewremy]

I think it involves pulling your build.prop?

http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/

No. This is lower-level software. It's part of the bootloader, governs the radio. The build.prop files are the same between 3.2.2 back from moto and 3.2.2 upgraded from stock.

 

[hammer4203]

I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.

Sent from my Xoom using xda premium

 

[zarkuu]

I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039

Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.

 

[Jewremy]

I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.

Sent from my Xoom using xda premium

It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.

It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. EDIT: Nevermind. Don't bother.

I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039

Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.

See above in this same post.

 

[dethrok]

Well, this is all hurting my head. Motorola e-mailed me back and said they were bumping my case up to their repair escalation team and I'll be getting a call in 1-2 days.

Hopefully they'll still help me out when it was my own stupid fault that I screwed up my connection. Maybe they'll be able to give me a solution to turn the radio back on.

 

[zarkuu]

It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.

It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. I'm thinking the baseband is contained in the ebb partition, also known as the bootloader. Reflashing the bootloader is extremely risky. You really don't want to do that. It's at /dev/block/mmcblk1p1. Controls the whole boot sequence. The HTJ85B update overwrites/updates the bootloader, which is what could cause our issue.

OK, this makes sense to me since I have flashed back to HRI66 and did OTA updates to HTL85B and nothing else would presumably have changed it back. My mistake was probably allowing the device to boot under HTJ85B. If I had just done it through recovery and then flashed back to HLK75C it wouldn't have touched the bootloader. I bet some people didn't do that and so they work when flashing various restores. I understand it is risky to flash the bootloader (because if it goes wrong you won't be able to even go to fastboot) but what other option is there other than RMA back to Moto? Do we think Moto will be releasing stock images for this new bootloader anytime soon? That's really more of a rhetorical question I think.

I guess if someone wants to try making a backup I might try flashing it.

From http://forum.xda-developers.com/showthread.php?t=1294824
Pulling your own images
1. Flash a custom recovery
2. Boot straight into recovery.

adb shell
mount /data
mkdir -p /data/media/images
dd if=/dev/block/platform/sdhci-tegra.3/by-name/ebb of=/data/media/images/bootloader322.img
sync

Then reboot back into android and pull it off your device.

 

[hammer4203]

See if you can use this.

http://forum.xda-developers.com/showthread.php?t=1270848

Sent from my Xoom using xda premium

 

[mmayhew]

I'm in the same boat: http://forum.xda-developers.com/showthread.php?t=1299485

Hopefully we'll find an answer soon.

 

[zarkuu]

See if you can use this.

http://forum.xda-developers.com/showthread.php?t=1270848

Sent from my Xoom using xda premium

No dice. I've checked all the OTA updates I know about:

19dea2ba1ae5.signed-trygon-HTJ85B-from-HMJ37.19dea2ba.zip
7a15c95f18ba.signed-trygon-HLK75-from-HLK42B.7a15c95f.zip
7ac6aeb09117.signed-trygon-HLK75D-from-HLK75C.7ac6aeb0.zip
a5de99b3e437.signed-trygon-HMJ37-from-HRI66.a5de99b3.zip

In HMJ37 from HRI66 (3.0.1 to 3.1) I see a bootloader.bin along with this in the updater-script

assert(package_extract_file("bootloader.bin", "/tmp/bootloader.bin"),
       moto.set_mbm_update("/tmp/bootloader.bin"),
       delete("/tmp/bootloader.bin"));

There is nothing else that does an "set_mbm_update" in any of the other updates.

On the upside the md5sum of this bootloader.bin matches my own dd dump of the ebb partition.

c3a74df4a356c0e4158fd592cc8be693  bootloader.img
c3a74df4a356c0e4158fd592cc8be693  /tmp/updates/bootloader.bin

I'd be interested to see if someone can take a dump of their ebb partition as I documented earlier and see if the md5sum matches. if it does, then we will know the bootloader is not the problem. If not, then this is something new to try. Basically we need the dump and then an update.zip to flash it. If someone can provide the dd dump then I can make the update.zip. That should be safe enough to flash I think.