[ROM][AOSP][7.1/8.1 EXP][K3.4][Repartition] Unlegacy Android Project - Asus Eee Pad Transformer Prime

The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T​
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- Touchscreen failure (sometimes occurs, if touch works after reboot it will work till next reboot);
- Camera (both);
- Dock special keys (top row);
- GUI crashes; - occure less often
Currently, I'm only one from Unlegacy Team, who has TF device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Latest information about OREO builds can be found HERE.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Eee Pad Transformer Prime
Contributors
Clamor, Ziyan, Narkolai
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17

Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.

REPARTITION and TREBLE
TF201 users know well what is repartition. While flashing 4.2BL from HB internal storage is reformatted. This thing is exactly the same.
I worked on it for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY!
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash HB bootloader or Bootloader 4.2 attached in Downloads section.

Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?

MalibuKoKo said:
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
Click to expand...
Click to collapse
Actually you can't build fully working ROM from my source for now. If you would like to help in developing - PM me.

Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.

goosebickel said:
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
Click to expand...
Click to collapse
Based on latest 4.2 bootloader (like Hairybean). I'll provide a bootloader + new TWRP and separate TWRP as soon as I get a stable recovery build.

General Feedback
Finally got around to flashing your ROM a week ago, following your instructions, everything went fine. I installed your UA-bootloader and flashed _that16 kernel.
Running pretty smooth with Pico gapps installed, after a week, the usual happens, slow loading apps etc, but that is not the ROMs fault, the very slow memory that Asus put into it and Google is slowing it down with constant syncs etc.
Was wondering if you had added compatibility for using MicroG?
Thanks for keeping this old tablet going.

@goosebickel sorry for such a long silence. MicroG are supported as I can say (I installed them but didn't test much).
P.S. If you are still on UA rom there is an update.

Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs from O for now. I know already about all major issues.

Thank you!
Great to see some development for the Transformer Prime

I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash

Clamor said:
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Click to expand...
Click to collapse
Are you planning to work on Pie as well once 8.1 is somewhat stable?

shinzz said:
Are you planning to work on Pie as well once 8.1 is somewhat stable?
Click to expand...
Click to collapse
I'm planing to bring up P as well. If O works, P should work as well.

Can the ROM be installed by using the latest KANG TWRP 3.2.3 or do I need to use the TWRP found in the download section?

@shinzz TWRP from download section

any update?

shinzz said:
any update?
Click to expand...
Click to collapse
Noticed the link to the ROM is 404'ed also. - NP

latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP

Clamor said:
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Click to expand...
Click to collapse
My 201 is on KANG's - TWRP 3.2.1-0 and KatKiss, if this ROM just a simple wipe and flash with KANG's - TWRP 3.2.1-0 and the Harry Bean bootloader on my 201 or will I need a different recovery console, bootloader ext. ext? - NP

Related

[ROM][Bacon][5.0.1]Vanir AOSP - AK - F2FS - multirom

Hi all,
this is a modified version of team Vanir's latest AOSP rom for bacon and the latest AK kernel but uses an f2fs file system.
To install it:
1. format system, cache and data, data/media to F2FS. Philz recovery is best for this.
2. wipe for a new rom.
3. Install this.
4. Install gapps Build by DHO for Vanir
5. Install SuperSU latest (I am currently using BETA-SuperSU-v2.38.zip with no problems)
6. Boot
Enjoy.
Currently this rom will only flash as a primary rom on Multirom. TWRP and Philz are also good. I hope to have a version that will flash directly as a secondary on multirom shortly but once installed, this rom can be migrated as a secondary rom, and can be swapped between primary and secondary.
If you get an error when you first install this, it means that you need to wipe the cache, and dalvik. Re-flash and all should be fine.
Changes to AK kernel can be dirty flashed onto this rom once installed,so I wont be releasing a new version with each AK kernel release, but will try to keep in sync with future Vanir lollipop releases with a f2fs flashable version. Nightly builds should be with us soon.
Thanks to AK, Team Vanir, and Martin_Ro for their excellent work. I take no credit for the rom, I just produced a f2fs friendly package with the AK kernel embedded.
See the official Vanir Google+ community for news/updates. Full details of the ext4 version of the rom can be found in Martin_Ro's thread, here.
I prefer to run my oneplus one with a f2fs file system and multirom, which means that many of the roms available have to be converted before I can use them. I have to convert the rom to be f2fs friendly. Its good to share, and save others the chore of doing this conversion.
Please note. The flash, and first boot take a little time, so be patient please.
Good job. Is there significant change in performance from ext4? and does the headsup notifications work for all the apps?
Much alohas
antisocialbratt said:
Good job. Is there significant change in performance from ext4? and does the headsup notifications work for all the apps?
Click to expand...
Click to collapse
It does depend on the specific rom. However I do generally find that it runs a little smoother, and battery seems a little better and antutu scores a little better (whatever that means). I havnt really had much time to perform any objective tests, and anyhow it would probably be best with two oneplus ones to do that, but it seems better.
- more info here
http://www.cnx-software.com/2013/01/...ces-elce-2012/
http://www.xda-developers.com/androi...-against-ext4/
The functionality should be exactly the same as the original, so the headsup notifications are the same as the original released software.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Nice to see that you convert more Roms. So i soon will change back to F2FS. I dont have much success to convert the Rom i like to test

[ROM][AOSP][WIP][ALPHA][M] Android M Alpha \\ 25-6-15 \\ Build I

Introduction:​So I see you have found my Android M Preview ROM thread. So... You all might of seen this. It's Sony announcing that it's AOSP open line of Xperia devices can now build Android M and is showing devs how to build it. Apparently things aren't exactly that way. Google created under it's source code, an alpha branch for the upcoming Android M, what that branch contains is mostly Android Lollipop code and some Android M stuff. This branch will evolve to become Android M, but at it's current state, the ROM is in between Android lollipop and M (kind of a weird mix of a sort that's why the build number is 5.1.51 and the easter egg is the one of lollipop). I will however provide weekly (hopefully) builds of Android M as it becomes more M than L. Keep in mind that the current release of the ROM (as of 25-6-2015) does not contain the new API's (for devs that are interested). You can see Sony's official explanation here. If you are still interested though in checking out the current state of Android M be my guest though keep in mind that in it's current state it is FAR from a daily driver (modem and camera are the most major of bugs currently) and most if not all of the cool features on Android M developer preview for the Nexus line probably are not currently included (as on 25-6-15).​
Warning
This works only on UNLOCKED BOOTLOADERS. Keep in mind that the ROM was built for the D6603 I don't know if it will work with any other variant of the Z3. In addition flashing this might erase recovery on some devices. Also I take no responsibility of whatever may happen by using this ROM.
Downloads (please read the Introduction if you haven't, its important )​Kernel
System
Userdata​
Installation:​1. Backup EVERYTHING (Your SD card included. This ROM has proven to be unpredictable as of storage on some handsets).
2. Download the Kernel, System and Userdata images
3. Get yourself a working ADB/Fastboot installation (more on that on the kernel page)
4. Flash the kernel as described on it's page (Steps 1-7)
5. While still in fastboot mode enter these commands in the command prompt:
Code:
fastboot flash system (directory of system image)
fastboot flash userdata (direcotry of userdata image)
6. Reboot your device and wait for it to start up​
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
Erases all storage (internal and external) on some handsets
Screenshots:
Here you go. ​
Credits:​
The rest of team Pear Crew
akateha
My Family & Friends
Sony and it's AOSP project
XDA
Google​
Changelog:
----- Build I -----
Initial release.
Synced the latest android-m-preview branch
Most Android M features completely missing, ROM is like a hybrid of Lollipop&M
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
I can't believe what you just posted
Hahaha @Griffiths_Anna why so?
@CedArctic
it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
@Gustavo RD78
Actually I haven't, even Sony states that Camera & Modem are guaranteed broken. Even if the modem was fixed (which I believe it will in the next few weeks) the ROM still needs a lot of work for all the other bugs. Although about the baseband, I think M requires a special version of the baseband because even when you flash the official M preview over the Nexus 5, you have to flash a new baseband that is compatible with Android M. I am currently away from my Z3 but if someone tries it out and confirms it working I would gladly add it to the main thread.
Wow, that was fast, need i say more??
@corpsegrinder62 Actually, considering the announcement date it is fast. I dualbooted my PC with linux just 36 hours ago, downloaded the sources and compiled... XD
Gustavo RD78 said:
@CedArctic
it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
Click to expand...
Click to collapse
Some modem components are stored on /system and not included for legal reasons in Sony's AOSP binary releases. https://github.com/SuperBenevolent/aosp-vendor-qcom-proprietary
At least with L-MR1, the ONLY things missing for modem to work are the blobs above. Dunno about M, I'm not bothering to mess with it until official M release.
Woaw, nice to see android m being worked on even though it's in its early stages.
Is that my build you are running?
Installed a few minutes ago. Thank you for compiling the source code.
Am I wrong or can´t I flash GApps?
Edit: Also I cannot use any storage. Not internal and not sd card
@Silveryard Yeah there are like lots of bugs... I hope some will be solved in the future. Storage is definetely one of them. I never tried to flash gapps though
It´s because some .apk files (like the play framework) cannot be installed with adb install command and require a custom recovery kernel or root or root for writing permissions in "system"
I don´t know much about compiling a system image but is it possible to place the gapps files into the right folder right before compiling everything in one file? This would help much and would make this preview much more usable in daily life.
Thank you! I'll be trying this on my D6653.
Made an installation video.
How To: Flash Android M Alpha for Xperia Z3: https://youtu.be/rJgYnqv3ZPM
Good news
CedArctic said:
@Silveryard Yeah there are like lots of bugs... I hope some will be solved in the future. Storage is definetely one of them. I never tried to flash gapps though
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...v-android-m-apps-framework-deodexing-t3166000
@squabbi Cool bro @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide
CedArctic said:
@squabbi Cool bro @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide
Click to expand...
Click to collapse
What? I'm not sure what your talking about
Just to repeat, those are the actual M preview apps and I "fixed" them so that you can add them to your rom
@Aaahh you posted a quote of me about storage and I said now that I think I know that the issue is in the storage-list.xml in the framework. I will include your apps in the next build, but for now I am focusing on a different project until M becomes more stable...

[ROM][UNOFFICIAL][6.0.1][SGP712/SGP771] CyanogenMod 13 for Xperia Z4 Tablet [Alpha]

CyanogenMod 13 for Sony Xperia Z4 Tablet Wifi and LTE (SGP712/SGP771)​
Code:
Your warranty may be voided ! I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications.
Issues:
- Back camera focus: image is blurred and color problem (waiting for new AOSP blobs from Sony)
- Minor bug with led while charging
- No FM radio
- Tell me what you find !
How to install
- Unlock your bootloader (you can save your TA partition before)
- Update your firmware to the last Marshmallow version (needed to update the bootloader, kernel will not boot if you use the Lollipop bootloader)
- Install AndroPlus kernel and TWRP
- Make a backup
- Push the rom’s zip to the SD card (optionnaly with gapps)
- Wipe System, Data, Cache, Dalvik cache
- Install the rom (and gapps if you want)
- Reboot
- Enjoy, and give me a feedback
Advice: You can use TWRP from Androplus before installing the rom. But it will not work with cyanogenmod kernel.
So, after installing the rom, you can use TWRP made for CM kernel (see the link bellow) and press vol+ at boot, or keep AndroPlus TWRP and use "fastboot boot boot.img", were boot.img is AndroPlus kernel.
Edit : my TWRP for CM seem to has a bug with touchscreem randomly not working, you can reboot the tablet with Power-Vol+ until the touchscreen works (it doesn't stop working after boot, it just works well or not at all), or use the fastboot method with AndroPlus Kernel.
I will solve this problem when I'll have the time.
Thanks
@CTXz and @zacharias.maladroit for all the work with the Z5 serie and the kitakami platform
To all people who helped them: @oshmoun, @moonbutt74, @sub77, @Joeisgood99, @bazhip, @alphatact1cs, @auras76, @Myself5
@AndroPlus for his great kernel and recovery
Sony’s AOSP team for providing sources for AOSP
CyanogenMod team, they are provinding a great android distribution
Google for Android
All the people I don’t explicitly thanks (You can ask if you think you should be on this list, I will add you with pleasure)
Downloads
Cyanogenmod unofficial rom for karin windy (Z4 tablet wifi only)
https://www.androidfilehost.com/?w=files&flid=67714
Cyanogenmod unofficial rom for karin (Z4 tablet LTE)
https://www.androidfilehost.com/?w=files&flid=86526
Gapps
http://opengapps.org/
Select ARM64, android 6,0, and choose the variant you want (I recommand pico)
TWRP for CM kernel (both Z4 tablet wifi and LTE)
https://www.androidfilehost.com/?w=files&flid=114592
Questions
- Please, avoid asking things like: how to flash this rom, what is fastboot, …
There is enough documentation on XDA and others websites. You also probably should not use this rom if you don’t know how to recover a bricked device with fastboot and flashtool.
- I’m not a professional devlopper, I don’t receive payement for this, so don’t ask for ETA, for make a rom for an other devices, …
- I only have a wifi only Z4 tablet, I make a LTE version, but since I don’t own this tablet it’s not possible for me to debug like on my wifi tablet.
Reporting a bug
- Explain what happen with the more details you can: how does this bug happen, when, …
- Share a log if you can
Source code:
Device
https://github.com/andralex8/android_device_sony_karin_windy
https://github.com/andralex8/android_device_sony_karin
https://github.com/andralex8/android_device_sony_kitakami
https://github.com/andralex8/android_device_sony_common
Kernel
https://github.com/andralex8/android_kernel_sony_kitakami
Vendor
https://github.com/andralex8/android_vendor_sony
https://github.com/andralex8/android_vendor_qcom
The remaining source code for the kitakami platform can be obtainde from here:
https://github.com/Sony-Kitakami
https://github.com/andralex8
CyanogenMod source code:
https://github.com/CyanogenMod
TWRP source code:
https://github.com/omnirom/android_bootable_recovery
Changelog
Code:
2016/11/25
- Increase max speaker volume
- Allow to set lower minimum brightness
- Sync last CyanogenMod sources (stable/cm-13.0-ZNH0E branch)
2016/11/13
- Sync last CyanogenMod sources (stable/cm-13.0-ZNH0E branch)
2016/09/18
(- Use cm libbt again)
2016/09/17
- Sync last CyanogenMod sources (stable/cm-13.0-ZNH0E branch)
2016/08/21
- Fix USB OTG (disable switch on boot)
2016/08/20
- Sync last CyanogenMod sources (stable/cm-13.0-ZNH0E branch)
2016/08/07
- Partially fix USB OTG (fix kernel usb driver)
- Use Adreno stock blobs (32.1.A.1.185)
- Sync last CyanogenMod sources (stable/cm-13.0-ZNH0E branch)
2016/07/29
- CyanogenMod for SGP771 karin released
2016/07/10
- Update qcom blobs (SW_binaries_for_Xperia_AOSP_M_v05a)
- Cpuquiet and rqbalance improvements (cherry-picking from sonyxperiadev)
- Sync last CyanogenMod source (stable/cm-13.0-ZNH0E branch)
2016/06/15
- Fix sensors
2016/06/14
- Fix bluetooth (use broadcom libbt from AOSP instead of CM)
2016/06/05
- Fix audio (add acdb and audio config from stock 32.1.A.1.185)
- Sync last CyanogenMod sources (stable/cm-13.0-ZNH0E branch)
2016/05/29
- CyanogenMod for SGP712 karin_windy released
- Use cm stable/cm-13.0-ZNH0E branch
XDA:DevDB Information
CyanogenMod 13 for Xperia Z4 Tablet, ROM for the Sony Xperia Z4 Tablet
Contributors
andralex8, and a lot more (see thanks section)
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-07-23
Last Updated 2016-11-25
File is uploading, should be online in a few minutes
Edit : link temporary changed to google drive, I have problems to upload to androidfilehost. The link should work now
Well done! Many thanks for getting this ROM started and sharing it.
Sent from my SGP712 using XDA-Developers mobile app
Good to know that at last cyanogenmod was released for our tablet, hope it will be the same for SGP771 soon.
Audio fixed, now the tablet should have sound working properly
Great work! Hanging on for recovery code to be integrated after some foibles with fastboot on the sgp612.
Sent from my A0001 using XDA-Developers mobile app
belrik said:
Great work! Hanging on for recovery code to be integrated after some foibles with fastboot on the sgp612.
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you!
In fact the current kernel/ramdisk can launch a recovery by pressing the vol+ when the led turn pink, but it cannot load the currently available TWRP recovery that need Androplus kernel.
I'm currently making a recovery that work with this kernel (it seem that it work with Androplus kernel too). It actually kinda work, it can wipe system and flash Cyanogenmod (not trying backup and restore yet). But the updater crash when trying to install Gapps, I need to fix this and it should be ok .
Awesome work, thanks! It's running pretty smooth. No problem booting TWRP manually from fastboot. Good luck hammering out the small things
TWRP is now working with the rom ! And without the need of the fastboot trick .
It's build to work with the kernel I used for cyanogenmod. (It work partialy with Androplus kernel too but with some limitations like adb is not working, ...)
This is the link: https://www.androidfilehost.com/?w=files&flid=67717
I forgot, but touchscreen may not work at first TWRP's boot. Just reboot the recovery and it should work again.
Recovery works great, no touchscreen issues after flashing it. :good:
andralex8 said:
- I only have a wifi only Z4 tablet, I could make a LTE version if nobody else make it, but since I don’t own this tablet it’s not possible for me to debug…
Click to expand...
Click to collapse
I would be willing to test an SGP771 version, if you can compile one?
Also, are the install instructions still correct?
andralex8 said:
How to install
- Unlock your bootloader (you can save your TA partition before)
- Update your firmware to the last Marshmallow version (needed to update the bootloader, kernel will not boot if you use the Lollipop bootloader)
- Install AndroPlus kernel and TWRP
- Make a backup
- Push the rom’s zip on the SD card (optionnaly with gapps)
- Wipe System, Data, Cache, Dalvik cache
- Install the rom (and gapps if you want)
- Reboot
- Enjoy, and report bugs
Click to expand...
Click to collapse
Should it not be the TWRP version you have built that should be used, as opposed to the AndroPlus version?
HotBlack77 said:
I would be willing to test an SGP771 version, if you can compile one?
Click to expand...
Click to collapse
I will check this week-end if I have the time . But I must make a cm device repo from Sony's AOSP repo before being able to compile anything. So I don't promise anything, I will see.
HotBlack77 said:
Also, are the install instructions still correct?
Should it not be the TWRP version you have built that should be used, as opposed to the AndroPlus version?
Click to expand...
Click to collapse
You first need to have a working recovery to flash CyanogenMod. And for the Z4 tablet (and almost all Xperia), the recovery use the same kernel as the system because the recovery is not lauched by the bootloader, but after, by using the FOTAKernel partition as a recovery partition.
It's the reason for what when coming from stock I advise to use Androplus kernel and TWRP. After flashing CyanogenMod, the kernel is cm's one, then TWRP from Androplus will not work and you will need to switch for TWRP for cm kernel.
You can try to use TWRP for cm kernel with Androplus kernel. I tried and it seem to work, but since it's not compiled with this kernel it may not work properly. I didn't make an extensive testing for this configuration (Androplus kernel + cm TWRP), so I can't advise people to use it but maybe it's not a problem.
Bluetooth should be fixed, the annoying bug with the keyboard is gone .
Using broadcom libbt from AOSP seem to fix the problem (thanks again to Sony Kitakami Platform Developer Organization)
Sensors fixed !
Now automatic rotation work (and other sensors too).
Is sgp771 going to be supported?
Enviado de meu SM-N920G usando Tapatalk
calj17 said:
Is sgp771 going to be supported?
Click to expand...
Click to collapse
This is what I already said a few post ago:
andralex8 said:
I will check this week-end if I have the time . But I must make a cm device repo from Sony's AOSP repo before being able to compile anything. So I don't promise anything, I will see.
Click to expand...
Click to collapse
So, you will tell me that yourself if it work or not when I'll make a test rom for SGP771 .
I already take a look and it have most of the device tree common with the SPG712, so I think it should not be too difficult to have a working rom for the sgp772 because it's working on the sgp712.
andralex8 said:
This is what I already said a few post ago:
So, you will tell me that yourself if it work or not when I'll make a test rom for SGP771 .
I already take a look and it have most of the device tree common with the SPG712, so I think it should not be too difficult to have a working rom for the sgp772 because it's working on the sgp712.
Click to expand...
Click to collapse
Great to hear that. The only difference is modem blobs between sgp712 and sgp771
Enviado do meu iPad usando Tapatalk
All fresh from this night, this is a rom for the SGP771 (Karin) :
https://www.androidfilehost.com/?fid=24591000424940766
I didn't test this rom because I only have a SGP712. Then, if someone can give me a feedback if the rom install and lauch correctly it would be great .
andralex8 said:
All fresh from this night, this is a rom for the SGP771 (Karin) :
https://www.androidfilehost.com/?fid=24591000424940766
I didn't test this rom because I only have a SGP712. Then, if someone can give me a feedback if the rom install and lauch correctly it would be great .
Click to expand...
Click to collapse
I have the 771 LTE version with recovery installed. I just need to flash the ROM and google apps?
Thanks
Sent from my Nexus 6P using Tapatalk

[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 weekly builds for Asus Zenpad 8.0 Z380K[N]L

Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?

[ROM][UNOFFICIAL][10] Paranoid Android Quartz for Pixel and Pixel XL

We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Device-specific issues
Logcat gets spammed by gralloc errors
Note: Custom kernels are NOT supported! It already comes with LunarKernel.
Downloads
Downloads (from Drive)
TWRP (download 3.4)
GApps already included, don't click on this link
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them.
Paranoid Android Quartz released
Instructions
Reboot to bootloader
Boot into TWRP recovery via fastboot
Code:
fastboot boot twrp-3.4.0-0-marlin.img
Wipe data
Flash the ROM (no need for GApps since they're included)
(Optional) Reboot bootloader, boot TWRP again, and flash any addons you want.
Reboot to the system
Important/Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Help us improve PA by submitting detailed bug reports with logs. Learn how to take logs here.
Send the logs to me, as this is a unofficial build.
Here's the various sources used for this ROM (feel free to fix stuff):
Kernel source (for GPL compliance): https://github.com/Lunarixus/LunarKernel-marlin
The rest (contains locations for all the device-specific sources required to build PA): https://github.com/yagyaxt1034/android_vendor_pa/blob/quartz/products/marlin/pa.dependencies
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android Quartz for Pixel and Pixel XL, ROM for the Google Pixel XL
Contributors
yagyaxt1068, Lunarixus, spezi77, AOSPA team, PixelDust-CAF, Qualcomm Android for MSM, probably a bit of Lineage in there somewhere, you get the idea.
Source Code: https://github.com/yagyaxt1034/android_vendor_pa
ROM OS Version: Android 10
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Latest 10 bootloader and radio
Based On: CAF
Version Information
Status: Testing
Current Beta Version: 5
Beta Release Date: 2020-08-17
Created 2020-08-18
Last Updated 2020-08-27
Thanks for bringing PA to our device. The install went perfectly, but setup kept asking me to insert my SIM card. I have Verizon. I was able to connect to WiFi, but couldn't get it to recognize the mobile network. I did try turning airplane mode on and off, but no luck.
beeewell said:
Thanks for bringing PA to our device. The install went perfectly, but setup kept asking me to insert my SIM card. I have Verizon. I was able to connect to WiFi, but couldn't get it to recognize the mobile network. I did try turning airplane mode on and off, but no luck.
Click to expand...
Click to collapse
Oh sorry, that's my bad. I accidentally forgot to switch to AOSP's RIL, as CAF RIL will not work. I'll fix it and upload a new build soon.
Same here, will wait, thanks for the fix in advance:good:
yagyaxt1068 said:
{Mod edit: Quoted OP shortened for better reading experience!}
Click to expand...
Click to collapse
Usually when I flash other rom I copied the rom zip to internal storage. In twrp I wiped system/data/delvik and flash the rom but here the instructions is different. could you plz elaborate I am newbie
imna357 said:
Same here, will wait, thanks for the fix in advance:good:
Click to expand...
Click to collapse
I've pushed an updated build with fixed RIL. Try it out.
bhaskarjyotisarmah51 said:
Usually when I flash other rom I copied the rom zip to internal storage. In twrp I wiped system/data/delvik and flash the rom but here the instructions is different. could you plz elaborate I am newbie
Click to expand...
Click to collapse
Most ROM instructions usually tell you to wipe /system, but this is not actually necessary on Pixels, since there's an A/B setup, so that's up to you whether you want to wipe system. I usually don't. And a factory reset should wipe both /data and dalvik, so that's not too hard.
The mobile network fix worked !! Good Job.
I'm getting Carrier Provisioning Service force close. I sent you a PM with a link to a logfile and hope you can read it.
A feature I'd love to see in future builds is Volume Steps.
Again, Thanks for your work here.
No bells and whistles but fast and smooth as to be expected
from PARANOID ANDROID brilliant thanks love it ?.
Excited to install again once it becomes stable
Apps take over the screen and I am not able to access screen buttons. I love that it is a CAF ROM.
cranialbug13 said:
Apps take over the screen and I am not able to access screen buttons. I love that it is a CAF ROM.
Click to expand...
Click to collapse
Sounds like a hostage situation intriguing very very intriguing ?.
You gave the wrong zip for sailfish, it's actually marlin.
Hey there!
Can we expect an Android 11 build in the future? That would be amazing! :fingers-crossed:
Help The Peace said:
Hey there!
Can we expect an Android 11 build in the future? That would be amazing! :fingers-crossed:
Click to expand...
Click to collapse
I'll try it once 11 is available for marlin and PA updates to it.
As the description says pixel and pixel xl ..just wanted to be sure if it would actually work in sailfish cause there's no such thread for this rom in sailfish.please reply
shtma said:
As the description says pixel and pixel xl ..just wanted to be sure if it would actually work in sailfish cause there's no such thread for this rom in sailfish.please reply
Click to expand...
Click to collapse
Unfortunately, the sailfish build didn't work right, so it's only on marlin for now. However, I'll come back to building PA on 11.
yagyaxt1068 said:
Unfortunately, the sailfish build didn't work right, so it's only on marlin for now. However, I'll come back to building PA on 11.
Click to expand...
Click to collapse
I see. It would be nice if in the future we're going to see other builds for sailfish/marlin. (official ones would be really awesome)

Categories

Resources