Related
Who are you? Well glad you asked. I am CedArctic founding member of the Pear Crew team on XDA. Our team is dedicated to develop custom software for any Android device that falls into our hands. In the past we flooded the HTC Inspire 4G/Desire HD/X-Arc/Neo/V/Play/Desire S/mT4G/... forums with custom ROMs and other ports and mods. And today we present you with our first build for the Xperia Z3. The Android M Developer Preview Kernel. Compiled for the Xperia Z3, this kernel can bear the weight of the M Dev Preview (thread coming up for that ASAP) we just figured out we should post the kernel separately. If anyone wants to use the kernel for his ROM he can feel free to do so, just message me in advance and give proper credit.
Warning
This kernel is still in ALPHA, as a matter of fact so is Android M. I do not take any responsibility for what may occur by using it. Also this only works for UNLOCKED BOOTLOADERS.
Installation:1. Download the kernel image (see downloads section)
2. Get any kind of fastboot/adb installation (either download android SDK-too much work / or you can download minimal adb and fastboot from XDA)
3. Make sure you have the correct drivers installed for the Xperia Z3
4. Make a full backup of everything
5. Open up the command prompt to your minimal adb installation (or if you have android SDK just open the command prompt)
6. Put your Xperia Z3 into fastboot mode (shut it down, then hold down the volume down button and connect it to the PC via the USB cable
7. Type fastboot flash boot and then drag in your boot.img should look like this: fastboot flash boot (location of boot.img) and then hit enter.
8. The kernel will flash and you can use it with any Android M Dev Preview ROM (mine is currently uploading- keep an eye out for it)
Downloads:Kernel
Credits:The rest of team Pear Crew
akateha
My Family & Friends
Sony and it's AOSP project
XDA
Sources: The kernel is based off the official Xperia Kernel sources for AOSP which can be found here.
Reserved for future changelogs
Mega asks for "decryption key" to dowmload. Can you give the "decryption key".
Oh really sorry for that. First time using MEGA. I'll update the link including the decryption key in a couple of minutes.
CedArctic said:
Oh really sorry for that. First time using MEGA. I'll update the link including the decryption key in a couple of minutes.
Click to expand...
Click to collapse
It is ok. Thanks.
Hi, will this work on Sony's 6.0 concept preview ? Can we flash SU with this kernel (permissive)?
I don't know whether it is compatible with sony's concept... and the kernel is not permissive. So no flashing SuperSu on top of it.
GeyerA said:
Hi, will this work on Sony's 6.0 concept preview ? Can we flash SU with this kernel (permissive)?
Click to expand...
Click to collapse
Use SELinux Mode Changer to change to permissive ...you need to be rooted though
Keep in mind that this was built for Sony's M Preview (which was a weird version of Lollipop and M together), NOT Sony's Concept for Android - Marshmallow...
Today Samsung Released an update that breaks a root method of Trapkernel im not not discussing of creating a kernel but assisting Devs by saving them time to create one so i extracted the boot.img & recovery.img from the Official firmware (No backups were used the files were tooken from the Odin format version of the firmware) their also in the zip as flashable files for odin so their is two different versions
You have 2 of the same files that arent flashable via odin
Boot.img & Recovery.img
And you have the same files as flashable fies for odin:
recovery.img.tar.md5 & boot.img.tar.md5
Yea they work and fully tested using my Galaxy Core Prime SM-G360T1 MPCS
Why do you ask of why i wanted Trap kernel to be updated?
A: see i flashed the trap kernel via Odin and the phone booted just fine no issues but i soonely realized that the Kernel breaks the Wi-Fi feature and thats all it breaks Cell and Other Features work just fine, so im asking devs to use the zip given to create a new root method out of the same root method if possible to root the Galaxy Core Prime SM-G360T1 MPCS and have our wifi fixed!
Now this us so important to me because Samsung just made the phone even faster better and secured with a patch to Quadrooter Vaulnerabilities so here ya you all go devs lets get rootin i will update the thread when new firmwares release!
Download Here: https://www.mediafire.com/download/bjj0i8f0f8zb01q
XDA:DevDB Information
SM-G360T1 G360T1UVS2APK3 Stock Recovery & Kernel For Developers , Kernel for the Samsung Galaxy Core Prime
Contributors
g7755725
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: None
Stable Release Date: 2016-12-23
Created 2016-12-23
Last Updated 2016-12-23
Edit - gave up.
also breaks the pc reconising the phone ahhhhhh like wtf nobody knows the fix..shoul be said on the thread it breaks wifi n pc as causes malfunction so pc dont see the phone.. twrp has file yet now cant revert back to just use twrp as it broke connection so cant flash stock
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* 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, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Installation
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Download the EXPERIMENTAL and NIGHTLY builds using the download link below
Install the EXPERIMENTAL build, without wiping anything.
Reboot into Android
Reboot back into recovery
Install the NIGHTLY build, without wiping anything.
Enjoy LineageOS!
First time LineageOS 14.1 installation on your Galaxy S IV:
Flash a custom recovery via dd, use this recovery: https://androidfilehost.com/?fid=962157660013071010
Push Lineage OS 14.1 Weekly Zip & (optionally) GApps (arm) & (optionally) addonsu (for root) to your device
Boot into Recovery
Perform factory reset
Flash Lineage OS 14.1 zip from SD card
(optionally)Flash GApps from SD card
(optionally)Flash AddonSU from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - https://androidfilehost.com/?fid=962157660013071010
[*]Push the new Lineage OS 14.1 zip to your SD card
[*]Boot into Recovery
[*]Flash the Lineage 14.1 zip from SD card
[*]Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
[*]Reboot
Downloads
Install packages: [URL="https://download.lineageos.org/jfltevzw"]https://download.lineageos.org/jfltevzw
Google Apps (arm): http://wiki.lineageos.org/gapps.html
Root add-on: https://download.lineageos.org/extras
Unofficial TWRP (NEEDED)
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for S4 Verizon, ROM for the Samsung Galaxy S IV S4 Verizon, ROM for the Verizon Samsung Galaxy S4
Contributors
[URL="https://forum.xda-developers.com/member.php?u=5968293"]side, invisiblek, npjohnson
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2017-03-15
Last Updated 2017-11-06
XDA:DevDB Information
[OFFICIAL][WEEKLY][7.1.2] LineageOS 14.1, ROM for the Verizon Samsung Galaxy S4
Contributors
npjohnson
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2017-11-06
Last Updated 2018-09-21
reserved
@side
Thanks for your contribution!
There is a small typo in the first post - the download URL actually points to jfltexx instead of jfltevzw builds.
Got a question, what root are you using in this? AICP switched to a systemless root magisk and couldn't get it working. Is this is still old school root? Systemless root has to patch the boot.IMG and with the bootloader locked it wont work? Correct? Just trying to understand. Thanks
Would like to switch.
Sent from my Nexus 6 with Pixel XL build.prop
side said:
Flash a custom recovery via Heimdall or Odin
Click to expand...
Click to collapse
Which custom recoveries do work on Verizon variant? Everytime I install TWRP is gives me this message: "System software not authorized by Verizon wireless has been found on your phone "
Alternatively, can this be flashed using Flashify?
Z4K101 said:
Which custom recoveries do work on Verizon variant? Everytime I install TWRP is gives me this message: "System software not authorized by Verizon wireless has been found on your phone "
Alternatively, can this be flashed using Flashify?
Click to expand...
Click to collapse
We don't have an unlocked bootloader. If your bootloader version is MDK, however, there is an exploit known as LOKI. The LOKI exploit allows the bootloader to load 'unsigned' software, if said software has been patched to use the LOKI exploit. If your bootloader is NOT MDK, you're SOL. Don't tamper any more or you risk a brick.
(You can check your bootloader version by typing 'getprop|grep bootloader' in a terminal emulator on your device, or using 'adb shell' and then that from a command line on your computer.)
If you download and install TWRP from the TWRP app or site, it will not be LOKI patched. You need to find a patched recovery and flash that. Check the official TWRP thread. There is a gentleman who was kind enough to throw together a little command script that will flash a LOKI signed TWRP to your phone, if you have ADB enabled and are rooted.
bryantjopplin said:
Got a question, what root are you using in this? AICP switched to a systemless root magisk and couldn't get it working. Is this is still old school root? Systemless root has to patch the boot.IMG and with the bootloader locked it wont work? Correct? Just trying to understand. Thanks
Would like to switch.
Sent from my Nexus 6 with Pixel XL build.prop
Click to expand...
Click to collapse
I would also like to get clarification on this. I want to switch from my OctOS MM ROM to this. I have TWRP 3.1. installed, MDK bootloader.
@side, could you explain how root works on LineageOS 14 on this device?
side said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* 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, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Installation
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Download the EXPERIMENTAL and NIGHTLY builds using the download link below
Install the EXPERIMENTAL build, without wiping anything.
Reboot into Android
Reboot back into recovery
Install the NIGHTLY build, without wiping anything.
Enjoy LineageOS!
First time LineageOS 14.1 installation on your Galaxy S IV:
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the Lineage 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the Lineage 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - Lineage Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 or higher to automatically install updates in Lineage 14.1)
Push the new Lineage 14.1 zip to your SD card
Boot into Recovery
Flash the Lineage 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Install packages: https://download.lineageos.org/jfltevzw
Google Apps (arm): http://wiki.lineageos.org/gapps.html
Root add-on: https://download.lineageos.org/extras
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for S4 Verizon, ROM for the Samsung Galaxy S IV S4 Verizon, ROM for the Verizon Samsung Galaxy S4
Contributors
side, invisiblek
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2017-03-15
Last Updated 2017-03-15
Click to expand...
Click to collapse
Plz help...... after installing twrp i am unable to boot into recovery mode on my s4 verizon nk1 build . it always says : System software not authorized by Verizon Wireless : ? is there any way to replace stock bootloader or any other way to install custom roms ?
---------- Post added at 04:03 PM ---------- Previous post was at 03:57 PM ----------
I also tried safestrap recovery it installed but not boot
rohailadnan said:
Plz help...... after installing twrp i am unable to boot into recovery mode on my s4 verizon nk1 build . it always says : System software not authorized by Verizon Wireless : ? is there any way to replace stock bootloader or any other way to install custom roms ?
---------- Post added at 04:03 PM ---------- Previous post was at 03:57 PM ----------
I also tried safestrap recovery it installed but not boot
Click to expand...
Click to collapse
This ROM is for MDK bootloaders only. It is not safestrap-compatible. On NK1, you'll need to stick with safestrap-compatible ROMs (TouchWiz-derived).
Also, please don't quote the OP
Has anyone tried this ROM on their jfltevzw yet? If not, I may give it a try anyway (with a bit more caution).
@side @Titokhan @bryantjopplin @uhh186
@flamadiddle
Sorry to disappoint you, but I never have this device.
flamadiddle said:
Has anyone tried this ROM on their jfltevzw yet? If not, I may give it a try anyway (with a bit more caution).
@side @Titokhan @bryantjopplin @uhh186
Click to expand...
Click to collapse
Not yet, not my daily and haven't messed with it again. Still on the aicp. I think I might have tried but had issues with finding root under developer options. That might have also been for the gnex. Lol
Sent from my Pixel XL using Tapatalk
flamadiddle said:
Has anyone tried this ROM on their jfltevzw yet? If not, I may give it a try anyway (with a bit more caution).
@[email protected]@[email protected]
Click to expand...
Click to collapse
Yup. I don't use my jflte much but this ROM works well for all I've seen so far.
Flash it away (if you're on MDK)
uhh186 said:
Yup. I don't use my jflte much but this ROM works well for all I've seen so far.
Flash it away (if you're on MDK)
Click to expand...
Click to collapse
Great! Thanks for the reply. Have you rooted this ROM? If so, which method did you use?
flamadiddle said:
Great! Thanks for the reply. Have you rooted this ROM? If so, which method did you use?
Click to expand...
Click to collapse
SuperSU I believe.
Alright, I'm taking the plunge. Loading 20170412 weekly and trying the SuperSU System-mode installer
Not going great. I was able to flash LineageOS and Pico Gapps, but every attempt I've made to root (system-mode method) so far has ended in boot-loops.
@uhh186 any tips would be appreciated.
flamadiddle said:
Not going great. I was able to flash LineageOS and Pico Gapps, but every attempt I've made to root (system-mode method) so far has ended in boot-loops.
@uhh186 any tips would be appreciated.
Click to expand...
Click to collapse
I'm sorry; I don't use my SG4 anymore, I just play with it every once and a while to see if I can't get the latest software on it. I was wrong/misremembered when I said SuperSU.
We can't use SuperSU because nougat+ requires systemless mode, and we can't do that with a locked bootloader.
My SG4 is rooted, so I went and looked what I had done. It appears I had just flashed the LOS root module.
uhh186 said:
I'm sorry; I don't use my SG4 anymore, I just play with it every once and a while to see if I can't get the latest software on it. I was wrong/misremembered when I said SuperSU.
We can't use SuperSU because nougat+ requires systemless mode, and we can't do that with a locked bootloader.
My SG4 is rooted, so I went and looked what I had done. It appears I had just flashed the LOS root module.
Click to expand...
Click to collapse
No apology necessary. Thanks for the help. It is strange, though. I've completely wiped internal storage, formatted data, installed again, and tried the LOS root addon. I still don't have root. The ChainsDD Superuser app from the Play store thinks I have root, but Titanium Backup and Root Checker can't find it.
flamadiddle said:
No apology necessary. Thanks for the help. It is strange, though. I've completely wiped internal storage, formatted data, installed again, and tried the LOS root addon. I still don't have root. The ChainsDD Superuser app from the Play store thinks I have root, but Titanium Backup and Root Checker can't find it.
Click to expand...
Click to collapse
LOS root requires some weird hoop jumping. Go into your developer options and make sure Root Access is enabled for apps and ADB.
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
Most of the TWRP projects are gone, official one is only for the PRO (vayu) version.
At this point we don't have single trustworthy recovery (except limited LOS), and still bunch of available custom ROMs.
Which version can we use with some security?