[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

Rohit99 · Dec 10, 2016

This is a test build I take no responsibility for what this may or may not do to your device.

NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .

1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot

]Not Booting

Code:

[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha

Thank you
@faust93 for cwm

XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad

Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod

Version Information
Status: Testing

Created 2016-12-10
Last Updated 2016-12-13

Rohit99 · Dec 10, 2016

Reserved

Sudeep Duhoon · Dec 10, 2016

Edit 1:initial build didn't boot for me, no adb can't get log

OoSTARTERoO · Dec 10, 2016

Ok im gonna try it.
If you want, i can leave logcat for you

Sudeep Duhoon · Dec 10, 2016

OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you

Can get logcat? Try please.

Nihhaar · Dec 10, 2016

Ofc, it doesn't boot. And don't create threads without testing.

OoSTARTERoO · Dec 10, 2016

Sudeep Duhoon said:
Can get logcat? Try please.

unfortunately....I couldn't get logcat too...

Nihhaar · Dec 10, 2016

Sudeep Duhoon said:
Can get logcat? Try please.

we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.

Sudeep Duhoon · Dec 10, 2016

Nihhaar said:
Ofc, it doesn't boot.

As I thought

Rohit99 · Dec 10, 2016

Prebuilt kernel from cm11

Sudeep Duhoon said:
As I thought

hey can i use prebuilt kernel from cm11 source @Nihhaar

Nihhaar · Dec 10, 2016

Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar

Always try to build kernel with source. I think you can't, but you can try.

vickdu31 · Dec 10, 2016

Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha

Harrynowl · Dec 10, 2016

You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits

Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.

We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.

highwaystar_ru · Dec 12, 2016

What kernel repo is upstream one for tegra android? Like CAF for quallcom.

I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?

Cyanogenmod's shield kernel?

Harrynowl · Dec 12, 2016

highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.

I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?

Cyanogenmod's shield kernel?

git://nv-tegra.nvidia.com/linux-3.10.git

I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.

Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

highwaystar_ru · Dec 12, 2016

Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git

I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.

Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.

What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

Harrynowl · Dec 12, 2016

highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.

What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)

Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet

drakonizer · Dec 12, 2016

My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.

Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.

EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

Harrynowl · Dec 12, 2016

drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.

Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.

EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.

They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

drakonizer · Dec 13, 2016

Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.

They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.

[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Forum Moderator

Senior Member

Retired Forum Moderator

Similar threads

Top Liked Posts