Hello Guys after trying many roms I felt like making one for communtiy
But I didnt want to make it from scratch when google is already doing a great job
of directly proving system.img
So what I did was collected Best of all vendor and major required files for booting. Including Always on Display my favourite.
And made a Flashable Zip of that specific files, images,patches etc.
So yes this best vendor can be used on any GSI FILES which you may want to boot.
This is basically a best Suitable vendor for major roms and specific for all Google Android Roms, I will be updating it when needed
For now,
All you need to do is Install this Zip
Flash System.img (whichever you like generic or Pixel or Other Oem)
Mount system and Vendor
Flash Patch 1 & 2
Reboot System, setup everything
Install latest gms as and when available
Connect to PC (optional) and give commands provided. For best results.
Hope this is exhaustive guide
Download Links
Major Boot Vendor Files
https://drive.google.com/file/d/1GqXP2ddv1DTJ8at_nSZR2_rhRs9iJBhy/view?usp=drivesdk
Q. Why didnt you give whole rom.zip instead of such pieces
A. Because this is only for advanced users , noobs stay away. This is specially made to cater this user who will flash latest GSI images from google and dont have to wait for other Devs to make rom for them. Basically you have PixelUI with minimum bugs.
Q. Can I use other GSI With this vendor
A. As per my research and flahsing experience with this vendor I can say major boots so dont know about others.
Q. Will you support This Project
A. Yes I will and since its not difficult to flash gsi when available theirs no support needed
Q. I want support in sense how to flash and bugs
A. Youre idiot If you ask so since already said this is GSI not Rom bugs are from GSI you flashed so we cant solve. Though patches will be released when available
Special thanks to my group Tester/Fixer
https://t.me/joinchat/E1XkwhvIsDgznr0dMrxzXQ
Havoc OS DEVELOPER, major vendor files are from it including updater script.
Erfan gsi for providing system images at earliest
And you all guys for support
Youtube Video on Latest GSI
HTTPS://youtube.com/JigneshJain
Updated with latest links and vendor
Related
Hi,
I know there are a lot of guides out there but you still might want to read it
What are the different things I need to know ?
Well you will hear three terms very often. Baseband, Kernel and the ROM. Lets see what they are.
Baseband :
A firmware to drive the radio (2G/3G) chipset in your phone. Most of the time you don't need to bother thinking about it. But you might need to upgrade this firmware in order to get optimum performance. Just think of it as something you won't need to apply unless explicitly specified. For you xperia neo v, you can find out the baseband version by going into phone info and looking up baseband version number. I have not flashed any baseband. I recommend if you have not rooted/flashed your phone, install the official sony update you'll get the latest baseband without any troubles, this is what I did. Although if you need to flash it, there are very many tutorials available on this forum. You can check out the flashtool androxyde . github . com / Flashtool (sorry for the spaces in the links. I can't post outside links because of some forum rules which don't make any sense whatsoever)
Kernel:
This is the Linux (android) kernel image that drives all the hardware. Always install (flash) the recommended kernel for any ROM. Installing kernel and ROM is an absolute must.
ROM:
This is the actual thing you see running on your phone. It consists of the modified android source, user interface tweaks, the apps and some under the hood modifications done by the ROM developer for ex. cyanogenmod.
Now lets setup you linux (ubuntu) install fo installing a custom ROM on your phone.
Follow this wiki : wiki. cyanogenmod. com / wiki / Howto:_Install_the_Android_SDK
Don't forget to setup Udev by making a file /etc/udev/rules.d/51-android.rules with contents as
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="plugdev"
now restart your udev daemon by running "sudo restart udev".
Now yo have the necessary kernel and ROM flashing tools at your disposal. I am going to tell you how to achieve a fast and very battery efficient cyanogenmod install.
1) Download CM9 ROM and gapps(for google apps) from here
ROM: download. cyanogenmod. com /get / jenkins/4630/cm-9.0.0-RC2-haida.zip
Gapps: cmw. 22aaf3. com/gapps /gapps-ics-20120317-signed.zip
Copy these two zips to your phone's sd card.
2) Download night elf's kernel for cyanogenmod 9 from here mediafire. com /?nm7g0zid8aazfl1
3) Follow this guide wiki. cyanogenmod. com/wiki/Sony_Ericsson_Xperia_Neo:_Full_Update_Guide
But instead of flashing the kernel inside the zip, flash the night elf's kernel (just provide the path to night elf's kernel instead of the ROM's boot.img).
4) As told in the link given in above step flash both the zips. Before flashing you may also clear the Dalvik cache by going into advanced options in the recovery menu.
5) Reboot your phone. Don't turn off the GPS !!! There is a bug in CM9 RC2 which results in substantial hit on battery life. Just let it be. Anyways the GPS antenna is turned off unless any application is using it.
I am having approx more than two days of battery life with light/moderate usage (No data connection, occasional wifi).
CM9 may not be the best looking ROM. But I can assure you nothing beats it in the performance and the default setup (its very sane !!! No need to change anything at all). Also I only trust cyanogen community with all my very personal information (its my phone, it has everything !! ). If you need eye candy more and are comfortable with taking privacy risks, you may try MIUI and the dozens more ROM in the thread. I am not trying to offend anyone, its just my opinion, feel free to call me paranoid.
Always keep in mind that there are no stupid questions only stupid answers Ask away !!
I wish you a free and serene future.
I am however more interested in using the source code provided by Sony with AOSP and compiling the system image by myself.
I know how to compile AOSP, but the files provided by Sony doesn't seem to contain the `device` directory.
Also is it possible to use the AOSP and compile a ROM that is exactly the same as the stock ROM?
I haven't done any reading or experimentation on the subject but as far as I know, Sony only provides the stock kernal sources, some hardware support libraries (not all for ex HDMI, xLOUD still not provided). You can compile the kernel from Sony sources. Android image and apps are not provided by sony. All the ROM makers who are releasing ROMs based on stock are modifying the stock ROM image to do it.
For compiling your own ROM, you will have to do it form AOSP or cyanogenmod (FXP) sources.
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
Hi!
i am new to the treble-enabled stuff, this is the first phone i own that is treble capable and i have a few questions. I think they can apply to other NOBS, so here i go hoping some nice guy will help me understand:
Background: i have the redmi 5plus (global) which i have unlocked (after painful 720h) and i have flashed Pixel Experience 8.1 rom, but i like to experiment and it seems most of interesting roms are on treble.
1. By default, "vince" is not treble enabled. (treble check app says so)
2. "vince" seems to be an "A only" device, not A/B device,
Main Question: Now, what should i do to try (safely) some GSI roms (like here XDA LOS 16 GSI)?
Sub-Question 1: I must most likely flash some other things first, i guess... like a vendor or a treble image? Where do i find it?
Sub-Question 2: I have installed TRWP recovery, is it treble enabled or should i ALSO find a treble enabled recovery?
If i got it all wrong, please i would be happy to stand corrected!
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Xyzko said:
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Click to expand...
Click to collapse
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
gardiol said:
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
Click to expand...
Click to collapse
Months ago it started to appear some projects about android 9.0 before of Google revealed it as android Pie, then at this time devices with treble support also can support GSIs from these projects according two specific conditions: the processor (first qualcomm, then exynos, kirin and mtk were supported) and kind of partition system A-A/B.
At this first times was needed to flash a vendor treble supported rom to add treble support and flash over it a GSI 9.0. without the need to flash other kernel.
In this forum there are a lot of GSIs that eventually could work in our device but it could be many bugs https://forum.xda-developers.com/project-treble/trebleenabled-device-development.
Now is not needed to complicate the job flashing a vendor, then a GSI and maybe a custom treblized kernel so started to appear first developments of roms running 9.0 and these roms will work as exactly did it any rom 7.1 or 8.1, in the future they could be include treble support.
This is the short story.
After some searching I have several question:
1. Does every 8.0 + support treble , or I need a 8.0 + rom which claim it support treble , like https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555
2. There is a thing call `vendor` on treble project wiki : https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-3-3-Pro#booting-gsis-pie . What is this used for ?
3. Can I just flash above vendor instead of flashing a whole rom , then install gsi ?
4. I also found below 3 files , they contain `vendor` in names . Equal to above vendor?
https://androidfilehost.com/?fid=1322778262903982506
https://forum.xda-developers.com/showpost.php?p=79042530&postcount=161
https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555/page40
twinsq said:
After some searching I have several question:
1. Does every 8.0 + support treble , or I need a 8.0 + rom which claim it support treble , like https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555
2. There is a thing call `vendor` on treble project wiki : https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-3-3-Pro#booting-gsis-pie . What is this used for ?
3. Can I just flash above vendor instead of flashing a whole rom , then install gsi ?
4. I also found below 3 files , they contain `vendor` in names . Equal to above vendor?
https://androidfilehost.com/?fid=1322778262903982506
https://forum.xda-developers.com/showpost.php?p=79042530&postcount=161
https://forum.xda-developers.com/redmi-3/development/rom-treble-roms-gsi-t3831555/page40
Click to expand...
Click to collapse
1-just treble Oreo Rom which include vendor
2-i think that is source code
3-you can just install vendor then put GSI, no need the whole firmware
4-Use third link because some fixes available there
mohammadj26 said:
1-just treble Oreo Rom which include vendor
2-i think that is source code
3-you can just install vendor then put GSI, no need the whole firmware
4-Use third link because some fixes available there
Click to expand...
Click to collapse
Thank you very much ! :good:
Hello,
It's been a while I update myself about what's going on here. Please I would like to do full custom ROM installation on my 3 years old pocophone F1. I would to know step by step to follow. I am on stock ROM MIUI global 12.0.3 stable. And I haven't done anything on the phone as regarding to development area.
Please where do I start from if I want to run custom ROM on the phone with necessary things that won't make me regrets my actions?
Thanks all in anticipation.
Please let me know where to start from? I don't want to do what I know nothing about.
crDroid is an excellent choice. In my other devices I regularly change ROMs but in F1 it's been crDroid pretty much exclusively other than a brief dalliance with a few others in the beginning. Since you are on the latest MIUI, after unlocking bootloader, which wipes all data, you need to first flash the recovery of your choice, TWRP or Orangefox etc. Once that is done just need to flash the crDroid ROM zip which includes the Vendor and Firmware. If you are new to custom ROMs better to start with the crDroid 7.15 which is the final A11 build. A12 builds are pretty stable but several features are missing compared to it's predecessor which will be added in the coming months. A12 installation is a bit convoluted for now as the recoveries haven't been updated to handle it yet. A11 builds don't come encrypted by default.