Baseband

[zone23]

I'm in the same boat Motorola is looking into it for me as well. I talked to verizon and we agreed that there would be others like me. Motorola should have provided updated images on their website when they started upgrading xooms.

Sent from my Xoom using xda premium

 

[Jewremy]

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.

c3a74df4a356c0e4158fd592cc8be693 /sdcard/ebb.img is mine. We should be able to flash it...theoretically. I've already overwrote my nand before. Make sure you flash it to /dev/block/mmcblk1p1 from recovery if anything. Can it be done from fastboot?

 

[hammer4203]

Give up! My xoom just took a dump!

Sent from my ADR6400L using xda premium

 

[Jewremy]

Give up! My xoom just took a dump!

Sent from my ADR6400L using xda premium

Tried to flash the bootloader?

 

[hammer4203]

No the damn network went down and my wife still had data somehow, so I thought it took a dump. We need an emergency broadcast system to let us know these things! I reset my xoom so many times it ain't funny! I'm back up to par now though. As far as the base and goes it looks like anything that gets dumped is leaving out the radio for some reason. It won't dump the USB info at all. I have even tried to copy it file by file and it just leaves a blank folder or copies nothing. I really think they have figured a way to copy protect it somehow.

Sent from my Xoom using xda premium

 

[tonesto7]

Has anyone noticed the two radio img's located in the HLK75 from HLK42B zip file?

There is two of them... lte_bp_gota.img and cdma_bp_gota.img

 

[zarkuu]

Has anyone noticed the two radio img's located in the HLK75 from HLK42B zip file?

There is two of them... lte_bp_gota.img and cdma_bp_gota.img

I see them. In the updater-script we see

assert(motorola.motoflash(package_extract_file("cdma_bp_gota.img")));
assert(motorola.motoflash(package_extract_file("lte_bp_gota.img")));

I'm thinking this is flashing to boot/kernel as opposed to the bootloader which I saw earlier.

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

Does that make sense? motoflash is flashing boot and set_mbm_update is flashing the bootloader? If this is true then I'd think we would already have these as part of the various hlk75c backup images that are floating around which include the boot partition.

 

[vdelsan]

See if you can use this.

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

Sent from my Xoom using xda premium

can this be flash in recovery I'm currently on build number 4g/hlk42b and will i loose root thanks