There are no official CM12.1 and PAC ROM 5.1.1 builds for TF700T. Cyanogenmod is a ROM loved by many people. In addition to the features of Cyanogenmod, PAC ROM also cherry-picked good features of some other ROMs, like OmniSwitch and Pie Control. More importantly, Cyanogenmod may be the only ROM that applies security updates even to their old branches.
It turned out that it's not very difficult to build fully functional CM12.1 and PAC ROM 5.1.1 for TF700T from source. Just several extra steps in addition to the official guides.
Here is how I did it.
Official guides:
How To Build CyanogenMod For Asus Transformer Pad Infinity ("tf700t")
How to prepare and build PAC-ROM in Ubuntu 14.04 or higher
How to Compile PAC Rom and Port
Additional steps for both CM12.1 and PAC ROM 5.1.1:
After 'repo init ...', before 'repo sync', Put the attached 'roomservice.xml' in '.repo/local_manifests/' directory in the folder where you downloaded the source code. This will ensure device tree and kernel source will be downloaded from VanirAOSP and CyanogenMod during 'repo sync'.
I used 'repo sync -f --force-sync' instead of 'repo sync', so that it won't abort due to errors.
Download Vanir 5.1.1 for TF700T. You can either install it and follow the instructions to extract the proprietary blobs, or just extract the contents of the '/system/' directory of the zip file to '/vendor/asus/tf700t/' directory in the folder where you downloaded the source code.
Additional steps PAC ROM 5.1.1:
Follow this guide to prepare additional files. The ones I used are attached. Mostly, they are from PAC ROM 4.4.4 branch.
Extract the proprietary blobs as stated above, before execute './build-pac.sh tf700t'.
The whole process takes several hours.
With F2FS /data, they are quite smooth, as good as, if not better than ZOMBi-POP.
The only problem I noticed is that Blue-tooth is not working with CM kernel, but it's not a problem when using with _that kernel. You have to use ramdisk of CM12.1 though. If you are going to install the ROM to internal storage, then you have to follow these steps to make a boot.blob with that kernel and CM ramdisk then flash it through fastboot.
Maybe it's better to do ROM2SD installation if you run a ROM internally with that kernel. Just follow the instructions of @_that. Flash rom2sd1.zip, then the ROM, SuperSU, OpenGapps Arm Nano 5.1, then rom2sd2.zip. Attached are the ones I used. I added several files from ZOMBi-POP, and also several lines to ensure '/system' is mounted.
This method also works for other ROMs without ROM2SD support, like OmniROM, Vanir, KatKiss, etc.
Sometimes, I got error with this method. Then I just replaced '0p1' in '/META-INF/com/google/android/updater-script' with '1p3' and flash the ROM before rom2sd1.zip. The rest is the same.
Please feel free to ask any questions.
It seems that these two ROMs run better with internal installation and ext4 /data.
Until someone with the knowledge is willing to tweak the ROM for TF700T, L SPEED can make it run faster. Some people might also be interested in Extreme battery life.
I've seen one tutorial on developing custom rom from source. To do that device specific files like kernel, device tree and vendor blobs are needed. I have following problems regarding those files.
* Kernel - I have zip file of kernel downloaded from my device manufacturer site. How can i make use of that to build a rom?
* device tree - I'm not able to find a device tree for my device anywhere (github or anywhere), how can I build device tree using (kernel/stockrom...)
I'm totally new for this so I don't know if it is even possible or not. Or Is there any other way to create device tree.
* vendor blobs - I've same problem for vendor blobs as in device tree.
~ so from where and how I can extract or create device tree and vendor?
~ and make things ready to develop a custom rom
My device is HTC one (m8 eye)
code name : melsuhl
Hi,
I have successfully build Lineageos .
Vendor tree kernel from exynos7850 source github
.
Problem is someone already pushed vendor and he build lineage. But some features are not working.
While I didn't sync repo last 1day. I have made changes in my local directory and got that build with minimum bug . Now I want to push the vendor. I an noob so please elaborate this git things
Twrp 3.3.1 built from Omni 9.0 minimal manifest.
bootable/recovery folder has several patches merged in , intended to assist in proper /data decryption.
Build tree used was forked from Armor 6 tree, some changes made to mk files and tree source to match the 6E.
Data decryption not working, same as with the version from armor 6.
GitHub build tree. HERE
GitHub device dump HERE
Android File host folder HERE
.
I did not keep this phone. So I will not be making any updates to this twrp.
I'm trying since many time to get a Lineage os build for my device, which is a Samsung A20s |SM-A207F| (codename: a20s) with OneUI 3 (android R) but i'm limited for the following reasons:
There are no device tree to work with.
No vendor blobs to work with
How I get device tree and vendor blob using stock rom or from any other methods