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:
Related
I am working on porting the latest upstream version and will update this post as things start working.
Things to do:
[DONE] Create boot image that boots into the Ubuntu Touch rootfs.
[DONE] Create Android container started by Ubuntu.
[WIP] Customize configurations and work on kernel and android system to make things work properly (e.g. audio).
[TODO] Setup apparmor security.
Testing, debugging and optimization...
Any help is welcome!
The information and images below are very out-of-date.
The port of Ubuntu Touch to our beloved TF300T is more or less working now.
Please see section "Known Issues" below.
And please read the instructions carefully, including the linked threads, before doing anything to your tablet that might result in a very expensive paper-weight.
Known Issues
Just listing major issues that are specific to the TF300T port.
This is not the place to discuss general issues with Ubuntu Touch.
Camera is broken.
Dock not fully supported.
There are probably more; please follow this thread and report any new issues you find.
Downloads
Please read the section "Installation" below carefully, if you are not sure what these files are.
That section also contains verbose information on the different bootloader versions.
The binaries are generated automatically by Jenkins.
Generally they are not tested and may be broken.
Please report any issues in this thread, so they can be fixed and broken binaries can be removed.
Bootloader 4.2
These are the latest binaries that should be up-to-date with respect to Canonical's binaries.
Well, sometimes allow a day or two...
Android Base-System
The Android base-system is a stripped-down version of CyanogenMod 10.1 with some additional patches.
This is, where the major effort for porting Ubuntu Touch goes into.
Ubuntu Touch Root FS
This is the Ubuntu Touch file system.
Flashing this ZIP will preserve network settings and the phablet home directory, if you had installed Ubuntu Touch before.
It should work for all devices, however a stripped-down version with some changes for our TF300T is provided.
Please see the list of changes below.
Media Files
These media files are part of Canonical's root fs, but they rarely (never?) change.
Splitting the media files into a separate image significantly reduces the size of the rootfs that receives regular updates.
Unless you manually remove /data/ubuntu, these files will persist re-flashing the rootfs.
Bootloader 4.1
These are out-of-date and are no longer being maintained.
They will be kept, till dev-host deletes them (30 days after the last download):
Android Base-System
Ubuntu Touch Root FS
The rootfs for bootloader 4.1 also includes the media files. There is no separate download.
Android Source Code
The patched repositories of the Android/CyanogenMod/Ubuntu source trees are available on GitHub.
For details, please see section "Building the Android Base-System from Source" below.
Ubuntu Touch Root FS Changes
The "official" Ubuntu Touch root fs does not quite work on our TF300T yet.
So a stripped-down version with the following changes is provided:
Run amixer on boot to fix mixer levels.
Disable save/restore of alsa settings.
Split media files into a separate image.
Remove several big and unnecessary files.
The official Ubuntu Touch image does work, but for these issues:
Flashing with TWRP fails.
For details, see the bug report on launchpad.
There is no sound, unless you adjust alsa mixer levels manually.
Rebooting from Ubuntu goes into a boot-loop.
When Ubuntu is properly shut down, it saves the current alsa settings.
Restoring them on the next boot crashes the system and causes the boot-loop.
Note that rebooting from Android or using adb works fine.
If you happen to run into the boot-loop, use the TWRP file manager (in the Advanced menu) to remove /data/ubuntu/var/lib/alsa/asound.state.
Installation
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.
Step 1: Unlock Your Tablet
If you want to give Ubuntu Touch a try, your tablet needs to be unlocked.
There are lots of threads helping with this, please use search to locate this information.
Step 2a: Which Bootloader Do I Have?
Unfortunately, Asus has released several incompatible bootloaders.
To find out, if you can use this port of Ubuntu Touch, go to the bootloader screen by holding the power and vol-down keys.
Once you see the bootloader screen with three or four icons in the center, check the long version number at the top of the screen.
It looks something like: "WW_epad-10.6.1.15.3-20130416".
The first two letters are your SKU and should not matter.
The version number following "epad" is what will be referred to in the following.
Version 10.6.1.15.3
This is the latest version from Asus, generally referred to as "bootloader 4.2" in the XDA forums.
The latest Ubuntu Touch binaries are developed and tested on this bootloader, so you should be fine.
Version 10.6.1.8
This is an older version of the bootloader 4.2.
The latest Ubuntu Touch binaries might work for you, though upgrading your bootloader is recommended (see below).
This version is known to cause issues with the latest TWRP recovery, so be careful.
Version 10.4.2.20
This is the old incompatible bootloader, generally referred to as "jb bootloader" or "bootloader 4.1" in the XDA forums.
The latest Ubuntu Touch binaries will not work for you, upgrading your bootloader is strongly recommended (see below).
Older binaries that work with this bootloader are still available for download though.
Any older version not listed
Your bootloader is really out of date and you should upgrade as soon as possible (see below).
Any newer version not listed
You are on uncharted territory. Proceed with care!
Let us know about your experience in this thread!
Step 2b: Upgrade Your Bootloader
If you have not yet installed bootloader 10.6.1.15.3, it is recommended to upgrade.
Please check the following threads (and several others; search might be helpful):
[GUIDE][26/04]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Step 3: Install TWRP Recovery
You need a custom recovery installed for flashing the Ubuntu Touch binaries.
Please check the following thread for getting and installing TWRP recovery:
[RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery!
Step 4: Backup and Wipe Your Android System
Before flashing Ubuntu Touch, you need to wipe some parts.
It is strongly recommended to make a backup of your Android system too.
Check section "Restore Android" below on how to restore it.
If you are running CyanogenMod 10.1:
Use TWRP to backup "boot" and "system".
Backing up "data" is not strictly necessary, but recommended.
Wipe "cache", "dalvic cache" and "system".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
If you are not running CyanogenMod 10.1, but another ROM:
Use TWRP to backup "boot", "system" and "data"
Wipe "cache", "system" and "data".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
Step 5: Flash Ubuntu Touch
If you want a clean start or you had installed Ubuntu Touch for bootloader 4.1, please remove /data/ubuntu manually before flashing.
You can use the TWRP file manager in the Advanced menu for that.
If you want to upgrade from a previous Ubuntu Touch for bootloader 4.2, please see section "Upgrade Ubuntu Touch" below.
Flash the following images (see above for downloads):
ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-media-XXXXXXXX.zip
Step 6: Reboot Your Tablet
Note that there is no boot animation yet, so the screen will be black, till the shell is starting up.
This make take some time, please be patient!
Restore Android
Boot into TWRP recovery.
Wipe "cache" and "dalvic cache".
Select the last backup done before installing Ubuntu Touch.
If you were running CyanogenMod 10.1:
Restore "boot" and "system".
If you were not running CyanogenMod 10.1, but another ROM:
Restore "boot", "system" and "data".
Reboot your tablet.
Upgrade Ubuntu Touch
Generally, the system and the rootfs can be upgraded individually.
However, sometimes Canonical introduces breaking changes, that require them to be upgraded together.
Upgrade ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
If you are running an older version of that ZIP, you can just flash the new one.
If you have returned to your Android system, please follow "Backup and Wipe Your Android System" under "Installation" above before flashing the new ZIP.
Upgrade ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
You can flash this ZIP anytime.
Network settings and the phablet home directory will be preserved. This includes the media files from the separate ZIP:
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Upgrade ubuntu-touch-media-XXXXXXXX.zip
You can flash this ZIP anytime.
It will just overwrite existing files and add new files; old files will not be deleted.
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Building the Android Base-System from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b phablet-10.1-tf300t
You can also run this command in an existing repository.
Thats great, but ...
f69m said:
Current Status:
Ubuntu Touch is booting and can be accessed via adb, but the screen stays black.
Click to expand...
Click to collapse
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Shu. said:
I have the exact same issue even on the official build released for nexus 4
Click to expand...
Click to collapse
Oops, that is intersting, thanks!
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed, if your interest is to have something to play with.
On the other hand, I'd like to see, what is already there and possibly help improve it by contributing to Canonical. And any work we do now will speed up porting, once there is a better release available.
Just trying some more Kernel tweaks after looking at the TF700 port that seems to work (see http://forum.xda-developers.com/showthread.php?t=2162472).
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
Shu. said:
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed but I have gotten it up and running on my nexus 4 without much issue, its cool for about 20 min( being generous) but then you realize you can't actually do anything. I feel that its gonna be an awesome platform especially for a transformer tablet though if it goes where they say it will. Full Ubuntu when docked and then touch when not....sounds like what these tablets were made for.
Sent from my Nexus 4 using xda premium
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
matonka007 said:
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
Click to expand...
Click to collapse
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
ColMustard said:
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
Click to expand...
Click to collapse
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
doubljdog said:
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Click to expand...
Click to collapse
Yes I realized that after I posted this. Just pointing out that someone has committed to porting this.
Edit: Thanks for pointing out the obvious though,I'm sure nobody else would have figure this out
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
So, is there someone working on it, or not?
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
How did you load the patch in your make file? I am adapting your patch to my device.
secosan said:
So, is there someone working on it, or not?
Click to expand...
Click to collapse
Yes, I am working on it, and so are some others.
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
Click to expand...
Click to collapse
That is interesting, thanks!
What happens on the tf300t using the CM tf300t base code is a segmentation fault.
The nv video drivers send a null file pointer to fputc() in the Ubuntu libc.
Just trying to do a quick fix, by building my own libc that silently ignores the null pointer, but that is sure not a final solution.
Eventually we need to figure out, where the null pointer comes from and avoid it.
I'll let you know, how it works, once the lenghthy ARM compilation has finished and I had a chance to try it.
WLAN is working fine, BTW, just the display is black.
giveen said:
How did you load the patch in your make file? I am adapting your patch to my device.
Click to expand...
Click to collapse
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Canonical started the daily building of Ubuntu Touch, good news I tryied the build for TF700 too, but it have bad DPI.
PS: f69m, I do not know about developing, but if I can help you write.
Re: [DEV] Porting Ubuntu Touch Preview to TF300T
f69m said:
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Click to expand...
Click to collapse
I was referring to the screen res patch, but I figured it out from your guide.
The problem I am having that my kernel not compiling with Ubuntu options even though I sent them in my defconfig.
They should be working but they are not.
Sent from my Nexus 7 using Tapatalk 2
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
matonka007 said:
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
Click to expand...
Click to collapse
Definitely not my build, I have no images out yet, but mine should be coming soon!
The entry in the device table was not added by me.
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
It sound great
Yes, Dropbox is good choice
And http://d-h.st/is not bad for sharing files
f69m said:
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
Click to expand...
Click to collapse
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
-angel* said:
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
Click to expand...
Click to collapse
Of course, l will make sure to update everywhere, once the image is released, though the entry in the Ubuntu wiki was not done by me.
Got a flashable filesystem now, but that version is crashing on me. Must be something small I am overlooking atm.
So taking a little break and then will finish with refreshed spirit.
Please Don't Quote This Post,
It's Just way too big and would make any comment look stupid,
Thanks
Just When You Thought Your Favourite Dev Is Out Of Ideas... He Comes Up With This
ok so alot are complaining how we can't flash kernel away from the pc among other things (which ill get to later ), (mostly @One-X-master)
so i looked for a way to get around this and found Kexec as the answer.
Wiki said:
In computing, kexec (kernel execution) is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware or BIOS) and directly loads the new kernel into memory, where it starts executing immediately. This avoids the long times associated with a full reboot,and can help systems to meet high-availability requirements by minimizing downtime.
Click to expand...
Click to collapse
however, with that comes managing online hardware which is somewhat problematic,
thus that prompted few people to come up with an ingenious solution called Kexec-hardboot.
Kexec-hardboot:This works by loading the kernel into memory and force restarting the phone with new kernel.
All of that with some ramdisk tweak allowed me to set a kernel at boot and restart to it,
avoiding having to flash it in the 1st place
Updating the kernel is called flashing..
A Flash is also what precedes Thunder
its also refered to as Lightning, Thus I came up with the name Kernel Lighter
Lighter= To Set Things On Fire/To Ignite (The Kernel)
Thus this is a kernel igniter
I Know, i've got to much time on my hand.
If you have a smart name, please do suggest.
Special Thanks: @Tasssadar: For His N7 Port, which made this port a breeze and for his help in debugging.
@Alex-V: Currently using his kernel as Base Kexec Kernel.
@Androguide.fr: For his recovery-less flash method.
@amarullz: For His AromaFM Source Code.
@LlabTooFeR: For His Stock Kernel.
@faux123: For His Kernel Source.
@mkasick: For The Original Port.
Sources:Alex-V 1.7 Kernel
Hardboot Patch
Faux Kitkat Kernel
AromaFM KL
Download Link In Post Below
Always have a backup.
Attachement & How-TO
ALL THE STEPS MUST BE FOLLOWED.
Requirements
S-off/Unlocked Bootloader
Android App & Recovery App
Fastboot flash boot Zeus.img
For ZeusKL.v10.img (New Layout) You must first switch to the new layout
Flashing Kernels Though Recovery
Boot Into Recovery
Flash AromaFM-KL.zip
Select Kernel Zip To Flash
Choose Flash Location
Choose Boot.img
Yes/No To Flash Zip (useful for flashing modules)
Reboot
Flashing Kernels Though Android(deprecated)
Start KL Android App
Choose Kernel Zip*
Kernel & Ramdisk
Reboot To Recovery --> Flash Modules
Reboot
* For zips to be listed, they must be placed in /sdcard/modules/
* otherwise click browse and happy hunting
Something Went Wrong:
Let say the phone wouldnt boot during kernel update after using the app,
the best solution would be to go back to stock kernel, look at the recovery flashable zips in Extras section,
If none seem to fit, try another custom kernel
if you still had no luck booting, you should try flashing that kernel through fastboot and see if it makes any difference.
Warning!!
Note: All the zips provided are flashable through both The App & Recovery... but I recommend recovery
BUT DON'T FLASH THE KEXEC (KL.Zeus.img) KERNEL THROUGH THE APP or Recovery,
as it will continuously boot itself over and over and over again.
Download Link In Post Below
Downloads
Kexec Kernel: KL.Zeus.img(CM12 Based)(V10)(Old Layout Only)
Kexec Kernel: KL.Zeus.img(CM12 Based)(v11)(New Layout Only)
Android App: KernelLighter.apk(No longer in active development, use the Recovery App instead)
Recovery App: AromaFM-KL Flasher(v4.1)(ZeusKL v9- only)
Recovery App: AromaFM-KL Flasher(4.6)(ZeusKL v10+ only)
Extras(deprecated)
Sense 5 Stock Kernel(Works on Sense 4+)(courtesy of LlabTooFeR) flash via recovery
ASOP/CM10.1(Android 4.1.2/4.2.2) flash via recovery
ASOP/CM10.2(Android 4.3) flash via recovery
Archieve
Multirom
ZeusKL
Thunder07 said:
& Another One.
Click to expand...
Click to collapse
Can't wait to try, sound incredible
Awesome! Looking forward to try it.
Sent from my Nexus 7 using Tapatalk 4
Someone tried it?
Never again without Sense 5! *~* <3
This i call development, thanks for that solution.
TouchscreenLover1 said:
Someone tried it?
Never again without Sense 5! *~* <3
Click to expand...
Click to collapse
i made a small typo in one of the files..
after flashing zip
do this
adb shell
mount /data -o rw
echo /data/boot/Kernels/Stock/boot.img-zImage>/data/boot/kernel
echo /data/boot/Kernels/Stock/boot.img-ramdisk.gz>/data/boot/ramdisk
Will Fix Zip soon
Edit: FIXED
Dexxmor said:
This i call development, thanks for that solution.
Click to expand...
Click to collapse
Anyone a Sense 5 Kernel.zip? Kexec boots a descriptet, will try this solution.
Dexxmor said:
Anyone a Sense 5 Kernel.zip? Kexec boots a descriptet, will try this solution.
Click to expand...
Click to collapse
this works on both sense 5 and 4+
i had this running for almost a week now on sense 4+
and just moved to sense 5 and thought it will be a good time to release this.
The Stock kernel comes from sense 5 ROM
I know, but back to 4.1.1 is not a solution for me (Sense 5 is the dealbreaker with AOSP ROMs )
Another Question, if i change to AOSP, it will work too? or must we flash (an not realeased) Kexec AOSP kernel? (i ask not for me, i ask for everyone on AOSP with ORD xD )
Dexxmor said:
I know, but back to 4.1.1 is not a solution for me (Sense 5 is the dealbreaker with AOSP ROMs )
Another Question, if i change to AOSP, it will work too? or must we flash (an not realeased) Kexec AOSP kernel? (i ask not for me, i ask for everyone on AOSP with ORD xD )
Click to expand...
Click to collapse
you dont have to go back to 4.1.1, this will work with sense 5 rom
if you want to use AOSP you must follow the custom kernel guide.
Ahh, (my english is bad..) i think we misunderstand each other, i asked for an Sense 5 kernel.zip to try your "Flash kernel in Recovery" Solution, it exists not so many Kernel.zip with the "Flash Kernel Script" to flash the kernel in recovery... I hope its clear what i mean
this wiil be work on maximus 21 ?
Yes
Dexxmor said:
Ahh, (my english is bad..) i think we misunderstand each other, i asked for an Sense 5 kernel.zip to try your "Flash kernel in Recovery" Solution, it exists not so many Kernel.zip with the "Flash Kernel Script" to flash the kernel in recovery... I hope its clear what i mean
Click to expand...
Click to collapse
im not 100% sure, but if you're looking for the zip, its in the 2nd post
the 1st time you must flash the kernel through fastboot AND zip through recovery,
later i will make an app that will work to replace kernels.
but even that all will require 1 flash through fastboot.
NOTE:
the zip contains to kernel, one that you flash in fastboot
one that will be copied to /data/boot/
the 1st is kexec which will boot the one in /data/boot/
Not clear enough xD, this (the kernel.zip) was not a request to you, it was an request to somebody to make me a flashable kernel zip, as an example repacked Alex-V kernel for Sense 5, to test this.
Its late here, so my explanation will suffer, sorry for that.
Dexxmor said:
Not clear enough xD, this (the kernel.zip) was not a request to you, it was an request to somebody to make me a flashable kernel zip, as an example repacked Alex-V kernel for Sense 5, to test this.
Its late here, so my explanation will suffer, sorry for that.
Click to expand...
Click to collapse
ok that was clear enough,
so far as far as i hear,
only trips kernel work with sense 5
Thanks, sorry for my poor english.
---------- Post added at 11:31 PM ---------- Previous post was at 11:18 PM ----------
EDIT: Now we can flash kernel without a PC, testet and it worked.
So, we can flash kernels through the rom itself by replacing boot.img in data/boot and reboot, can't we ?
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
WARNING #1: CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
USEFUL LINK OF TW ROMS:
http://forum.xda-developers.com/showthread.php?t=2616221
CURRENT PROJECT STATUS:
v3.72 (NB1): Beta testing, no rom-slots
v3.71 (MK2): Debugging some rom-slot issues
v3.65 (TW4.2): Stable
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
[v3.72] ROM-SLOTs aren't supported yet
[v3.72] "Reboot Recovery" doesn't work in the APK?
NEW TO v3.72:
TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.
ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S4 (NOT THE ACTIVE MODEL)
MAKE SURE IF YOU ARE UPGRADING TO v3.7x FROM v3.65 THAT YOU USE THE "UNINSTALL RECOVERY" BUTTON IN THE v3.65 APK BEFORE INSTALLING v3.7x.
NOTE: USE ONLY ROMS THAT MATCH UP WITH YOUR TOUCHWIZ VERSION. IF YOU'RE ON MK2 THEN ONLY USE ROMS BASED ON MK2 AND IF YOU'RE ON MF3 ONLY USE ROMS BASED ON MF3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
FOR USERS OF NB1:
USE 3.72+:BETA Safestrap-JFLTE-3.72.apk (updated 2014-04-02)
FOR USERS OF MK2:
USE 3.71+:BETA Safestrap-JFLTEATT-3.71.apk (updated 2013-12-27)
FOR USERS OF MF3 (TW4.2):
LATEST FILE: Safestrap-JFLTEATT-3.65.apk (updated 2013-11-15)
Main XDA Downloads Page
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
ALSO DOWNLOAD THE KERNEL MODULES .ZIP THAT MATCHES YOUR BUILD # (FLASH THIS AFTER ROMS):
MF3: http://forum.xda-developers.com/devdb/project/dl/?id=508
MK2: http://forum.xda-developers.com/devdb/project/dl/?id=3275
HOW TO MANUALLY REMOVE SAFESTRAP:
[ INSTRUCTIONS ONLY FOR PRIOR TO v3.65. REMOVE VIA APK FOR v3.70+ ]
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
This thread is a development ONLY thread.
For discussion go here:
http://forum.xda-developers.com/showthread.php?t=2428254
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.72 (KK), a Tool/Utility for the AT&T Samsung Galaxy S 4
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.71
Stable Release Date: 2013-12-27
Current Beta Version: 3.72
Beta Release Date: 2014-04-02
Created 2013-09-18
Last Updated 2014-04-02
Reserved
KNOWN ISSUES:
Bluetooth remote control isn't working on rom-slots.
CHANGELOG:
[2013/11/13] TWRP updates
[2013/11/13] "toolbox" binary / symlinks in recovery fixed
[2013/11/11] Uninstall from the APK fixed
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes
Reserved
KNOWN ROM INSTALL / ISSUES:
All TW-based ROMs. If you don't have wifi make sure to flash the kernel modules for your stock kernel version.
Looks promising,
Thanks
Sent from my GT-I9505G using XDA Premium HD app
Add the MF3 kernel module .zip to the "Downloads" section.
http://forum.xda-developers.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
Thank you so much hash!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
An at&t thread. Yes! andyfredrick
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hashcode said:
Add the MF3 kernel module .zip to the "Downloads" section.
http://forum.xda-developers.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
Click to expand...
Click to collapse
WIFI WORKS!!!!!!!! and so does everything else...
Hash can i backup my stock rom to the external sd card and than delete it so i get my 10gigs back? is that safe?
hope this helps out some people!!.. nice job man!! :good:
Just install gpe wifi gps work! i also went back to stock rom and everything worked perfect
Andrew149 said:
WIFI WORKS!!!!!!!! and so does everything else...
Hash can i backup my stock rom to the external sd card and than delete it so i get my 10gigs back? is that safe?
Click to expand...
Click to collapse
God , no!
Sent from my SPH-L720 using XDA Premium 4 mobile app
rebel1699 said:
God , no!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well that sucks! i hate having only 3gigs of user space =[
Graviton Rom works on SS... no issues at the moment ...what else are other users using?
---------- Post added at 07:12 AM ---------- Previous post was at 06:51 AM ----------
Can I flash performance mods zips only on slot 1 like killjoy or flyon mod etc? Or no because the stock kernel doesn't have init.d support?
Edit: as long as you flash to slot 1-4 everything will be safe. .. currently using darth stalker rom and that has init.d support, no issues at the moment.
HI
sykoj82 said:
Graviton Rom works on SS... no issues at the moment ...what else are other users using?
---------- Post added at 07:12 AM ---------- Previous post was at 06:51 AM ----------
Can I flash performance mods zips only on slot 1 like killjoy or flyon mod etc? Or no because the stock kernel doesn't have init.d support?
Click to expand...
Click to collapse
HELLO GREETINGS GUYS, GREAT JOB, I HAVE A DOUBT REGARDING THE SAFE ROMS SUPPORT STRAPS, AND ROM VERSIONS
1 - VERSION 4.3 SUPPORT? SS
2 - VERSION 4.2.2 SUPPORT? ROMS SUPPORT IS SS
3-THEME CAN FLASH MOD, ECT ..,?
* FINALLY HAVE MANY ROM Pacht LOKI LOKI IS DEVE install AFTER THE ROM OR NOT ONLY THE MODULE MF3? SORRY FOR MY ENGLISH I AM USING GOOGLE TRANSLATOR .. THANKS ..
HOLA CHICOS SALUDOS ,,GRAN TRABAJO,TENGO UNA DUDA EN CUANTO LOS ROMS SOPORTE PARA SAFE STRAPS,Y VERSIONES DE ROM
1- 4.3 VERSION SOPPORTE?SS
2- 4.2.2 VERSION SOPPORTE?SS CUAL ROMS SOPORTE
3-SE PUEDE FLASHEAR MOD THEME, ECT..,?
POR ULTIMO MUCHOS ROM TIENE LOKI PACHT SE DEVE INTALAR EL LOKI DESPUES DEL ROM O NO SOLAMENTE EL MODULO MF3 ? DISCULPEN POR MI INGLES ESTOY USANDO GOOGLE TRADUCTOR..GRACIAS..
So I've searched and searched, but can't seem to find a clear answer and I want to make sure of this before I try.
My "stock" ROMs are always CM-based 4.3 ROMs (haven't used TW in awhile). I got my S4 when it was still MDL so my qfuse isn't blown - so my intended use for this is only for the additional ROM slots. I have gathered that, at least for now, the only ROMs we can flash to the additional slots have to be TW or GPE 4.2.2. But my question is, does my primary ROM also have to meet that description? Or can I keep my 4.3 AOSP ROM as my primary?
AT&T Error
Hello,
I flashed the GEP rom to Rom Slot 1 and now I am getting an error that says Kernel Fail; System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help. There is a yellow triangle.
I followed the instructions, but now have a hosed phone unless I can somehow restore the backup of my stock rom.
Any information would be helpful.
Thanks for your efforts.
dtruong23 said:
Hello,
I flashed the GEP rom to Rom Slot 1 and now I am getting an error that says Kernel Fail; System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help. There is a yellow triangle.
I followed the instructions, but now have a hosed phone unless I can somehow restore the backup of my stock rom.
Any information would be helpful.
Thanks for your efforts.
Click to expand...
Click to collapse
Oh no...I hope I don't see that. I wish you luck! Was your phone encrypted to begin with?
Does anybody know why it would say this? Now I'm hesitant to flash anymore roms.
sykoj82 said:
Oh no...I hope I don't see that. I wish you luck! Was your phone encrypted to begin with?
Click to expand...
Click to collapse
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
dtruong23 said:
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
Click to expand...
Click to collapse
Wow...so far I flashed 2 different roms...I haven't tried the one you flashed...good luck to u... I'm definitely scared to flash any more roms...but you are 100% positive slot 1 was activated before flashing right? Thats the only thing I can think of that "stock" was activated..
dtruong23 said:
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
Click to expand...
Click to collapse
What GPE rom did u flash?? did u flash the kernel module zip??
Hi, this is United Oxygen team.
We were specially working for MultiROM for a long while, and finally, it is almost finished, so we are proud to show up this project to you.
- DOWNLOAD -
@ MultiROM TWRP
- For F220K (Optimus GK)
http://drive.google.com/file/d/0BwF2VxTC-s7_RG10ZTMxWDBMVFk/view?usp=sharing
- For F240 (Korea Optimus G Pro)
http://drive.google.com/file/d/0BwF2VxTC-s7_U1Y1SDUxX09KMms/view?usp=sharing
- For E980 (Intl Optimus G Pro)
http://drive.google.com/file/d/0BwF2VxTC-s7_SE5Fc0VpN0dTYU0/view?usp=sharing
@ MultiROM
http://copy.com/7eCxh7k6f8x7o6LG
Please download all 3 files!
- Caution -
1. YOU SHOULD USE kexec-hardboot SUPPORTED KERNEL IN PRIMARY(STOCK) SLOT! United Oxygen will support kexec in Oxygen Kernel 2.0. Otherwise, you should check whether that kernel supports kexec.
2. In Secondary slots (MultiROM slots), you can install any ROMs, even if it doesn't support kexec-hardboot. It means, you have to install kexec-supported ROM in Original System Partition, and after that, you are free to install any ROM in MultiROM.
-How to install MultiROM-
0.Reboot to custom recovery, and install kexec supported ROM or Kernel like our Oxygen Kernel 2.0. We've already shown our ROMs in other threads.)
1. Install MultiROM TWRP in other recoveries.
2. Reboot recovery, and you will be in MultiROM TWRP.
3. Flash 'MultiROM-~~~-e980.zip'.
4. (Recommended) Reboot recovery once again.
5. Go to Advanced - MultiROM -Add ROM - Install your favorite ROMs to Secondary slots.
6. Reboot system, and you can choose ROMs that you want to boot in bootmenu.
- Must-Know about MultiROM -
Q. Bootmenu does not appear. What should I do?
A. I think you upgraded or changed the kernel. If you upgraded the kernel, please flash 'MultiROM-injectboot.zip' in MultiROM TWRP.
Or, if you deleted MultiROM data, please flash 'MultiROM-~~~-e980.zip' once again.
Q. I want to delete MultiROM.
A. Flash 'MultiROM-uninstaller.zip'.
Q. ADB Sideload not works in TWRP Recovery.
A. It is a bug...We will try to fix it soon.
Oh, it's there already. Thanks.
Oh God, can't believe it! Thanks A LOT Oxygen Team! This will save a loooot of time for flashing
This is a very great addition to the G PRO community. Anyone test this then report?
This thread is keep being written. Please don't follow this yet.
victor19 said:
Oh God, can't believe it! Thanks A LOT Oxygen Team! This will save a loooot of time for flashing
Click to expand...
Click to collapse
MitoTakatori said:
This is a very great addition to the G PRO community. Anyone test this then report?
Click to expand...
Click to collapse
I'm writting again, please wait.
======Finished!======
Genie's said:
I'm writting again, please wait.
======Finished!======
Click to expand...
Click to collapse
I am so excited to try this and I have some questions!
So, there is a kexec kernel for CM 12.1 and for Blisspop 3.2, so to be able to use this MultiROM I am going to need to flash either CM 12.1 or Blisspop 3.2 and their respective kexec kernel right? And that would be my primary ROM, then after that I can flash my stock ROM(or any ROM of my liking) and serve as my secondary ROM. Did I get that right?
[email protected] said:
I am so excited to try this and I have some questions!
So, there is a kexec kernel for CM 12.1 and for Blisspop 3.2, so to be able to use this MultiROM I am going to need to flash either CM 12.1 or Blisspop 3.2 and their respective kexec kernel right? And that would be my primary ROM, then after that I can flash my stock ROM(or any ROM of my liking) and serve as my secondary ROM. Did I get that right?
Click to expand...
Click to collapse
1. Yeah. You just need to install our Oxygen Kernel 2.0-contained ROMs or ROM with other custom kernels that supports kexec.
2. Yeah...maybe? We didn't test stock in secondary slot, but I think it may work.
I recommend these to E980 users:
Install our Oxygen Kernel 2.0-contained ROMs based on F240 in E980's primary slot. Some functions will not work maybe, but you can use MultiROM. (Tested.)
Any one test Twrp recovery for e980
On Adding a secondary ROM, there are details on that part, can you detail what to choose? I am trying to flash a secondary ROM, but I don't know what to do on that part.
There are options there whether the ROM is android or multirom (.rmm)?, then where to install, whether internal, or on the other 2 options. Can you please elaborate on those parts?
Thanks.
@Genie's
MitoTakatori said:
On Adding a secondary ROM, there are details on that part, can you detail what to choose? I am trying to flash a secondary ROM, but I don't know what to do on that part.
There are options there whether the ROM is android or multirom (.rmm)?, then where to install, whether internal, or on the other 2 options. Can you please elaborate on those parts?
Thanks.
@Genie's
Click to expand...
Click to collapse
There's no limits in installing ROMs in Secondary slots. Just install anything you just want to flash.
But you should install kexec-supported ROM or Kernel in just Primary Slot.
We are now tring to support E980.
Please go to my threads that contains ROM with Oxygen Kernel V2.0, download E980 version and test ROM and whether MultiROM is supported or not.
If you install this ROM in Primary Slot, please enter this adb command to know us what E980's kexec code is. :
adb shell
su
dmesg | grep -i hardboot
Genie's said:
There's no limits in installing ROMs in Secondary slots. Just install anything you just want to flash.
But you should install kexec-supported ROM or Kernel in just Primary Slot.
Click to expand...
Click to collapse
Currently I have BP 3.2 installed on Internal slot, then I want to install another ROM for the secondary slot, where to install it? There are 3 options on the multirom menu
Use 'Add ROM' Menu to install in secondary slot.
Genie's said:
Use 'Add ROM' Menu to install in secondary slot.
Click to expand...
Click to collapse
So, I will install on the second slot? Not on the Internal slot?
I will explain shortly :
Primary Slot, means Original System Partition : Kexec-Supported ROMs, like our Oxygen Kernel 2.0 contained ROM.
Secondary Slot, means Internal Memory : Any ROM you want. (But our testers said Stock ROM would not work, maybe.)
@saxsymbol succeeded installing MultiROM in E980 with our Oxygen Kernel 2.0 ROMs for E980!
E980 users should use our ROMs in Primary Slot if you are having trouble in installing MultiROM.
Genie's said:
I will explain shortly :
Primary Slot, means Original System Partition : Kexec-Supported ROMs, like our Oxygen Kernel 2.0 contained ROM.
Secondary Slot, means Internal Memory : Any ROM you want. (But our testers said Stock ROM would not work, maybe.)
Click to expand...
Click to collapse
I am still a bit confused. Sorry. If you can post SS of the MultiROM menu, and step by step guide, maybe I will understand it. Thanks by the way.
Hi all,
Seems there is a CM14.1 nightly now available for find7s on the official CM site, link here: hxxps://download.cyanogenmod.org/?type=nightly&device=find7s
Was just wondering if anyones given it a go yet, and if so knows whether or not it supports LVM and how stable the rom is?
Haven't found any info that states one way or the other, hoping someone knows.
Thanks in advance.
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Its a little bit weird that there is not available yet on the page https://www.cmxlog.com/14.1/
Hope it will appear here soon as well as it is already here:
(Find 7a) https://download.cyanogenmod.org/?device=find7
and
(Find 7) https://download.cyanogenmod.org/?device=find7s
Dirty flashed cm-14.1-20161205-NIGHTLY over cm-14.1-20161201-UNOFFICIAL via menu CyanogenMod updates. Everything seems to be OK. One remark: boot time when update is completed is quite long, so be patient. Of course in order to not see "SD corrupted" it is necessary to flash cm-13.0-find7-unified-storage-patch.zip
EDIT: Just for your information: boot animation CM face is gone. Now there is word "android" in plain white.
great news
Finally there we are changes logs:
https://www.cmxlog.com/14.1/find7/
https://www.cmxlog.com/14.1/find7s/
Android 7.1.1 in the next nightly
CyanogenMod will never support LVM.
This is 7.1 right? Or is it 7.0? I downloaded the 7.1 GAPPS, which should be correct for this build...
I updated it, and it runs smooth without any force crashes and nonsense. (Besides the time I tried to open an app not built for nougat, =P. If you're hesistant about updating, don't think, just do it.
Injected said:
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Click to expand...
Click to collapse
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
-lorenzo- said:
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
Click to expand...
Click to collapse
Yup u can do that. After flashing cm14.1 official, u might wanted to flash cm13 patch by wuxianlin, then flash the gapps and lastly wipe the cache and dalvik
-lorenzo- said:
i want to upgrade from an existing cm 13 installation, it is alredy unified with the chinese method, did you made a clean installation? what about the need of flashing Wuxianlin's patch after every upgrade? thanks in advice
Click to expand...
Click to collapse
And yes you need to flash Wuxianlin's patch after every upgrade just for aesthetic purpose, that is to fix the SDcard damage info bug, unless CM find7 maintainer will fix that, and when it happen you will no longer need to flash the Wuxianlin's CM13 patch.
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Yashraj Chawla said:
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Click to expand...
Click to collapse
1. If you are on LVM you need to back to stock partition layout. Just google for "Find 7 unbrick tool" for procedure. "Sahara" tool is available for download here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
2. Setup Chinese partition layout: http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
3. Flash wuxianlin's version of TWRP: link available under point 10. on http://community.oppo.com/en/thread-47844-1-1.html
4. Flash cm-14.1 last official nightly build: https://www.cmxlog.com/14.1/find7/
5. Flash nano open gaaps
6. Flash SU
7. Flash cm-13.0-find7-unified-storage-patch
8. Enjoy newest, very stable and fast Android 7.1.1.
Yashraj Chawla said:
I am on crdroid right now (LVM) and i really want to try this. Please tell me in short how to revert back to stock partition and then flash this.
Click to expand...
Click to collapse
rafal.polska.b said:
1. If you are on LVM you need to back to stock partition layout. Just google for "Find 7 unbrick tool" for procedure. "Sahara" tool is available for download here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
2. Setup Chinese partition layout: http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
3. Flash wuxianlin's version of TWRP: link available under point 10. on http://community.oppo.com/en/thread-47844-1-1.html
4. Flash cm-14.1 last official nightly build: https://www.cmxlog.com/14.1/find7/
5. Flash nano open gaaps
6. Flash SU
7. Flash cm-13.0-find7-unified-storage-patch
8. Enjoy newest, very stable and fast Android 7.1.1.
Click to expand...
Click to collapse
OMG! No! Just need to flash "unlvm" script to revert to stock layout, that is supported by this ROM. Then flash ROM, gapps and SuperSU.
Anyway, to configure chinese storage, if desired, step 1 is unnecesary: just step 2 is enough.
And, of course, don't forget to make a backup in external SD because any choosen method (unbrick tool, setup chinese storage or revert LVM) erases both data and internal card.
Edit:
Here you can find the removelvm_find7_FULL_WIPE script needed to revert to stock layout; flashing it from TWRP is the only you need. When in stock again, you can proceed as usual flashing ROM, gapps and everything you want.
DELETE
Thanks everyone for the info, might hold off as I have LVM, here's hoping that namelessrom put out an official nougat rom in the not too distant future.
New Display is not supported
Injected said:
About the storage support:
Stock -> YES
LVM - NO
Coldbird - Not tested
Chinese - YES
New display:
Cant test it because i havent the new display
At the moment no theme engine
Is stable for daily driver FROM MY POINT OF VIEW
Click to expand...
Click to collapse
New Display is not supported. Colors, ghosting, and bleeding will still be running wild just like all older CM.
The only Custom ROM on the planet that fully supports new display is OmniROM and it seems that they could use some help. Please support their effort: omnirom.org
javier.pc said:
OMG! No! Just need to flash "unlvm" script to revert to stock layout, that is supported by this ROM. Then flash ROM, gapps and SuperSU.
Anyway, to configure chinese storage, if desired, step 1 is unnecesary: just step 2 is enough.
And, of course, don't forget to make a backup in external SD because any choosen method (unbrick tool, setup chinese storage or revert LVM) erases both data and internal card.
Edit:
Here you can find the removelvm_find7_FULL_WIPE script needed to revert to stock layout; flashing it from TWRP is the only you need. When in stock again, you can proceed as usual flashing ROM, gapps and everything you want.
Click to expand...
Click to collapse
Thank you guys i just did that and i must say CM - 14.1 is Lovely :good:
Yashraj Chawla said:
Thank you guys i just did that and i must say CM - 14.1 is Lovely :good:
Click to expand...
Click to collapse
It is. But omnirom support substratum theme.
StormTrooper89 said:
It is. But omnirom support substratum theme.
Click to expand...
Click to collapse
I think you can install substratum theme in CM14.1 (but only substratum themes that support Android 7.1.1), since there no theme engine inside CM14.1