[ROM][CM11][UNOFFICIAL] Cyanogenmod 11 for the Nexus 10 [11/8/2013]

Search This thread
By:
Advanced…
sorcio46

sorcio46

Senior Member
May 6, 2011
234
121
Rome
holtr94 said:
To compile my build I had to merge CyanogenMod's 10.2 branch of android_device_samsung_manta with the 4.4 AOSP version. I put it in my github repo under the cm-11.0 branch. Google has not released the kernel or binaries for 4.4 yet so I used the cm-10.2 branch for those.

You can use this line in roomservice:
Code: 
<project name="rob356/android_device_samsung_manta" path="device/samsung/manta" remote="github" revision="cm-11.0"/>

Once someone puts up the Google 4.4 build I can pull the binaries off it and update the build. That should fix videos.
Click to expand...
Click to collapse
Build succeeded :D, thanks mate, now I have to figure out what changes to do when the binaries will come.
https://lh4.googleusercontent.com/-...84-h865-no/Screenshot_2013-11-13-21-49-55.png
 
Last edited:
Leoisright

Leoisright

Inactive Recognized Developer
Dec 22, 2010
4,857
6,948
MN
It's will break root but super easy to reroot. I would hold tight on the props. Cm will update their bit with the correct files. Will make much easier to resync their bit.

4.4 is extremely similar to these builds from also, cm, and slimkat. Hang tight the updates are coming.

For those that don't want to wait, you can use the toolkit to get back to stock unroot, adb side load the update then just really. Not that bad of a process. I did it mainly to clean my system back to out of box.

Sent from my Nexus 10 using XDA Premium HD app
 
  • Like
Reactions: b1g.p0ppa
Leoisright

Leoisright

Inactive Recognized Developer
Dec 22, 2010
4,857
6,948
MN
sorcio46 said:
Nexus 10 "manta" Android 4.4 (KRT16O) Binaries are out now - https://developers.google.com/android/nexus/drivers
How can I use it to update my CM11 unofficial ROM?

EDIT: http://review.cyanogenmod.org/#/c/53822/
Click to expand...
Click to collapse

the commit posted is just a fingerprint change. Nothing much there. But you need to extract the .sh binary files and place them in the vendor files. Keep in mind there is a kernel change too according to android.googlesource.com . I added the new binaries and couldn't get past the google splash screen which led me to believe there may be a kernel change to reflect the new binaries. Sure enough, they had a change posted. We are now going to be at 4.4 r1.1 which before was 4.4 r1

edit. I've just extracted the vendor files. Place the 3 .sh files in the root of your build environment, then ./nameoffile.sh to extract. you will need to agree to the license before they will extract. I believe it was after 8 d then hit enter, then I ACCEPT and you're home free. Don't go too fast, if you go past the agreement you will have to start over. A real pain in the butt.
 
Last edited:
  • Like
Reactions: shockem and sorcio46
sorcio46

sorcio46

Senior Member
May 6, 2011
234
121
Rome
Leoisright said:
the commit posted is just a fingerprint change. Nothing much there. But you need to extract the .sh binary files and place them in the vendor files. Keep in mind there is a kernel change too according to android.googlesource.com . I added the new binaries and couldn't get past the google splash screen which led me to believe there may be a kernel change to reflect the new binaries. Sure enough, they had a change posted. We are now going to be at 4.4 r1.1 which before was 4.4 r1

edit. I've just extracted the vendor files. Place the 3 .sh files in the root of your build environment, then ./nameoffile.sh to extract. you will need to agree to the license before they will extract. I believe it was after 8 d then hit enter, then I ACCEPT and you're home free. Don't go too fast, if you go past the agreement you will have to start over. A real pain in the butt.
Click to expand...
Click to collapse
Same here, I tried to compile and boot, but it doesn't seem to go far from the Google logo screen.
 
sorcio46

sorcio46

Senior Member
May 6, 2011
234
121
Rome
Leoisright said:
Did you extract the binaries and change out the new kernel?

Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse

Correctly extracted the new binaries following your procedure but I don't know if I did the change to the new kernel with a simple
Code: 
$ repo sync

Should I have to change something in "roomservice.xml" and "local_manifest.xml"

Here you find mines:
[roomservice.xml]
Code: 
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_device_lge_mako" path="device/lge/mako" remote="github" />
  <project name="CyanogenMod/android_kernel_google_msm" path="kernel/google/msm" remote="github" />

  <project name="CyanogenMod/android_device_samsung_manta" path="device/samsung/manta" remote="github" revision="cm-11.0" />
  <project name="CyanogenMod/android_kernel_samsung_manta" path="kernel/samsung/manta" remote="github" revision="cm-11.0" />

  <project name="CyanogenMod/android_device_asus_grouper" path="device/asus/grouper" remote="github" revision="cm-11.0" />
  <project name="CyanogenMod/android_kernel_asus_grouper" path="kernel/asus/grouper" remote="github" revision="cm-11.0" />
</manifest>
[local_manifest.xml]
Code: 
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-11.0"/>
  <project name="TheMuppets/proprietary_vendor_asus.git" path="vendor/asus" remote="github" revision="cm-10.2"/>
</manifest>
 
Leoisright

Leoisright

Inactive Recognized Developer
Dec 22, 2010
4,857
6,948
MN
OK, got full booter from pure also now. Was definetly the kernel. Grab those props and kernel and you will be golden
 
Leoisright

Leoisright

Inactive Recognized Developer
Dec 22, 2010
4,857
6,948
MN
Since you are syncing with CM you will have to wait for them to merge the new kernel. Or you can download my rom in the other forum and pull the boot.img and replace but I wouldn't suggest that.

You could sync with google like I did and get the kernel that way, then just replace it in device/Samsung/manta
 
Last edited:
  • Like
Reactions: zequav and sorcio46
E

enico64

Senior Member
Oct 18, 2010
86
22
Aosp browser is very strange : blank pages and a sort of vibrating scroling. Dont have the right world in english but weird...
 
R

renegade7879

Member
Apr 21, 2013
49
4
The new build from 11/14 works great. I haven't run into any problems yet during normal use. Installed flawlessly with TWRP 2.6.3.1, which was just added to the TWRP thread.

Sent from my Nexus 10 using XDA Premium HD app
 
G

groovinroovin

Senior Member
Nov 2, 2010
68
2
Is this Cm version already coming with fullscreen mode and pie navigation?

Gesendet von meinem Nexus 4 mit Tapatalk
 
You must log in or register to reply here.

Similar threads

ktoonsez
[KERNEL][Nexus 10][04/06/2014][4.4/4.3/4.2] KTManta
Replies
5K
Views
648K
M
marce002
J
[ROM - AOSPA - 4.2.2] PARANOIDANDROID 3.68 (HALO) [Nexus 10] 19-JUL-2013
Replies
1K
Views
315K
alteredlikeness
alteredlikeness
scanno
[ROM] [OmniROM for Nexus 10 ] [Android N]
Replies
1K
Views
263K
Azukegi
Azukegi
mskip
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 10 - Drivers, Root, Recovery + MORE
Replies
618
Views
381K
D
dkrte
DariosF
  • Locked
[ROM] [GPL] [KK 4.4.4] ♦ PURITY ROM ♦ (Manta) 17/10
Replies
825
Views
157K
Woody
Woody

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 17
    H
    holtr94
    NOTE: This is pre-nightly status. It is very likely things will go wrong. Use at your own risk. I am not responsible for damage to your device.

    Everything should be working now.
    If you find any issues let me know.

    NOTE: You must flash from CWM. TWRP has issues flashing 4.4 roms currently.

    Download:
    http://d-h.st/hbr

    GApps:
    Use PA-GApps: https://plus.google.com/107979589566958860409/posts/6eZrEBD3H99
    Direct Link: http://goo.gl/6tPVe

    My Github Repo

    Changes:
    • (11/8/2013) - Enabled transparant nav/status bar in the launcher. Despite what Google claims it works fine.
    • (11/14/2013) - Fixed video playback. Now using 4.4 binaries.

    REMEMBER: FLASH AT YOUR OWN RISK
    View
    6
    H
    holtr94
    Hey Guys,

    I just uploaded a new build with the new binaries which fixes videos: http://d-h.st/hbr
    Let me know if you see any more problems now.

    Because Google hasn't posted the 4.4 kernel source I have to use the kernel built by Google (as Leoisright said earlier) for now.
    View
    5
    W
    wtgserpant
    I compiled CM 11 for myself

    So I have compiled CM11 and here it is :

    Everything works, but the kernel from the CM repo does not boot. I recommend flashing the Der Kernel as it worked perfectly for me.

    I will look into the kernel issue later; I will be trying to share my builds every few days,

    I did some testing and everything seems to work, except the kernel!

    Downloads:
    CM 11: https://mega.co.nz/#!t4QW1T4Y!TldGuxGb8ZHVaVUmQJm0wDB26TNo9kwqhAuG7C5RA2w
    Kernel: http://goo.gl/yst6NC
    Gapps: http://www.mediafire.com/download/76dawa7slqi3aju/pa_gapps-full-4.4-20131126-signed.zip.md5


    DEFAULT KERNEL DOES NOT WORK, try Der kernel or other ones for now.

    Thanks to the CM team and morfic for everyhting
    View
    3
    hanspampel
    hanspampel
    I made one for first Snapshot.
    View
    2
    H
    holtr94
    To compile my build I had to merge CyanogenMod's 10.2 branch of android_device_samsung_manta with the 4.4 AOSP version. I put it in my github repo under the cm-11.0 branch. Google has not released the kernel or binaries for 4.4 yet so I used the cm-10.2 branch for those.

    You can use this line in roomservice:
    Code: 
    <project name="rob356/android_device_samsung_manta" path="device/samsung/manta" remote="github" revision="cm-11.0"/>

    Once someone puts up the Google 4.4 build I can pull the binaries off it and update the build. That should fix videos.
    View

New posts