Failed to download info about updates

[Zer0t3ch]

The Manage ROMs screen is correctly displaying my ROMs, but the Install/Update screen is seemingly displaying [at least some] of the correct information. Mine is as follows:

MultiROM: v32a
Recovery: 2015-06-30
Kernel: has kexec-hardboot patch

At the bottom of the panel though, it says: Failed to download info about updates

Is this to be expected? Is there something (hopefully temporary) wrong with whatever server is serving the update information? If it helps, it seems to actually take a small bit of time when attempting to retrieve the update info. (Seems long enough that it's recieving something, and short enough that it's not just timing out)

Screenshot: http://i.imgur.com/xTsGQMr.png

[Tasssadar]

Which device do you have? If it is one with an unofficial port, report this to its maintainer.

[Tasssadar]

Since the version numbers are the same, I'm gonna go ahead and assume you have one of the nexus devices supported by me. Can you get me a logcat?

 adb logcat -c
 # reopen the app on the phone or refresh it, so it tries to download it again.
 # Continue after it shows that red error message
 adb logcat -d > logcat.txt

[Zer0t3ch]

@Tasssadar Thanks for the quick reply.

This is on a Nexus 6 (shamu) which doesn't seem to be listed as officially supported in your GitHub wiki, but it was posted by you in xda-developers. I am certain that MultiROMManager used to be able to find and download updates.

I noticed the MultiROMManager version is v32a, but I'm pretty sure I've seen a newer version somewhere. Odd because I know I'm on the latest Play Store version.

I hope it's not too much to sift through.
http://pastebin.com/4VPtWwPY

On a sidenote, is there any reason for anything related with MultiROM to cause random and sudden reboots? (CM12.1 with Hydra Kernel, but I get it with all kernels)

[Tasssadar]

EDIT: On the other hand, you seem to be able to work with adb - before you do what I described below, can you get me the files, maybe that's gonna help me debug it (I'm asuming multirom is installed on that device, so I'm using busybox from it):

adb shell
su
cd /data/data/com.tassadar.multirommgr
/data/media/0/multirom/busybox tar -czf /sdcard/mrom_data.tar.gz ./
chmod 777 /sdcard/mrom_data.tar.gz
exit
exit
adb pull /sdcard/mrom_data.tar.gz

Can you get me that mrom_data.tar.gz archive? Also, which version of the MultiROM Manager app do you have?

ORIGINAL:

 E/MROMMgr::Manifest(20993): Manifest signature verification failed!

Interesting. Must be a corrupted download that got cached for some reason. Go to settings, apps, find multirom manager, erase its cache and force stop it and open again, that should fix it. This shouldn't really happen though :/

[Zer0t3ch]

This fixed it, thank you.

[Zer0t3ch]

@Tasssadar Ok, while your suggestion did fix it temporarily, it returned again. I appear to be able to fix the problem every time it shows up by clearing the app's cache/data.

I just saw the edit you made to your comment, so here's the tarball of the data folder: Is dropbox okay?

MultiROMManager has it's version listed as 1.186 in the settings, it should be the most up-to-date from the Play Store.

[Zer0t3ch]

Just to update this, I've confirmed this is not caused by the specific ROM I was running at the time. I have gotten this problem on xTraSmooth (Marshmallow stock-alike), Chroma (AOSP-based 5.1.1), and CM12.1

[marco664]

Buenos días tengo el mismo problema con mi htcm8 como puedo solucionarlo gracias