My list of compiled Roms for Motorola Xoom

[d13g0oo]

Installed CM11 for Wingray this morning over a OMNIRom version that was exceedingly problematic.

So far, so good, other than being a bit lethargic. Is there a way to overclock under CM11?

chris

What is the most stable and fastest room for motorola xoom today? I just need chome and youtube.

 

[akira_yuki]

This is the forum for the roms I compile for Motorola Xoom.
I have nicknamed these future roms Moto-Rola for personal reasons. xD
I will try to make them faster and put some cute things on them, even if I start with KitKat versions.
As you all know, I am currently using some of Schischu's sources, I am just following his hard work and making it available for everyone.

This first rom is the Cyanogenmod 11 version for Motorola Xoom Wingray you already know.
I will compile next the Everest version, you will have to try it for me if I am able to do it. I do not have the everest version of the Motorola Xoom so...

https://www.dropbox.com/sh/1fxrnv2ce8fyjyn/AABHGMZcGCYBYqtDSvMMpXC-a?dl=0
Here are the links (up here) It is a dropbox folder with everything you need.

TWRP 3.0.1 recovery with sdcard support.
CM11 for wingray
Open gapps Kitkat pico version
Open gapps Kitkat nano version
Supersu.
Omnirom 4.4.4.
Thank you for your support!


XDA:DevDB Information
Moto-Rola ROMS, ROM for the Motorola Xoom

Contributors
Manuellama
Source Code: https://github.com/Manuellama/android/blob/android-4.4/default.xml

ROM OS Version: 4.4.x KitKat
ROM Firmware Required: BigParted Recovery
Based On: CyanogenMod 11

Version Information
Status: Stable
Current Stable Version: 4.4.4
Stable Release Date: 2017-05-06

Created 2017-05-06
Last Updated 2018-01-20

Hi!! could you please provide some guide on how you build it from source code? I'm actually configuring the environment to build LineageOS 14.1 but if you give me a little help I would really appreciate that.

 

[Manuellama]

#https://github.com/Manuellama/android/tree/android-4.4
#https://stackoverflow.com/questions/28379870/aosp-repo-sync-takes-too-long
#https://www.azul.com/downloads/zulu-community/?architecture=x86-64-bit&package=jdk

repo init -u git://github.com/omnirom/android.git -b android-4.4
repo sync -c --no-clone-bundle
source build/envsetup.sh
brunch wingray

You will have to download openjava 6 from azul/zulu link, I think it is the one that KitKat uses.
I did not check those sources in a long time, I think you will find building errors.
Anyway, if you have any doubts, ask.

If you build it successfully, the zip is on the out directory, in the subdirectory wingray.
As it has passed so long time since I built the wingray rom using the Schischu code, I do not remember many things. I will try my best to solve your questions anyway.

 

[Diagon]

Edit: Having done a lot more reading since this post, I'm editing it with my answers ...

I'm on an LTE upgraded MZ600 / stingray. I found TWRP's for both winray and stingray here, but I wasn't able to find any but broken links for the stingray/BigPart version. (@Kovaelin 's link is no longer working, either.) Could someone point me to it or reup?

Edit: The most recent TWRP recoveries, 2.8.x.0, both BigPart and non-BigPart, are here. Though there is one more recent, linked in the OP on this thread. Manuellama's dropbox link includes a TWRP-3.0.2-BigPart, though it's only labeled as twrp3sd.img.

I'm noticing that for the Nook Tablet, when the repartitioning recovery is not available, others are making do with a printout of the partition table, which they then write using adb with sgdisk or parted. eg. here. So maybe someone might upload a printout of the before/after partition table? That could be useful for future travelers.

Edit: Conversion from non-Bigpart ot Bigpart is described at the BigPart Repartition Upgrade and Resource Center. Conversion back from BigPart to non-BigPart is described here. Printing out the partition table might still be a good idea, but maybe someone's done it there. If not, I'll do it myself. [I couldn't figure out how to do it. `fdisk` doesn't see a partition table.]

Finally, @Manuellama , the only ROM I'm seeing for stingray in your dropbox, is omni-4.4.4. I'm wondering if anyone has a copy of CM11? Are these two the most up-to-date ROMs we've got?

Edit: I gather that flashing Wingray ROMS works on Stingray, though 4G/LTE will not work. That's ok with me, so the CM11-wingray ROM should do.

Thanks for all your work!

 

[Diagon]

I found that some of those files are corrupt. I had better luck here, if anyone runs into trouble: https://drive.google.com/drive/folders/1ykMWK3pueLZwcxJlSrsS-uEr0y_-DmfI

Kovaelin - that google drive link is broken. Any chance you could reup any of those you had trouble with? I'd certainly appreciate not flashing corrupt files.

 

[Diagon]

If anyone has thoughts on the best non-BigPart ROM, I would appreciate it. I have yet to unlock/root my Xoom/Stingray, which is still running stock 3.2.6. I would probably try that first, before exploring BigPart and CM11.

Edit: If I've got it right, there should be 3 choices:

1. Team EOS XOOM JB 4.1.1 Stingray MZ602 NIGHTLIES
2. [ROM][JB] Team EOS 3 (Stable release)
3. [ROM][NIGHTLY] CM10.1 (Wingray/Stingray/Everest)

I haven't looked closely at whether the Team-EOS threads have the necessary files available, but I did find all the CM nightlies on the internet archive.

Edit: Using F-Droid I found that there are so few apps on these early versions of Android, that it's not really usable. Even the ebook readers are quite clunky, and none of the browsers work. So I did move to BigPart and am experimenting with those ROM's now. The 4.4.4 ROM's work well but don't have much more software. The 5.1.1 ROM has many bugs, but there is more in the way of working apps. I haven't yet tried 6.0.1.

 

[Diagon]

@Manuellama - Do you know if your twrp3sd.img will work for the BigPart conversion procedure?

BigPart Repartition Upgrade and Resource Center

Edit: I ended up using R.A.H._TWRPv2.6.3.zip (non-bigpart) and R.A.H._TWRPv2.6.3_BigPart_selinux.zip (bigpart) for that procedure. I found them both in the OP, here. Once finished, I then flashed TWRP-3.0.2-0 from the OP in this thread (called twimg3sd.img in the Dropbox).

 

[Kovaelin]

If anyone has thoughts on the best non-BigPart ROM, I would appreciate it. I have yet to unlock/root my Xoom/Stingray, which is still running stock 3.2.6. I would probably try that first, before exploring BigPart and CM11.

Edit: If I've got it right, there should be 3 choices:

1. Team EOS XOOM JB 4.1.1 Stingray MZ602 NIGHTLIES
2. [ROM][JB] Team EOS 3 (Stable release)
3. [ROM][NIGHTLY] CM10.1 (Wingray/Stingray/Everest)

I haven't looked closely at whether the Team-EOS threads have the necessary files available, but I did find all the CM nightlies on the internet archive.

I'm not sure if you should worry about non-BigPart ROMs, but if you really wanted to play with it, then I think I started with the recovery-Tiamat-R4c-100611-1150-cwm.img file: http://www.mediafire.com/file/47l7ds9g0dwvd1w/recovery-Tiamat-R4c-100611-1150-cwm.img

@Manuellama - Do you know if your twrp3sd.img will work for the BigPart conversion procedure?

BigPart Repartition Upgrade and Resource Center

It's been a while, but I believe that one does indeed work.

Kovaelin - that google drive link is broken. Any chance you could reup any of those you had trouble with? I'd certainly appreciate not flashing corrupt files.

The original link was not mine, and I can't remember specifically which files were corrupted. However, I believe I kept the replacement files relevant to MZ604.

Here's everything that I thought was worth keeping: https://mega.nz/folder/Qtlh2IhA#g1zrlhV8HOpV9ggHYhmceg

Omni was working for a while, but Google pushed some change that caused issues back in August (as you probably gathered from the most recent posts). I didn't check if a newer version of GApps fixed things again, because I wanted to hand the tablet over to my parents. Eventually, I settled back on CM11.

However, I would rather stick with Omni for more up-to-date features. So, please let me know if you manage to get it to work.

 

[Diagon]

I'm not sure if you should worry about non-BigPart ROMs, but if you really wanted to play with it, then I think I started with the recovery-Tiamat-R4c-100611-1150-cwm.img file: http://www.mediafire.com/file/47l7ds9g0dwvd1w/recovery-Tiamat-R4c-100611-1150-cwm.img

I was actually able to install CM10.1, going right from the non-BigPart TWRP 2.8.0.0. I see the problems with this ROM, though. I could use it for reading ebooks, but that's just about it. VLC crashes, no browser. I will definitely need to move to BigPart.

[...] Here's everything I thought was worth keeping: https://mega.nz/folder/Qtlh2IhA#g1zrlhV8HOpV9ggHYhmceg

Thank you! I got it.

Omni was working for a while, but Google pushed some change that caused issues back in August .... I didn't check if a newer version of GApps fixed things again, because I wanted to hand the tablet over to my parents. Eventually, I settled back on CM11.

However, I would rather stick with Omni for more up-to-date features. So, please let me know if you manage to get it to work.

I'll do that, though I tend to stick to F-Droid. Maybe I'll check in later and we can compare notes about what's working and what's not. Thanks for your input.

 

[Kovaelin]

I'll do that, though I tend to stick to F-Droid. Maybe I'll check in later and we can compare notes about what's working and what's not. Thanks for your input.

Sounds good. I'll let you know if I take another crack at it in the future, but I don't have it handy at the moment.

Sticking to F-Droid is probably the most stable option. However, it would be also be great to have the option for more apps. Omni 5.1.1 seemed like it was the only option for that, until it stopped working over the summer. If you find a way to get it to work again or any other options, please feel free to share. I think dozens of us would really appreciate it!

 

[Diagon]

Here's everything that I thought was worth keeping: https://mega.nz/folder/Qtlh2IhA#g1zrlhV8HOpV9ggHYhmceg

Kovaelin - I recognize everything else, but could you let me know what the files `H.6.2-21_Canada.zip` and `StockWiFiSystem.zip` are in that archive? That's if you remember, that is.

Also, there's a cm11-wingray.zip in the OP of this present thread (in Manuellama's drop-box), but another, cm-11-20150725-UNOFFICIAL-2201+0200-wingray, in the OP of this thread. Do you know the difference?

... t would be also be great to have the option for more apps. Omni 5.1.1 seemed like it was the only option for that, until it stopped working over the summer. If you find a way to get it to work again or any other options, please feel free to share. I think dozens of us would really appreciate it!

Is Manuellama still working on things? I'm not too versed in the modification of ROM's, though I was planning to get started reading this.

 

[Kovaelin]

Kovaelin - I recognize everything else, but could you let me know what the files `H.6.2-21_Canada.zip` and `StockWiFiSystem.zip` are in that archive? That's if you remember, that is.

Also, there's a cm11-wingray.zip in the OP of this present thread (in Manuellama's drop-box), but another, cm-11-20150725-UNOFFICIAL-2201+0200-wingray, in the OP of this thread. Do you know the difference?

Is Manuellama still working on things? I'm not too versed in the modification of ROM's, though I was planning to get started reading this.

`StockWiFiSystem.zip` is just the stock image, in case you want to restore to factory settings. `H.6.2-21_Canada.zip` should basically be the same thing. My device was purchased in Canada, so I included it just in case if region mattered (it does not seem to matter).

I don't know what's up with `cm-11-20150725-UNOFFICIAL-2201+0200-wingray.zip`. I don't think I ever tried using that one.

I have not heard of any new progress from Manuellama either, unfortunately.

 

[Diagon]

`StockWiFiSystem.zip` is just the stock image, in case you want to restore to factory settings. `H.6.2-21_Canada.zip`

Thanks. Which device do you have? I have the MZ602, and have been looking for stock. The Marshmallow thread referred to this really great site for ROM's, but the google drive is refusing to offer the download.

 

[Kovaelin]

Thanks. Which device do you have? I have the MZ602, and have been looking for stock. The Marshmallow thread referred to this really great site for ROM's, but the google drive is refusing to offer the download.

Same as above. MZ604 Wingray.

 

[Kovaelin]

I'm still trying to find more on `cm-11-20150725-UNOFFICIAL-2201+0200-wingray.zip`, but I can't find where it originally came from. I thought the version I had was the latest one, but now I wonder if I missed something. I also can't remember why I didn't keep Marshmallow runbning - it may have been due to instability or missing features. I wouldn't mind losing the camera if it meant getting Google Play to work again though.

 

[Diagon]

I'm still trying to find more on `cm-11-20150725-UNOFFICIAL-2201+0200-wingray.zip`, but I can't find where it originally came from. I thought the version I had was the latest one, but now I wonder if I missed something.

Ya, I haven't read this whole thread yet, so I'm not sure what Manuellama was doing with CM11 (if anything). But the CM11 here is *smaller* than that 2015 one I linked above.

I also can't remember why I didn't keep Marshmallow - it may have been due to instability or missing features. I wouldn't mind losing the camera if it meant getting Google Play to work again.

I just finished that whole thread. Manuellama was working on it, but getting a bit over-extended. Lolipop became Marshmallow became Oreo ... and she then seemed to drop it. S/He had a couple of modifications in that thread whose links still work, along with a reup. The original is also reuped in that thread.

I just finished the Lolipop thread. I see you tried that one, too, but I gather you're back to CM11. I understand that a few things are broken there, like camera, HDMI and hardware videocoding. And now Gapps is broken too, yes? From reading the thread, Gapps seemed a little unstable on that ROM, with a number of people having problems. Did you try reflashing?

 

[Kovaelin]

And now Gapps is broken too, yes? From reading the thread, Gapps seemed a little unstable on that ROM, with a number of people having problems. Did you try reflashing?

I haven't tried since August, but it might work again now. I would probably try the pico version again if I were to give it a go. One of my friends recommended to try finding the google play services apk install and clear cache and storage if it starts to show the "Google Play has stopped working" message later on.

 

[Diagon]

Hi!! could you please provide some guide on how you build it from source code? I'm actually configuring the environment to build LineageOS 14.1 but if you give me a little help I would really appreciate that.

@akira_yuki - I'm a rank beginner in this area - though I do know something about linux - but I gather Android Go might be a better target for an older machine like this. i'm wondering if you made any headway?