Develop Bugs

[BOOT][4.2+][UNOFFICIAL] MultiROM for TF300T [2014-02-13]

MultiROM lets you install multiple ROMs into subfolders, just by flashing them using a modified TWRP.
This is an unofficial port of MultiROM originally developed for the Nexus series to our beloved TF300T.
Big thanks @Tasssadar for the original work!
THIS IS AN EARLY VERSION OF THIS PORT, NOT ALL FEATURES ARE FULLY TESTED.
But please test and give feedback, so I can eventually remove above line.
Features
Run a primary Android ROM from the normal partitions.
Run multiple secondary ROMs from subfolders on an SD card or on an external USB stick/drive.
Easily add/update your primary and secondary ROMs using a modified version of TWRP.
Install Ubuntu and Ubuntu Touch as secondary ROMs Not supported yet.
And more...
Changes vs. official MultiROM
This section is mostly useful for people using MultiROM on another device. New users can safely ignore it.
My first test - installing a plain CM 11, installing MultiROM, and then installing OmniROM with its own kernel - failed gloriously. The reason was that the official MultiROM re-uses the kernel of the currently installed Android system and that kernel does not include the kexec hardboot patch required for MultiROM to work properly.
The beauty of MultiROM is that - once installed with a proper kernel - it allows an average user that has never heard about kexec and never installed a custom kernel to run multi-boot at the touch of a finger. So I decided that my first simple use case must be supported.
The obvious solution was to ship a working kernel with MultiROM, save the currenly installed kernel for the primary ROM and boot that via kexec. The idea is to sacrifice another 10 secs on booting the primary ROM for making MultiROM much easier to install and to use. However, this decision led to several changes in the TWRP user interface:
The "share kernel with primary ROM" option was removed. Each ROM has its own boot image and is always booted via kexec.
The "Inject current boot sector" on the MultiROM screen button was replaced with a "Reinstall" button. Use this, if you have overwritten the boot sector, for example via fastboot. Mind, reinstalling MultiROM will save the current boot partition and use it for booting straight into the primary ROM, so better make sure this works, before running reinstall, or you won't be able to boot into your primary ROM after reinstallation.
The "Add/Remove boot.img" button on the ROM management screen has been replaced with "Replace boot.img" and can be used to easily install a custom kernel for that ROM.
Looking forward to your feedback on this major change!
Downloads
Downloads are available from the "Downloads" tab at the top of the page.
MultiROM installer including the modified TWRP:
multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.zip
TWRP for MultiROM (not needed, if you use the installer):
twrp-multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.blob
Installing and Upgrading MultiROM
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet. The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet. I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Make a backup!
MultiROM will modify your system, and if anything goes wrong, this backup will be more than helpful.
Check the version of your bootloader.
On the bootloader screen, check the version shown on the top left. MultiROM was ported and tested on version 10.6.1.27.5. If your bootloader version is 10.6.1.27.1 or 10.6.1.15.3 you should have no issues. Version 10.6.1.8 might work, but is likely to cause issues; upgrading is highly suggested. For any other version, make sure you first upgrade your bootloader, or you risk ending up with a brick,
Flash the lastest multirom-vXX-YYYYYYYY-UNOFFICIAL-tf300t.zip
Reboot right away!
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Now you should be able to boot your primary ROM via MultiROM. For next steps, check out "Installing ROMs" in the next post.
Uninstall MultiROM
The uninstaller for the official MultiROM has not been ported yet, but you can get rid of MultiROM following these steps:
Flash your favourite (not MultiROM) recovery.
Restore your boot partition from a backup or re-flash your ROM.
Remove the "multirom" folder on the sdcard.
The latter is optional. You may keep it around for trying MultiROM again later.
Changes
2014-03-16:
Fixed MultiROM reinstallation from TWRP.
Some fixes for swapping primary/secondary ROMs.
Some fixes for primary ROM initrd.
Added support for Ubuntu Touch (needs upcoming manager app).
2014-03-02:
Support secondary ROMs on SD card (not fully tested).
Use packaged initrd instead of the primary ROM's.
Some bug fixes.
2014-02-13:
Allows flashing 4.2-based ROMs without removing the assert line in the updater-script.
Several bug fixes for more stability.
Note that changes may be documented, before the downloads are available. Please check back a little later in that case.
Future Work
In no particular order:
Provide uninstaller.
Add the missing features listed above.
Fix TWRP for encrypted filesystems.
Allow replacing the kernel for any ROM, keeping the ramdisk.
Remove unnecessary drivers (net, sound, camera) from the kernel (currently breaks building the kernel).
XDA:DevDB Information
MultiROM for TF300T, a Tool/Utility for the Asus Transformer TF300T
Contributors
f69m
Version Information
Status: Alpha
Created 2014-02-11
Last Updated 2014-03-16

Installing ROMs
Custom 4.2- and 4.4-based ROMs
To install/update your primary ROM, just flash it as usual with the modified MultiROM TWRP, using "Install" from the main screen.
Installing a secondary ROM is just as easy, but use:
Advanced > MultiROM > Add ROM
You can update a secondary ROM by flashing it from the ROM management screen, using;
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
OTA updates using the update manager coming with your ROM should work fine for both primary and secondary ROMs.
Note: It is no longer necessary to remove the assertion from a 4.2 updater-script.
Gaps, SuperSU, etc.
You can flash additional ZIP files for a secondary ROM from the ROM management screen, using:
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
Asus Stock ROM
Asus stock ROM has a different installer and won't work the same way as custom ROMs.
Here are the steps to install stock ROM as your primary ROM:
Sorry, I have not tested this myself yet, please let me know, how it works out.
Unzip the Asus ROM twice to get the blob.
Flash the blob using fastboot.
Boot into stock ROM.
Re-install the modified TWRP using fastboot (use the separate download).
In TWRP: Advanced > MultiROM > Reinstall.
This should give you a working MultiROM setup with stock ROM as your primary ROM.
If you need more detailed instructions on the first two steps, please refer to the guides in the General section.
Ubuntu Touch
Coming soon...
Ubuntu
Not working yet.
Notes on Specific ROMs
CROMi-X 5.3
Don't try to install CROMi-X as a secondary ROM. It has an amazing installer, but that will nuke your primary ROM's /system partition.
Trouble-shooting
If your primary or one of your secondary ROMs is not booting properly, it can help to restore the boot partition of the primary ROM and then do a clean reinstall of MultiROM.
No worries, you can move your installed secondary ROMs to the side and move them back later.
First try restoring the boot partition from your latest backup, before installing MultiROM and reboot.
If your device boots cleanly into your primary ROM, without showing the MultiROM boot screen, you can skip ahad to step 3.
Next try flashing an unmodified recovery, re-flash your primary ROM and reboot.
If your device boots cleanly into your primary ROM without showing the MultiROM boot screen, you are ready to go to step 3.
Otherwise you should post your issue.
Use a root terminal or a root exlorer to remove the folder /data/media/0/multirom.
Alternatively you can rename that folder, keeping your installed ROMs.
Note: though this folder is on the sdcard, you have to use the path given; trying to use /sdcard or /storage you will get "permission denied", when trying to remove or rename the folder.
Reflash the latest multirom-v*.zip and reboot.
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Try booting your primary ROM. It should now start cleanly.
Try installing a secondary ROM, or move it back to /data/media/0/multirom/roms/ from the folder you renamed above.
Just moving back the folder will make it show up on the MultiROM boot screen.
Please read and follow each step carefully.
If these steps do not make all your ROMs boot properly, please post about your issue in this thread.

Source Code Repositories
The easiest way to build MultiROM is using my manifest following the build instructions below.
Here is a list of the MultiROM-specific repositories that can be built by adding them to the OmniROM tree:
Latest manifest:
https://github.com/f69m/android
MultiROM (check out to "bootable/multirom"):
https://github.com/f69m/multirom
TWRP for MultiROM (check out to "bootable/recovery"):
https://github.com/f69m/multirom-twrp
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
TF300T device config (check out to "device/asus/tf300t"):
https://github.com/f69m/android_device_asus_tf300t
TF300T kernel (check out to "kernel/asus/tf300t"):
https://github.com/f69m/android_kernel_asus_tf300t
Look out for branches named "multirom-*" in above repositories.
Please check the manifest for the latest stable branch.
Build Instructions
Using my manifest makes it easy to check out the MultiROM repositories and a small part of the OmniROM tree needed for building.
Code:
repo init -u git://github.com/f69m/android -b multirom
repo sync
manifest/pick-cherries.sh
source build/envsetup.sh
lunch mrom_tf300t-userdebug
make -j4 multirom_zip

Sweet! Thanks man, this looks pretty cool!
Sent from my SGH-T999 using xda app-developers app

Finally, first download is up!
Let me know, how it works for you.

Thanks for your work.
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??

z1022 said:
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
Click to expand...
Click to collapse
Absolutely, just flash the multirom-*.zip file (includes TWRP), and you should be able to boot into CROMi-X via MultiROM.
But I have not tested with CROMi-X yet, so make sure you have a backup!
Sent from my TF300T using Tapatalk

Thanks
I will try later and report back.
CROMi kernel should be not included the kexec. Can I use the Multirom to install second ROM ??

z1022 said:
I will try later and report back.
Click to expand...
Click to collapse
Great, looking forward to hearing about your experiences.
CROMi kernel should be not included the kexec.
Click to expand...
Click to collapse
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Can I use the Multirom to install second ROM ??
Click to expand...
Click to collapse
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk

Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
As Primary ROM i have NIGHTLY CM11 for TF300T. As "virtual" ROM i installed the same ROM (i want to examine the new GRIMKERN_KitKat).
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.

Dasdranamin said:
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
Click to expand...
Click to collapse
Wow, amazing!
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Click to expand...
Click to collapse
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Sent from my TF300T using Tapatalk

f69m said:
Wow, amazing!
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Click to expand...
Click to collapse
Yes. That's what I meant.

Dasdranamin said:
Yes. That's what I meant.
Click to expand...
Click to collapse
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Sent from my TF300T using Tapatalk

f69m said:
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
Click to expand...
Click to collapse
Yes, in TWRP touch works without any problem!
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Click to expand...
Click to collapse
That would be great! Thanks in advance!

f69m said:
Great, looking forward to hearing about your experiences.
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.

z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
I successfully installed just now on TF201 Omni 4.4.2. ROM TF300T Homebuild versions [20140126] (it's last ROM with MultiWindow feature) + Gapps Mini Modular Package.
All works properly. :good: MultiWindow too.

how long omni finished the booting.
---------- Post added at 11:59 PM ---------- Previous post was at 11:50 PM ----------
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
Try CM11 in second ROM. still stick in CM11 booting screen.

z1022 said:
how long omni finished the booting.
Click to expand...
Click to collapse
First time about 5 min (with Gapps).
Next times about 2 min.

Nice! cant wait to try this, thanks for your hard work!

Hi f69m,
I found: in "MultiROM menu that comes up after boot" I can select a ROM by VOLUME UP/DOWN and confirm by POWER (like in "old" CWM). :laugh:

Unlocking the 32GB Mi5 frequency

Hi guys, I have been looking at / working on allowing the 32GB variant Mi5 to run at the full speeds (2.15/1.6/624) on the msm8996 SOC as its 64/128GB brothers.
I was able to patch the kernel frequency table to run my 64GB at the reduced frequency of the 32GB but cannot test this in reverse as I don't have a 32GB device
I am hoping a 32GB user can test a boot.img for me. Can fastboot boot/flash it, or flash via TWRP (install -> install image -> select img) and just backup your existing img.
I do suspect it will not boot or work (it does boot/otherwise work on my 64GB though, but there's a few more code differences I haven't changed), but it'd be nice to know
boot_rev1.img this revision does not work, yet
boot_rev2.img a few users report that this one works.
What I would like to know is overall stability for 32GB users, if they could test their phone in games etc as voltage tables may need more adjustment
Edit: please note this kernel is for CM13/AOSP based ROM. please don't flash it over MIUI8
Project moved to http://forum.xda-developers.com/mi-...d-32gb-mi5-t3482455/post69177557#post69177557
Source here: https://github.com/harrynowl/falconkernel-gemini

awesome. did you post in the miui forum?

rochee94 said:
awesome. did you post in the miui forum?
Click to expand...
Click to collapse
Not yet, hoping to find feedback here first

As you are using CM kernel as base, you must inform that this will only work on devices running MIUI 7.x firmware and a CM based ROM.
On top of that, don't forget to publish the link to the kernel source in order to follow XDA's GPL regulations. I know you have the source in Github.

Could you build a kernel to overclock the 64 &128GB versions too? That would be great.

Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)

razibrizal said:
Sorry out of topic but, does snapdragon 820 have mpdecision or not? (by default)
Click to expand...
Click to collapse
No: https://source.codeaurora.org/quic/...init.qcom.post_boot.sh?h=LA.HB.1.3.1.c1#n1729.

GalaxyS4_Lollipop said:
Could you build a kernel to overclock the 64 &128GB versions too? That would be great.
Click to expand...
Click to collapse
First focus is on giving 32GB users the full power of the hardware they paid for

I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Edit
Using AOKP and Cm13 same result

sys01 said:
I've tried it and it fails to boot
It goes into the bootanimation but after like one second it freeze and reboot
And when it happen, it kinda overheat
Click to expand...
Click to collapse
Thanks for info, I think I know why this is..

Harrynowl said:
First focus is on giving 32GB users the full power of the hardware they paid for
Click to expand...
Click to collapse
That's cool.
Anyway, if it is any method to power up the beast to the SnapDragon821 power, I wait for it. (on 64gb)
Good luck and thanks for your support.

4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !

Alex4455 said:
4 days ago bought a 32gb Mi5 -> upgraded to latest MIUI 8.0.12
Unlocked bootloader -> Flashed Ressurection Remix's latest ROM via TWRP
Looking forward in testing this !
Click to expand...
Click to collapse
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:

Looking forward towards the fix.
Many people will be happy if this comes out with no issues !

Harrynowl said:
Well, please don't use the one I posted originally as it won't work. But I'm looking at a fix now :good:
Click to expand...
Click to collapse
thank u for the initiative will wait for the next build :good:

pls after making it work, build one for MIUI 8 if it's possible.

catalizgar said:
pls after making it work, build one for MIUI 8 if it's possible.
Click to expand...
Click to collapse
Miui8 firmware blobs are not currently compatible with the kernel sources we have.
A member got a kernel booting on miui8 but stability was a big problem.

First of all, thank you. I think all 32GB users will thank you for that.
Obviously when it's done, it will consume more power, and would have less SoT.
Can you make predictions of what it will take when optimized and fully working?

After changing my ROM to AOSP based I will use this. thanks for your hard working. really appreciated

I added a new boot.img to the OP with some updates to the source. Hopefully this one has more luck. Specifically changes to the voltage table(s).
Please test 32GB users

[ROM] [LINK] Sailfish OS 2.1 JBBL ONLY

the original OP is VERY confusing. Take a look for credits sake though. I am putting a link to the download page below it.
I DIDN'T MAKE THIS ROM! All credit for the Droid Razr M build goes to elros34, also please thank vevgeniev for making the Photon Q port.
JBBL ONLY!!! -- I MIGHT be tempted to try and build a KKBL port if enough people are interested, but at the moment, JBBL works flawlessly, and a few KKBL users downgrading their Boot loaders is way easier than me building a whole new (most likely) barely functioning port just for KKBL, when we already have a great JBBL port
What works:
Camera
Wifi
GSM: Everything works, including calls, data, and text
CDMA: I don't use CDMA but as far as I know, only calls work.
Vibration
Audio and Video
>>*when using the YTPlayer app, turn off early video loading in Settings>Player>Early video loading = set it to "Never"*
USB MTP to both my PC and my Chromebook.
What doesn't work:
nothing, this is a ROCK SOLID PORT!
you have to first flash CM11, and then flash sailfish over it.
So I was browsing around the Photon Q xda page and saw this gem. I would have passed it over and just thought "neat" and moved on, but as I skimmed the page I saw that it is based on msm8960_jbbl sources, so it theoretically works on all unified msm8960 devices on jbbl. I actually read the OP and low and behold there is the RAZR M on the list of supported devices. I didn't make this (obviously) but definitely swing by the original thread and take a look.
NOTE: THE PHOTON Q PORT WON'T BOOT ON THE XT907 OR XT905 - Please use the elros34 build linked in the Direct Download links section.
https://forum.xda-developers.com/photon-q-4g-lte/general/sailfishos-2-0-motorola-photon-q-t3281262
http://www.vladislavonline.com/sailfishos-for-photon-q/
DIRECT DOWNLOAD LINKS
CM11 BASE [ https://archive.org/download/cmarch...626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip ]
Sailfish OS 2.1.3.7 alpha3 xt907 [ https://goo.gl/DJ8zre ] || Mirror [ https://onedrive.live.com/?cid=f188cb653189eae0&id=F188CB653189EAE0!403&authkey=!AGtl3flkGPJHaiE ]
rahimali AFH: [ https://androidfilehost.com/?w=files&flid=236124 ]
Headphone Jack fix for xt907 ---> HEADPHONE JACK FIXED IN ALPHA BUILD 3, THANKS elros34!!!
tested and working on the alpha 2 build, thank elros34 for this not me, he is the genius behind this one, think of me as a parrot.
You need to either use ssh on your computer, or the terminal app on your phone. You also need to set a root password in Settings -> Developer Options
devel-su
[input root password]
vim /etc/ohm/plugins.d/accessories.ini
*you'll see 4 lines, one of witch being Jack Match = /dev/input/event5 (or something similar, you'll see it, it should be the last line in the file)
*enter the letter "i" to edit
*replace "/dev/input/event5" with "/dev/input/event4"
*enter CTRL+C
*enter ":", and enter "write"
*now hit ":" again and enter "quit"
reboot your device and now headphone jack should work, hooray!
I DID NOT MAKE THIS!!! I AM SIMPLY LINKING IT FOR OTHER XT907 USERS TO ENJOY! CREDIT TO elros34 FOR THE PORT TO THE RAZR M, AND vevgeniev FOR MAKING THE PHOTON Q PORT!

The link doesn't seem to work. Says an error has occurred.

link is not working

faisala66 said:
link is not working
Click to expand...
Click to collapse
Ill update it :good:
The one drive links works fine on my chromebook, but Ill replace it with the direct one I find in the thread.

I've shared the files here

it is for kkbl?

faisala66 said:
it is for kkbl?
Click to expand...
Click to collapse
Nope. JBBL only.

rahimali said:
Nope. JBBL only.
Click to expand...
Click to collapse
but it says it is for kkbl and I have also installed in my phone in KKBL

faisala66 said:
but it says it is for kkbl and I have also installed in my phone in KKBL
Click to expand...
Click to collapse
Good for you! :good:

rahimali said:
Good for you! :good:
Click to expand...
Click to collapse
thanks but its not booting

faisala66 said:
thanks but its not booting
Click to expand...
Click to collapse
So what do you expect if you don't follow instructions?

rahimali said:
So what do you expect if you don't follow instructions?
Click to expand...
Click to collapse
sorry sorry i wlashed wrong CM11 snapshot (msm8960) it is for (msm8960jbbl) right:laugh::good:

its working great. but it is not android rom and i cant run apk

faisala66 said:
thanks but its not booting
Click to expand...
Click to collapse
then it's obviously only for jbbl, switch to jbbl if you want to use this, its a real quick 10 minute process, and since this is a GNU/Linux rom, the downgrade won't do much.

faisala66 said:
its working great. but it is not android rom and i cant run apk
Click to expand...
Click to collapse
well yeah, it isn't an android rom, so you won't be able to run android apps. It is a GNU/Linux based OS, the only way you will be able to run android apps is if you somehow hack in alien dalvik (edit platform manifest file, cross your fingers), or get one of the other android emulators set up. The reason you use Sailfish OS is because it is lightweight, fast, and a generally beautiful and fun to use OS.

It's stuck in the bootlogo here.
I used the CM11 mentioned in the OP (from here), SailfishOS 2.0.1.11 (from here) and ilichva's TWRP 3.0.2-1 (DiamondJohn's TWRP 3.1.1-1 failed with error 7). Both data and system partitions are ext4. Am I missing something? Thanks in advance.

hernandezjonathan21 said:
It's stuck in the bootlogo here.
I used the CM11 mentioned in the OP (from here), SailfishOS 2.0.1.11 (from here) and ilichva's TWRP 3.0.2-1 (DiamondJohn's TWRP 3.1.1-1 failed with error 7). Both data and system partitions are ext4. Am I missing something? Thanks in advance.
Click to expand...
Click to collapse
you are on JBBL right? I used that same zipe and rootfs and all is good.. you flashed the cm zip, then the sailfish zip on top without wiping anything right? and you wiped all your partitions (except internal and external sd of course) before hand?\
EDIT: You are using a photon Q build on xt907, no wonder it won't boot. grab the one from the bottom of the rahimali afh link or the xt907 one in the downloads section.

Galaxyninja66 said:
you are on JBBL right? I used that same zipe and rootfs and all is good.. you flashed the cm zip, then the sailfish zip on top without wiping anything right? and you wiped all your partitions (except internal and external sd of course) before hand?\
EDIT: You are using a photon Q build on xt907, no wonder it won't boot. grab the one from the bottom of the rahimali afh link or the xt907 one in the downloads section.
Click to expand...
Click to collapse
Alright, gotta try it ASAP (which means in a week or two :crying. Any fixes for the headphone jack?
EDIT: Nevermind, I just saw the updated OP. Now this is looking reaaaally good for a daily driver.

hernandezjonathan21 said:
Alright, gotta try it ASAP (which means in a week or two :crying. Any fixes for the headphone jack?
EDIT: Nevermind, I just saw the updated OP. Now this is looking reaaaally good for a daily driver.
Click to expand...
Click to collapse
headphone jack is being patched in the new update, elros34 should release it by tonight, he was messing with it on the IRC (it'll be based on the newest version of sail and have fixed headphone jack built in, hooray!!! )

I'm replying from Sailfish in my XT907! I tried to install the alpha 3 from @rahimali's folder and it didn't boot (I wasn't surprised though, as it said it was for XT897).
Battery seems to last waaay more than Android and it's really fun to use! I just need to find a way to use WhatsApp.

[ROM][AOSP][7.1/8.1 EXP][K3.4][Repartition] Unlegacy Android Project

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 the 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:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL 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.
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 Transformer TF300T
Contributors
Clamor, Ziyan
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
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
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 Stock or Bootloader 4.2 attached in Downloads section.

How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom

androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.

Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:

androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread

Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.

androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS

TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.

Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned

I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?

@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.

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 here from O for now. I know already about all major issues.

I have some good news. Here is mostly working Oreo 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

Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.

@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.

@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).

@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.

Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.

project treble?

Is anyone working on porting project treble? I would think it would make rom building much easier if this was achieved.

mattlowry said:
Is anyone working on porting project treble? I would think it would make rom building much easier if this was achieved.
Click to expand...
Click to collapse
It wouldn't make much difference per what @invisiblek and @npjohnson stated. We could put the vendor blobs on it's own partition, but it wouldn't make building any easier as we still have to get the blobs. ROMs are already working minus gapps install, LTE for Sprint, selinux rules, and audio recording (camcorder, Skype, VoIP calls on soft phones, etc). There might be smaller issues I don't notice personally.

Uzephi said:
It wouldn't make much difference per what @invisiblek and @npjohnson stated. We could put the vendor blobs on it's own partition, but it wouldn't make building any easier as we still have to get the blobs. ROMs are already working minus gapps install, LTE for Sprint, selinux rules, and audio recording (camcorder, Skype, VoIP calls on soft phones, etc). There might be smaller issues I don't notice personally.
Click to expand...
Click to collapse
Ok I was just doing a bunch of reading on the topic and it appeared that there were generic images that could be flashed when you have treble

mattlowry said:
Ok I was just doing a bunch of reading on the topic and it appeared that there were generic images that could be flashed when you have treble
Click to expand...
Click to collapse
Generic images won't have motomods support. Right now, the greybus driver is built in-line with the kernel and sits in the boot image which would change with a generic image.

Uzephi said:
Generic images won't have motomods support. Right now, the greybus driver is built in-line with the kernel and sits in the boot image which would change with a generic image.
Click to expand...
Click to collapse
No one cares about Moto mods ?

mattlowry said:
No one cares about Moto mods ?
Click to expand...
Click to collapse
? yeah, if only. I get hounded because my AOSP kernel doesn't support motomods due to me building with linaro still and it causes issues with the build of the greybus drivet

if we use the oem partition and created a GSI for the Moto z family then treble could be usable with moto mods built in with the standard gcc toolchain google used, correct me if im mistaken but i think they are still on 4.8. Anyway treble can mean really big thing i bricked my AT&T moto z2 trying to exploit it to gain root (epic fail on to the tmobile unit that works now) on it and have since replaced and started looking into treble as the custom roms i was building had a GSI, so i then wanted to focus on getting a treble system up and running on my z2 force and will post once i have better progress and a repeatable process.

Kaesberg said:
if we use the oem partition and created a GSI for the Moto z family then treble could be usable with moto mods built in with the standard gcc toolchain google used, correct me if im mistaken but i think they are still on 4.8. Anyway treble can mean really big thing i bricked my AT&T moto z2 trying to exploit it to gain root (epic fail on to the tmobile unit that works now) on it and have since replaced and started looking into treble as the custom roms i was building had a GSI, so i then wanted to focus on getting a treble system up and running on my z2 force and will post once i have better progress and a repeatable process.
Click to expand...
Click to collapse
It all would work except for one thing. Motomods. That is in system and kernel. Both are not in the treble images.

Uzephi said:
It all would work except for one thing. Motomods. That is in system and kernel. Both are not in the treble images.
Click to expand...
Click to collapse
sweet so when i rebuild a GSI if it is made to include the files in the image, and maybe a extra zip for a kernel to go with it? i want to build a GSI ROM i can install on the whole Z family, and it sounds like it may need to have an extra package to install after the GSI. this treble thing is a new field for me so i am just trying to see what we can do with it.