Database Users

CyanogenMod for TouchPad Alpha 2.1 Released!

Hi everyone
Alpha 2.1 is Released!!!
http://rootzwiki.com/showthread.php?4011-RELEASE-ALPHA-Discussion-CyanogenMod-team-Touchpad-port
Post feedbacks, bugs and thoughts!

Installed alongside 3.0.3; no issues. The instructions were well-written, so I didn't have any trouble.
Seems to work well enough, haven't had a chance to extensively play with it.

... don't se the other several page long thread..
Posted from my cm7 alpha already! Now to install a thumb/split keyboard.. oh how I've been waiting for thee

bluetooth works for me. able to transfer files from my Galaxy S2
wifi works too. no drop or such.
gapps installed and could access certain market apps
most games i played on my Galaxy S2 works on the TouchPad
mass storage device works with 10gb of useable space
double boot was right on! though it takes alittle longer to start webos.
got me thinking if it was stuck at the HP logo
all in all great work. Your call this an alpha release?
Kudos to the CyanogenMOD team!

Those calls in the video were hilarious, I like the way they "called just by chance"

Works quite well, seems to die quite a bit when I lock it and then it won't wake up or it will wake up and the touchscreen won't work. I'm impressed though. Thanks CM Team.

help!!!
can anyone help me. im trying to do the command for acme installer but its not going thru in novcam. im trying to install from my pc windows 7. any suggestions?

No Clockwork Recovery
Somehow when I installed cm7 the clockwork recovery did not make it on to the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? Without
recovery I can't push google apps....Any help would be appreciated.
---------- Post added at 03:13 PM ---------- Previous post was at 02:24 PM ----------
Somehow when I installed cm7 the clockwork recovery did not make it onlt the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? With recovery I can't push google apps....Any help would be appreciated.

cbogiages said:
Somehow when I installed cm7 the clockwork recovery did not make it on to the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? Without
recovery I can't push google apps....Any help would be appreciated.
---------- Post added at 03:13 PM ---------- Previous post was at 02:24 PM ----------
Somehow when I installed cm7 the clockwork recovery did not make it onlt the touchpad. Any ideas about how I can write the recovery image now that it has this multi boot functionality? With recovery I can't push google apps....Any help would be appreciated.
Click to expand...
Click to collapse
I know ROM Manager is included so maybe you can flash it through that if it has the touchpad version.
Sent from my Nexus S running NSCollab ROM and Trinity T144 Beast Kernel.

Rom manager is only partially functional right now. As long as you reboot to recovery it works fine, though the CWM GUI still needs some work. Remember,we are using alpha software here. That said, other thanthe occasional app, the only issue I have really seen so far is some codex problems, occasional wifi drops and assorted odds and ends. CM did amazing work! I've tested beta software with more issues.
Sent from my HP Touchdroid using xda premium

Ok... First Thanks CM for getting this to us! Its very nice to have touchpad running Android.
I decided to try a couple things and now i can't revert back to find out and hoping some in here can help me.
I tried porting honeycomb over to the touchpad. Well it installed just fine, but now it seems as tho I have a hybrid of a rom. I have 2g/3g stuff (nothing works on there) but have adwlauncher and many more settings.
So, my question is, can someone pm me that is running this to see if we can compare systems. I can't format and go back to test things cause i tried.
Thanks,
~leo

Alpha 2.1 released!!!
updating now

xenocide976 said:
Alpha 2.1 released!!!
updating now
Click to expand...
Click to collapse
How do you update it?
Sent from my Nexus S running NSCollab ROM and Morfics Thermite Beast Kernel.

Why is this in WebOS Software Development category?

Just installed 2.1 on my Touchpad and it is pretty impressive for only being in Alpha stage.

benrees21 said:
How do you update it?
Sent from my Nexus S running NSCollab ROM and Morfics Thermite Beast Kernel.
Click to expand...
Click to collapse
copy the new update.....zip to the "cminstall" folder
then run novacom command and it will install the new 2.1 alpha
if u recently updated to webos3.0.4, u will need to start all over again for CM7 as it has deleted the moboot from /boot

xenocide976 said:
copy the new update.....zip to the "cminstall" folder
then run novacom command and it will install the new 2.1 alpha
if u recently updated to webos3.0.4, u will need to start all over again for CM7 as it has deleted the moboot from /boot
Click to expand...
Click to collapse
Thanks.
Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!

been working good for me for the past couple days

yah... been working good for me thus far too!

Only bit I'm confused about is what terminal to run novacom ? Bash, dos prompt ?
Sent from my GT-I9100 using XDA App

CWM touch edition for i9001

As I use "CWM touch" since some time and have no problems,
I like to offer the single post of czobor (http://forum.xda-developers.com/showpost.php?p=29258457&postcount=1573) as new thread.
The download link was: http://d-h.st/users/czobor
If there is already a new version of CWM as touch edition available it would be nice to post it here.
Experiences are always helpful to post.
The touch edition works for backups and restores of GB and ICS.

I think it's a good idea but you should've told czobor to open it. You know, for problems in this recovery instead of reporting it in CM9 thread
Sent from my S+ using XDA premium

OmarPlus said:
I think it's a good idea but you should've told czobor to open it. You know, for problems in this recovery instead of reporting it in CM9 thread
Sent from my S+ using XDA premium
Click to expand...
Click to collapse
Have informed czobor by pm before opening.
If there are any problems, please write it here for CWM touch.
I think it is better to read it at this point than distributed in different threads and places.
I only know that some people do not like the new style of backup in the file system of CWM6.
With the touch edition itself it is more secure to handle menus than without, because of "double click events"
which can not happen so often here.

Well my problem is :
It reads internal sd as external and vice versa. So if you backup to external it'll backup to internal and so on.. Also with installing zips.
Sent from my S+ using XDA premium

CWM 6.0.1.2
The new version or ClockworkMod is available for download, the download link is the same (http://d-h.st/users/czobor).
The non touch version is arco's one, but the touch one is mine. They're CWM flashable.
Enjoy!
Edit: Thread moved: http://forum.xda-developers.com/showthread.php?t=1843825

could someone provide an alternate download for cwm6012 touch? because i'm being unable to download it... it stops at 80 - 90 %...

czobor said:
CWM 6.0.1.2
The new version or ClockworkMod is available for download, the download link is the same (http://d-h.st/users/czobor).
The non touch version is arco's one, but the touch one is mine. They're CWM flashable.
Enjoy!
Click to expand...
Click to collapse
thanks czobor.
Just installed and works fine.

This is not development - it is discussion/Q&A. Moving this to the General section

Version 6.0.1.5 works well, or problems such as the 1.4?

[RECOVERY] [CWM Touch Recovery 6.0.2.8] [Updated 03-07-13]

Disclaimer
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
What is It
This is the latest version of CWM Touch Recovery (6.0.2.8) that I've built for the Touchpad.
It is a flashable zip so simply download the file and flash in your installed recovery.
It is also should be compatible to use with ACMEInstaller3.
I've uploaded the Touch version of CWM but touch doesn't work. However this version of CWM still has the enlarged icons like CWM Touch Recovery. It's really a CWM Touch Recovery but touch just isn't working yet. Touch should be working sometime this weekend. You can still navigate in this recovery with the hardware keys.
Changelog
CWM Touch 6.0.2.8 has the ability to "Install zip from sideload" while jcsullin's doesn't.
This allows you to use adb to install packages from your computer. Essentially you choose that option than run adb sideload flashable_zip_name (where flashable_zip_name is the path to the zip you want to flash). This prevents you from having to go into USB mode to copy over files to flash. Instead you just activate this and get it directly installed.
This was an intentional thing on jcsullin's recovery but has been fixed/enabled in this version (so basically not a problem with CWM itself).
This is probably not going to really sway very many of you but just keep in mind there are probably plenty of under the hood changes and ones I simply don't know.
Obviously, now this is the touch version of CWM but touch isn't working yet. Just use the hardware keys for now.
If I get any further changes I will post them here.
Downloads
Download No Touch Version Here
Download Touch Version Here
Bugs/Issues
If you have any issues please feel free to post them in this thread.
If someone thinks I should add more information to the OP just ask.

Hi, can you tell us what the difference is between your version and jcsullins version 6.0.1.9 please..
Thanks

these version numbers always confuse me. b/c if i look at cwm on google play store they list:
Updated:
February 16, 2013
Current Version:
5.5.2.3
is cwm 6x a beta or something? i can't find any info on the cwm website, or a changelog

x000x said:
these version numbers always confuse me. b/c if i look at cwm on google play store they list:
Updated:
February 16, 2013
Current Version:
5.5.2.3
is cwm 6x a beta or something? i can't find any info on the cwm website, or a changelog
Click to expand...
Click to collapse
I think what you are referring to is Rom Manager which is specifically designed to work with CMW much like Goo Manager is designed to work with TWRP an alternative to CMW.
The version I was referring to was written by jcsullins to overcome earlier versions corrupting the system along with moboot and the latest cm10 which most other versions for our TouchPad appear to be based on.

Works great so far! Thanks! :highfive:

-SGA- said:
Works great so far! Thanks! :highfive:
Click to expand...
Click to collapse
SGA can you tell us how this differs from jcsullins version. Thanks.

haha you're absolutely right sstar. when trying to find changelogs etc, i clicked on it through the clockwork website, and thought it was the same thing

sstar said:
Hi, can you tell us what the difference is between your version and jcsullins version 6.0.1.9 please..
Thanks
Click to expand...
Click to collapse
There is no official changelog for CWM so the answer is no I don't know the changes right now.
-SGA- said:
Works great so far! Thanks! :highfive:
Click to expand...
Click to collapse
Thanks for the feedback!
x000x said:
haha you're absolutely right sstar. when trying to find changelogs etc, i clicked on it through the clockwork website, and thought it was the same thing
Click to expand...
Click to collapse
It appears koush doesn't really say what every version has in it.

Remolten said:
There is no official changelog for CWM so the answer is no I don't know the changes right now.
Thanks for the feedback!
It appears koush doesn't really say what every version has in it.
Click to expand...
Click to collapse
Thanks for your reply but in the op you've said that you built this, so what changes have you made?

Re: [RECOVERY] [Remolten's CWM 6.0.2.8] [02-28-13]
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium

Anyone know Koush? If so, ask him for some details and post them here.

-SGA- said:
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for your reply . My understanding was that jcscullins developed one that did not corrupt the system as posted by nevertells.
Maybe I'm wrong, just don't like the idea of flashing something the poster/ developer can't give any details about.

-SGA- said:
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
SGA explains it perfectly.
sstar said:
Thanks for your reply . My understanding was that jcscullins developed one that did not corrupt the system as posted by nevertells.
Maybe I'm wrong, just don't like the idea of flashing something the poster/ developer can't give any details about.
Click to expand...
Click to collapse
I can't give any information as I don't know what koush edits and such in CWM I just built it for the Touchpad.
Only change that I can vouch for is the version has been bumped.

You can see the commits do dot really go into any kind of detail as to what the changes are: https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
Many of the moves to a higher version are only committed with a version number update.

-SGA- said:
You can see the commits do dot really go into any kind of detail as to what the changes are: https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
Many of the moves to a higher version are only committed with a version number update.
Click to expand...
Click to collapse
Noticed that too.
Also I noticed that the latest version of CWM for the Nexus devices is 6.0.2.3 so I'm not sure how the version incrementals work since CWM is available on loads of different devices. I've successfully built a CWM Touch for the Touchpad with no touch (however it has the enlarged icons but no touch yet). Will post soon if you just want a recovery with enlarged look.

Added changes (changelog) from jcsullin's CWM6 release.

Remolten said:
Added changes (changelog) from jcsullin's CWM6 release.
Click to expand...
Click to collapse
Thanks, where are they?

sstar said:
Thanks, where are they?
Click to expand...
Click to collapse
Sorry took time to write look for section called changelog.

Re: [RECOVERY] [CWM 6.0.2.8] [No Touch] [02-28-13]
Is there a way to configure Rom Manager to recognize this version of CWM Recovery?
Sent from my cm_tenderloin using xda app-developers app

masterosok said:
Is there a way to configure Rom Manager to recognize this version of CWM Recovery?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I would have to become the CWM Recovery Device Maintainer which isn't going to happen anytime soon as I'm not a prominent developer yet
Short answer is not yet.
Why do you need to use Rom Manager? Just download the file and flash in your current version of CWM Recovery.

[ROM][UNOFFICIAL][4.4.4][3.4 Kernel] CyanogenMod 11.0 Nightlies (tenderloin)

It's been requested that I create a new thread for this so as not to clog up @milaq's thread.
As some of you may have seen in flintman's Evervolv and milaq's CM threads, there has been a lot of work on the 3.4 kernel for tenderloin. Its a pretty awesome feat to have this running on our good ol tenderloin. =)
The gratitude for this kernel and build needs to be given to almost anyone but me. (Flemmard, flintman, jcsullins, Dorregaray and everyone that came before me on this device (dalingrin, green, and other's I'm sure that I'm missing)). I've had my tenderloin for quite awhile but never really done much with it until recently.
Anyway, without further ado, I present to you nightlies of CM-11.0 for tenderloin with a 3.4 kernel and -caf based HALs. Basically what this means is we'll be running the latest code from codeaurora on our msm8660 tenderloin.
THERE WILL BE BUGS! This thing is not perfect. It is still in active development.
CURRENT BUGZ (in no particular order):
- Bluetooth steals battery, but DOES work (jcsullins) - also sixaxis app doesn't work =(
- Camera is a bit derpy still, major wip, it takes pictures though (Dorregaray)
- Other stuff? Probably, yea
Destructions: PLEASE READ
1. This is a /data/media rom (relevant). What that means is you should be partitioned with a very small 'media' partition and a very large 'data' partition. The benefit of this is that your /sdcard and /data partitions share the big chunk of your usable space, just like any newer phone does these days. Use TPToolbox to achieve the new partition scheme: http://forum.xda-developers.com/showthread.php?t=2756314
2. You'll need a recovery that has both /data/media support and selinux support. Any of the following will work. Flashable via recovery.
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
3. Now you're ready to flash the rom. Downloads here: http://www.invisiblek.org/roms/cm-11.0/tenderloin/
4. Gapps here: http://wiki.cyanogenmod.org/w/Google_Apps
I'd recommend wiping data when coming to this rom or going to a different one (going between milaq's and this should be fine).
These are automatically built on my personal server at home and then uploaded. There may or may not be issues during the build times so don't always expect a fresh build every day. You can follow the automated twitter account here which will spit out a tweet once the build is finished uploading.
Sources:
-Kernel
-Device Tree
-CM Sources (the rest of what's needed)
There are a couple more changes and a couple other repos that are required to build this. Add this stuff to your .repo/local_manifests/roomservice.xml in order to build this yourself (after syncing the cm source of course)
http://pastebin.com/jKAMWM8T
You'll also need to cherry pick this commit from jcsullins: http://review.cyanogenmod.org/#/c/54380
Feel free to fork and fix!
Again -
Thanks to everyone that has contributed to making this rom.
Flemmard, flintman, jcsullins, dalingrin, green, milaq, the entire CM team and I'm sure many others.

Good new year present.

Looking forward to when Bluetooth is working. That and the black boxes were the only thing keeping me off KitKat.
Sent from my TouchPad using XDA Premium 4 mobile app

invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk

i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery

k4ever said:
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
vinukondamahesh said:
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
Click to expand...
Click to collapse
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.

allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk

k4ever said:
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
No clue. I heard of apps disappearing from the Google Home Launcher, but not getting completely removed or preventing apps from being installed. Is that the launcher you're using? Only remedy I heard from that (Milaq's CM11 thread, somewhere around page 40) was to just readd them from the app drawer.
Best advice is to wait for todays build to get uploaded and see what happens.

2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD

allstar319 said:
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
Click to expand...
Click to collapse
thank you its working nw

milaq actually has a flashable zip in his thread. that is the easiest. i was on 4.3 went into that recovery, made a backup then flashed the new cwm, rebooted recovery did a full wipe and flashed the rom and gapps and i am up and running. who would have ever thought we would have kitkat on a touchpad. not to mention a 3.x kernel. unreal, thanks for everyones work. Happy New Year

jerryatherton said:
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
Click to expand...
Click to collapse
Oops, I had the wrong image there. Link updated with the cwm =P
EDIT: Also added a flashable zip for it, had trouble downloading milaq's so I made my own =/

Anyone else getting a Core Process failure message when booting to the 01012014 Build?
I went back to the 12312013 build and all appears to be back to normal.
To be clear, I went straight to this build from a fresh CM9 image without booting into Android - ever. Got a second-hand device back from a relative, and pushed it to CM11, so it may have been a result of my own process.
I'll reflash 01012014 and see if the error persists.
--McBean

Really looking forwards to a stable version of this to try. Thanks for the effort.

BillzillaAus said:
Really looking forwards to a stable version of this to try. Thanks for the effort.
Click to expand...
Click to collapse
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk

k4ever said:
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.

allstar319 said:
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
Click to expand...
Click to collapse
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk

k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Click to expand...
Click to collapse
Also, the old kernel was preventing us from having "official" CM builds.

Getting SoD's once I turn the screen off. Tried the old way to fix that by raising the min clock, but that didn't seem to help. Any ideas?

k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
The 3.4 kernel, minimally, resolves an issues with the other CM11 builds where the core/stock apps were experiencing "black boxes" which prevented users from reading mail, using the browser to navigate and some other issues. Right off the bat, the new kernel resolves that issue.
--McBean

My list of compiled Roms for Motorola Xoom

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

Guys with wingray should tell us if they encounter problems. I have the everest, and can't try this.

I am grabbing this to try and get my winray going for the young bloke. I'll report back
---------- Post added at 10:39 AM ---------- Previous post was at 10:18 AM ----------
loaded up fine.. but I didn't do the google account or anything as I figured I'd have to get the "fixed" apk for google play services - but installed version is 11.0.38 - I'll do a factory reset and try a full setup

It works ok with the gapps included in the folder.

RaZz0Raus1980;72197561[/COLOR said:
loaded up fine.. but I didn't do the google account or anything as I figured I'd have to get the "fixed" apk for google play services - but installed version is 11.0.38 - I'll do a factory reset and try a full setup
Click to expand...
Click to collapse
What is this fixed apk that you are talking about please?
My Xoom is getting some gaaps stopped, google services stopped, etc that is driving me insane.
---------- Post added at 10:33 PM ---------- Previous post was at 09:50 PM ----------
RaZz0Raus1980 said:
I am grabbing this to try and get my winray going for the young bloke. I'll report back
---------- Post added at 10:39 AM ---------- Previous post was at 10:18 AM ----------
loaded up fine.. but I didn't do the google account or anything as I figured I'd have to get the "fixed" apk for google play services - but installed version is 11.0.38 - I'll do a factory reset and try a full setup
Click to expand...
Click to collapse
Manuellama said:
It works ok with the gapps included in the folder.
Click to expand...
Click to collapse
FWIW:
Manuellama you are a legend.
I installed these gaaps after a reinstall of cm11 and it does work great indeed. No more stopped services bull***
Thank you so much. I was so upset about loosing my Xoom. I have an Nvidia shield k1 but the Xoom is still a great device to have around.

munecito said:
What is this fixed apk that you are talking about please?
My Xoom is getting some gaaps stopped, google services stopped, etc that is driving me insane
Click to expand...
Click to collapse
Yep - flashed those files and seems 100% perrrrfect

Hi guys, thanks for the new build!
I would like a question, do I have to follow the procedures to in "BigPart Repartition Upgrade and Resource Center by realjumy" to format for bigpart?
I have a xoom GEDfied - It had a google official release. I am not sure if it was a UMTS or CDMA device before - it has a simcard slot.
I have tried the big part process many times and with no success - in the end, when flashing the CM 11 image, it says it is not a big part device... Is it because I am using wingray images?
Thanks very much!

In the dropbox folder there is a recovery you can flash, TWRP 3.0.1. with sdcard support...I suppose you need the bigpart thing to flash it.
But here it is how they did it for bigpart.
https://forum.xda-developers.com/showthread.php?t=2506997

Manuellama said:
In the dropbox folder there is a recovery you can flash, TWRP 3.0.1. with sdcard support...I suppose you need the bigpart thing to flash it.
But here it is how they did it for bigpart.
https://forum.xda-developers.com/showthread.php?t=2506997
Click to expand...
Click to collapse
Yeah, I have already tried that tutorial (like 10 times) for bigpart, no success.
Maybe it is something with my hardware (I am not sure if it is gsm, cdma or wifi) - everybuild I try says I don't have bigpart partitioning.
I will wait for an everest build

jubarim said:
Yeah, I have already tried that tutorial (like 10 times) for bigpart, no success.
Maybe it is something with my hardware (I am not sure if it is gsm, cdma or wifi) - everybuild I try says I don't have bigpart partitioning.
I will wait for an everest build
Click to expand...
Click to collapse
The easier way to know what variant is your Xoom is to check the model number at the back.
The problem you are going to have with most of the late builds is that they need big partition. So you need to find the easy to partition your tablet.

munecito said:
The easier way to know what variant is your Xoom is to check the model number at the back.
The problem you are going to have with most of the late builds is that they need big partition. So you need to find the easy to partition your tablet.
Click to expand...
Click to collapse
I will attach a picture here, I have not found the variant, I guess it is a prototype unit.
Yeah, bigpart is necessary...

https://goo.gl/photos/y8rQj2rNzU2d78PR9
@jubarim See that? My model number is mz601 (Everest) check your model number at the back of the tablet.

Thanks munecito! Mine don't have this sticker, I will post a picture tonight.

Well. It will help if you tell us if yours is a wifi only model, LTE? Where did you buy it (country)? Does it have a branded rom installed? Anything at all to identify it.
---------- Post added at 10:14 PM ---------- Previous post was at 10:08 PM ----------
kerry_xu_cs
12-02-2012, 10:47 AM |#10
Member68 posts Thanks: 13
boot into fastboot mode
plug your usb
use
fastboot getvar all
command to check the model

Uploading everest build to the dropbox folder.
I am not 100% sure it will work, but please try it and tell me.
It will take 1 or 2 hours to upload so now it is still not there.

Manuellama said:
Uploading everest build to the dropbox folder.
I am not 100% sure it will work, but please try it and tell me.
It will take 1 or 2 hours to upload so now it is still not there.
Click to expand...
Click to collapse
About 4 hours later and still not showing. Maybe the upload was interrupted.
Can't wait to try it.:good:

My internet failed, I will upload it now.

Everest uploaded.
I think it will work, but I am not 100% since I do not have an everest xoom.
Please try it, tell me if it works so I can put it on the main post.

I am going to test Everest. But I have a problem:
In the BigPart Repartition thread they say the following:
Put all needed resources on your microsd card! You will need the original TWRP 2.6.3.0 touch recovery from @runandhide05, TWRP 2.6.3.0 BigPart version, your desired rom, and the BigPart boot image that goes with your desired rom. The BigPart boot images can be found in the next section.
Click to expand...
Click to collapse
So what versions of TWRP do I put on the SD card? The one from the beginning of the thread is BigPart version?

It is the Schischu TWRP 3.0.1 recovery with added sd card support. I always do
Fastboot flash recovery recovery.img
If recovery.img is the name of the recovery image.
I cannot guarantee it works.