MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices.
★ Disclaimer:
This service is FREE of charge, use it at your own risk, take it or leave it !
Click to expand...
Click to collapse
THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. USE AT YOUR OWN RISK!
Click to expand...
Click to collapse
MultiSystem is a powerful tool and can perform potentially dangerous and/or destructive operations on your device and data that may affect your life. While it is unlikely to do irreversable damage to your device, it is not impossible, and you should proceed with caution. Loss of data and/or the need to re-flash a full stock (manufacturer-supplied) firmware IMGs (usually requiring a computer) is always a possibility, and is increasingly likely if you do not know what you are doing. It is possible to lose root access when using MultiSystem on locked-bootloader devices running unexpoitable (bu rooted) Android firmware, without careful reading of documentation or following the instructions. Please consult with expert users before performing actions you do not comprehend.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Notes:
To devs: Please do not use/port MultiSystem to any other device. If you'd like to add support for your device, please contact me!
Click to expand...
Click to collapse
To users: This thread is only for DEVELOPMENT. If you need a place for general discussions, go to MultiSystem Q&A thread.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
★ Features:
Keeps stock system partition safe/rooted
Permenant root survival with proper use
MultiROM support via virtual ROMs
Unlimited number of virtual ROMs
Booting options to choose stock, primary, or secondary virtual ROM
Any of the virtual ROMs can work as a recovery replacement
Flashing multiple ROMs at the same time without a reboot
Ability to create/install ROMs on Linux to microSD card
Great performance & battery life on virtual ROMs
Recovery solution to install ROMs or Mods
Easy upgrade to newer versions of Android
Ability to safely apply OTA updates to virtual system
Permissive SELinux and other kernel tweaks
Safe flashing that doesn't trip KNOX flag on Samsung devices
Wrapper script runs via ADB or a Terminal Emulator on device
APK to manage all MultiSystem functions with a nice UI and extra options
Management for the best performance & user experience
Support for all Android devices with microSD card
Portability to almost all devices
Compatibility with all Android versions
Click to expand...
Click to collapse
★ ChangeLog:
Check the updated changelog in the main development thread!
Click to expand...
Click to collapse
★ Instructions:
Check the updated instructions in the main development thread!
Click to expand...
Click to collapse
★ Downloads:
Download the latest version from the main development thread!
Click to expand...
Click to collapse
★ Credits:
@ChainFire - for SuperSU & FlashFire
@Hashcode - for Safestrap Recovery
@[NUT] - for XZDualRecovery
@Androguide.fr - for APKreator & various libraries/apps
Jack Palevich - for Terminal Emulator for Android
@osm0sis - for Android Image Kitchen
All authors of binaries/libraries, source codes, or tutorials...
Please PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'd like to thank everyone who made a donation just to show appreciation.
It's fine to just click Thanks! or enjoy my work without saying anything.
A donation is to show appreciation of the work I have done already.
A donation is not by any means in expectation of future work.
A donation doesn't entitle for preferred/private support/requests.
A donation is meant as a gift - always appreciated, never required.
Click to expand...
Click to collapse
Verizon Samsung Galaxy Note 4 (N910V), Note 3 (N900V) & LG G3 (VS985)
Hit thanks, follow thread & add 5-star rating/review... Donations are always appreciated!
XDA:DevDB Information
MultiSystem, Tool/Utility for the AT&T Samsung Galaxy Note 3
Contributors
hsbadr
Source Code: https://github.com/hsbadr/MultiSystem
Version Information
Status: Testing
Current Stable Version: 1.3.1
Stable Release Date: 2015-05-09
Current Beta Version: 1.1.2
Beta Release Date: 2015-05-03
Created 2015-05-04
Last Updated 2015-05-10
Supported Devices
Samsung Devices
Samsung Galaxy Note 3
Samsung Galaxy Note 3 - Verizon Variant [Retail Edition]
Samsung Galaxy Note 3 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 3 - AT&T Variant
Samsung Galaxy Note 3 - T-Mobile Variant
Samsung Galaxy Note 3 - Sprint Variant
Samsung Galaxy Note 3 - International Variant
Samsung Galaxy Note 4
Samsung Galaxy Note 4 - Verizon Variant [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - Verizon Variant [Developer Edition]
Samsung Galaxy Note 4 - Verizon Varian [Retail Edition] (ROOT Required!)
Samsung Galaxy Note 4 - AT&T Variant (ROOT Required!)
Samsung Galaxy Note 4 - T-Mobile Variant
Samsung Galaxy Note 4 - Sprint Variant
Samsung Galaxy Note 4 - International Variant
Samsung Galaxy S4
Samsung Galaxy S4 - Verizon Variant
Samsung Galaxy S4 - AT&T Variant
Samsung Galaxy S4 - T-Mobile Variant
Samsung Galaxy S4 - Sprint Variant
Samsung Galaxy S4 - International Variant
Samsung Galaxy S5
Samsung Galaxy S5 - Verizon Variant
Samsung Galaxy S5 - AT&T Variant
Samsung Galaxy S5 - T-Mobile Variant
Samsung Galaxy S5 - Sprint Variant
Samsung Galaxy S5 - International Variant
Click to expand...
Click to collapse
LG Devices
LG G3
LG G3 VS985 - Verizon Variant (Under Testing + more features utilizing Bump!)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+++
Reserved #2
Reserved #3
Reserved #4
Reserved #5
@hsbadr
If this doesn't get affected by the locked bootloader, does it mean that you can flash AOSP ROMs on our phone with it? I know kernels are different, but maybe you have something else in mind. Sounds like a pretty interesting tool. Thank you.
From my Allianced Note 3!
K-alz said:
@hsbadr
If this doesn't get affected by the locked bootloader, does it mean that you can flash AOSP ROMs on our phone with it?
Click to expand...
Click to collapse
It depends on the stock kernel though. So you can't flash AOSP ROMs for now (I've something in mind but not achieved yet: simply 2nd-init hijack of the kernel ramdisk. However, there's no promise that this could be achieved anytime soon). MultiSystem will allow you to run multiple virtual systems keeping your physical system partition safe & enjoying the freedom of swapping systems on the fly (say you've 3 virtual system IMG: flash a ROM to one of them; if something went wrong, use the boot options to boot the stock system or a secondary virtual IMG). Also, system backups now can be just a copy/paste of system IMGs & if you've Linux skills, you'll be able to insert a new microSD to your Linux machine & install/copy/modify virtual system IMGs as you wish & any of them is ready to boot when you insert it into the device & activate primary & secondary ROMs. For more detail, check the features in OP & Q&A section.
hsbadr said:
It depends on the stock kernel though. So you can't flash AOSP ROMs for now (I've something in mind but not achieved yet: simply 2nd-init hijack of the kernel ramdisk. However, there's no promise that this could be achieved anytime soon). MultiSystem will allow you to run multiple virtual systems keeping your physical system partition safe & enjoying the freedom of swapping systems on the fly (say you've 3 virtual system IMG: flash a ROM to one of them; if something went wrong, use the boot options to boot the stock system or a secondary virtual IMG). Also, system backups now can be just a copy/paste of system IMGs & if you've Linux skills, you'll be able to insert a new microSD to your Linux machine & install/copy/modify virtual system IMGs as you wish & any of them is ready to boot when you insert it into the device & activate primary & secondary ROMs. For more detail, check the features in OP & Q&A section.
Click to expand...
Click to collapse
Sounds very interesting. if you ever need a tester for an AOSP project, just hit me up.
is it, in some way, close to the safestrap concept? Except this one has more options to it?
K-alz said:
Sounds very interesting. if you ever need a tester for an AOSP project, just hit me up.
is it, in some way, close to the safestrap concept? Except this one has more options to it?
Click to expand...
Click to collapse
All 2nd-init recovery hijacks kernel at early boot & so, they've similar hijack methods but probably diffrent binaries or hijack scripts. There're many diffrences in the operation that you could easily notice by reading the Q&A section. MultiSystem is designed to be independet on device nor the OS version. I've tester's success on VZW S4 & ATT Note 3 for both LP & KK.
As for ramdisk hijack, this may be a long wait, since I need to deliver the main functions to almost all devices before adding time-consuming features.
hsbadr said:
All 2nd-init recovery hijacks kernel at early boot & so, they've similar hijack methods but probably diffrent binaries or hijack scripts. There're many diffrences in the operation that you could easily notice by reading the Q&A section. MultiSystem is designed to be independet on device nor the OS version. I've tester's success on VZW S4 & ATT Note 3 for both LP & KK.
As for ramdisk hijack, this may be a long wait, since I need to deliver the main functions to almost all devices before adding time-consuming features.
Click to expand...
Click to collapse
I like how you made the tool independent on the device not the OS. That opens up a whole new level of usability for so many devices. You're good to go as long as you got root.
So, if I'm on a lollipop rom (on my note 3) and wanted to switch to another rom or just have to lollipop ROMs at once, Multisystem helps me get that. Sorry for asking a lot. Just trying to understand.
BTW, I read the whole thread.
K-alz said:
I like how you made the tool independent on the device not the OS. That opens up a whole new level of usability for so many devices. You're good to go as long as you got root.
So, if I'm on a lollipop rom (on my note 3) and wanted to switch to another rom or just have to lollipop ROMs at once, Multisystem helps me get that. Sorry for asking a lot. Just trying to understand.
BTW, I read the whole thread.
Click to expand...
Click to collapse
You always need to run a virtual ROM supported by your current firmware/kernel. Always make data backup, b/c it's shared between all ROMs for performance/battery & to avoid splitting your data/messages/contacts/etc between different ROMs. So, you'll have only one recent backup of your data, in case you run a completely diffrent ROM that doesn't like your data (hence, wipe data & restore what you want from the shared backup).
hsbadr said:
You always need to run a virtual ROM supported by your current firmware/kernel. Always make data backup, b/c it's shared between all ROMs for performance/battery & to avoid splitting your data/messages/contacts/etc between different ROMs. So, you'll have only one recent backup of your data, in case you run a completely diffrent ROM that doesn't like your data (hence, wipe data & restore what you want from the shared backup).
Click to expand...
Click to collapse
Makes sense.
I'm asking because I wanted to know if this tool could be used as a "custom recovery" while on a lollipop rom just in case I wanted to flash something. And you know that SS doesn't work with LP and we are using a workaround to get to it every time we need to get to the recovery.
K-alz said:
Makes sense.
I'm asking because I wanted to know if this tool could be used as a "custom recovery" while on a lollipop rom just in case I wanted to flash something. And you know that SS doesn't work with LP and we are using a workaround to get to it every time we need to get to the recovery.
Click to expand...
Click to collapse
As the tite says, it's "MultiROM and Recovery Replacement". Yes, you can flah ZIP files to your stock system, current virtual system, or any of your IMGs. This can be done via MultiSystem Flash function or using FlashFire, which is 100% supprted by MultiSystem virtual ROMs. However, as stated in the Q&A OP, the updater-script shouldn't mount the physical system partition to /system when flashing to a virtual ROM (A minor edit in the updater-script is required).
hsbadr said:
As the tite says, it's "MultiROM and Recovery Replacement". Yes, you can flah ZIP files to your stock system, current virtual system, or any of your IMGs. This can be done via MultiSystem Flash function or using FlashFire, which is 100% supprted by MultiSystem virtual ROMs. However, as stated in the Q&A OP, the updater-script shouldn't mount the physical system partition to /system when flashing to a virtual ROM (A minor edit in the updater-script is required).
Click to expand...
Click to collapse
When are you planning on putting the tool out for public? I see "under testing" in OP. Is there a specific reason for waiting? Just curious. Because this would be very helpful for other devs who want to build LP ROMs since they've been waiting for some work to be done on SS to work with LP (I know we have the workaround but a proper way is always preferred).
K-alz said:
When are you planning on putting the tool out for public? I see "under testing" in OP. Is there a specific reason for waiting? Just curious. Because this would be very helpful for other devs who want to build LP ROMs since they've been waiting for some work to be done on SS to work with LP (I know we have the workaround but a proper way is always preferred).
Click to expand...
Click to collapse
I'm working on a new version with bug fixes & S4/S5 support while @carl1961 is testing the current version. When he reports all issues on N900A & I fix them, it'll be immediately released.
hsbadr said:
I'm working on a new version with bug fixes & S4/S5 support while @carl1961 is testing the current version. When he reports all issues on N900A & I fix them, it'll be immediately released.
Click to expand...
Click to collapse
Thank you very much, sir
As I've mentioned before, if you need a tester I'm always ready to jump in. My note isn't my daily driver, so I can f^ck it up with no problem as long as it is recoverable.
K-alz said:
Thank you very much, sir
As I've mentioned before, if you need a tester I'm always ready to jump in. My note isn't my daily driver, so I can f^ck it up with no problem as long as it is recoverable.
Click to expand...
Click to collapse
Since the current installation has some issues that makes it a bit complicated, I'd recommend for you to wait for the new version with one-step installation of all MultiSystem components in a flashable .ZIP file.
What hijack do you use for SM-N900A? safestrap just replaced e2fsck
And can you please push the source to github?
benwaffle said:
What hijack do you use for SM-N900A? safestrap just replaced e2fsck
And can you please push the source to github?
Click to expand...
Click to collapse
e2fsck is hijacked by MultiSystem as well. As for the source code, it'll most probably be open & get pushed to this GitHub repo.
Related
For all those who aren't yet ready to upgrade to Lollipop but would like to close this vulnerability on their device, I have built the latest CM11 i9100 source as of 9/1/15 (since CM11 nightlies for this device are no longer released for download). This build is unofficial but I have not modified it in any way**. It includes all StageFright fixes that the CM development team has implemented.
All required downloads are located here.
Works well as a daily driver with Lanchon's i777 Crossflash Kernel on my device.
Installation instructions can be found on CM's website or on Lanchon's kernel thread (above).
I recommend wiping cache/system/data prior to flashing (dirty flash with only a cache wipe did not work on my device when upgrading from the last public nightly).
Good luck!
** I did manually modify the updater-script to allow this ROM to be flashed on any device (because i9100 ROMs refuse to flash on the i777/S959G). Flashing this ROM on anything other than an i9100/i777/S959G WILL brick your device.
XDA:DevDB Information
CyanogenMod 11 [UNOFFICIAL] for i777 with Stagefright Fix, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
dimoochka
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-08-31
Last Updated 2015-08-31
Apparently the crossflash kernel is incompatible with this build (not sure why - was working ok on my device). A compatible version was rebuilt by Lanchon on 9/4/15 (can be found on his thread or in the download link in the first post).
Very considerate, and good of you to take the time to present this. Cheers, and build-on!
-Cyril
Stagefright bug still present
Flashed it yesterday.....all works fine.....except bug isn't fully patched
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
I just started a rebuild. Will try to upload when it's finished tonight - maybe that vulnerability has been patched since the last time I built this (months ago).
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
dimoochka said:
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
Click to expand...
Click to collapse
i just dirty flash it. right?
mmystere68 said:
i just dirty flash it. right?
Click to expand...
Click to collapse
If you're coming from a prior version of CM11 dirty flash should be fine.
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Edgarhighmen said:
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Click to expand...
Click to collapse
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
dimoochka said:
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
Click to expand...
Click to collapse
Thanks dimoochka, i'm probably going to give it a go this weekend.
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Rhaegon said:
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Click to expand...
Click to collapse
Glad this helped! Just so you're aware I haven't rebuilt this ROM for a good 9 months (and I am not even sure if the CM team is still patching old bugs in versions 11/12). If you're unable to get CM13 on the i777, I would definitely suggest buying a newer device for the sake of security. Nexus devices are basically the only option I'm aware of here since none of the other manufacturers actively maintain their ROMs. I retired my i777 in leiu of a Nexus 5X about 6 months ago.
Best of luck!
This rom is a port of the Stock Touchwiz Marshmallow beta build
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
I'm searching for Contributors, if you are interested, please send me a PM
Current Status: Released first Alpha (v0.1a)
Next Release ETA: ~ January 2016
Known Issues:
Stuck On Boot Logo
Click to expand...
Click to collapse
Install Guide:
Download the compressed file
Decompress the file
Reboot phone in download mode
Open the folder called "Odin + flash files"
Open Odin, flash the pit file (i9100-3GB) and the kernel (i9100-kernel)
Copy the continuingM flashable zip file into an sd card
Insert the SD card in the phone
reboot the phone in recovery mode
Wipe data/factory reset
Flash the continuingM Zip
Fix permission
reboot phone
Click to expand...
Click to collapse
Changelog:
v0.1a
Initial Release
Click to expand...
Click to collapse
Downloads:
Alpha 1
Click to expand...
Click to collapse
XDA:DevDB Information
ContinuingM Touchwiz Edition, ROM for the Samsung Galaxy S II
Contributors
firepenguin
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2015-12-29
Last Updated 2015-12-29
Interesting project. Keep it up!
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
firepenguin said:
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
Click to expand...
Click to collapse
hi,
something like this ?
http://forum.xda-developers.com/showpost.php?p=63855358&postcount=122
http://forum.xda-developers.com/showpost.php?p=63854846&postcount=113
wel wel wel... rely intersting project keep up
Interesting,
I am waiting to test your rom.You know if we gonna have this function available ?
Call record
Code:
Voice call uplink + downlink audio source
Constant Value: 4 (0x00000004)
Interesting .......
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
GreekDragon said:
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
Click to expand...
Click to collapse
Yes bro but I guess device needs official marshmallow, Because i don't have much faith in Touchwiz when it comes to updates
And personally i believe stockis better than port in Touchwiz ROMs
Placeholders aren't allowed on XDA.
edi194 said:
Placeholders aren't allowed on XDA.
Click to expand...
Click to collapse
Actually, since this thread is clearly labeled "WIP" this is allowed. Ongoing development.
Thanks for your concern.
The_Merovingian
Forum Moderator
I will test to help development
I'm currently deodexing the dump and removing all arm64 libs/binaries. I think that the first alpha will be ready for the 2nd January
I've done the first build, Now i'm uploading it. It won't boot, it gets stuck on Galaxy SII logo, I don't know why. To flash it you need to repartition the phone. The file i will upload is a 7z file, so you need to decompress it to flash. The file contains odin, the pit file and the rom
Clean CM13 kernel can't boot TouchWiz rom. You need to modify it.
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
firepenguin said:
I've done the first build, It won't boot, it gets stuck on Galaxy SII logo, I don't know why.
Click to expand...
Click to collapse
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
i confirm , no boot , sorry for s2.
I think S2 would be ported on S3 JB 4.3 stock firmware rather than this.
This is almost impossible... 64bit firmware is not compatible with 32bit device.
FaserF said:
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
Click to expand...
Click to collapse
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
PolishVodka said:
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
Click to expand...
Click to collapse
Thank you so much. I will try your method
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.
As the title says, I've got a rooted i545 running 5.0.1 on OF1. I have a new daily driver so I'm wondering what I should do with my s4.
I don't have any 'need' for this phone, so I'm open to ideas. I have a couple of young (3/4) kids that I was thinking of loading it up with kids apps for them. I also thought of keeping it in my car and connecting it to a wireless OBD reader all the time. I'm not locked into either idea.
As it is currently, the phone keeps prompting me every day to update which I really need to get rid of. It looks like OF1 limits what I can do with it (no LineageOS), but I saw that Albe95 S6 FULL PORT 4.7 should work. Is there anything else fun I should consider?
Phoenix ROM, the s6-s7 rom, the new cyanwiz updates which use ports of the nougat frameworks for the next gen appearance.
Viper4android and a plethora of sound mods.
My flash list contains almost 11 different modifications besides the ROM and kernel updates.
ninjasinabag said:
Phoenix ROM, the s6-s7 rom, the new cyanwiz updates which use ports of the nougat frameworks for the next gen appearance.
Viper4android and a plethora of sound mods.
My flash list contains almost 11 different modifications besides the ROM and kernel updates.
Click to expand...
Click to collapse
Sounds great ... will this work with my i545 on OF1? On tdroms I see a build for the i9500 and the i9505; I didn't think I could use their roms interchangeably.
ljer said:
Sounds great ... will this work with my i545 on OF1? On tdroms I see a build for the i9500 and the i9505; I didn't think I could use their roms interchangeably.
Click to expand...
Click to collapse
Some roms will work, just make sure you also flash the relevant kernel files. They're usually provided on the oc1/of1 compatible threads.
This is more or less a copy-paste from the same thread over the s9 section but whatevs. I thought you guys would like this too.
Pixel Experience ROM for the NOTE 9
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Click to expand...
Click to collapse
Semi-GSI? what's that?
a semi-gsi (at least by my own definition) is a gsi built from source, with heavy patches intended for a specific device that wouldn't make the gsi necessarily as universal as a gsi should be. so in terms: don't flash this on other devices.
How does this differ from any other gsis out there/what are the features?
Well this includes a number of fixes including:
Dual speakers are working.
Ui lag is no more (at least 99.99%).
Aod is working/enabled.
Auto brightness is kinda working.
MTP is working
Other performance fixes and improvments.
What's working/not working?
First up:
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS Pixel Experience. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS PixelExperience.
Click to expand...
Click to collapse
2ndly the semi-gsi has a few quirks of it's own. Nothing major or worth noting but you should check the "anything else i should know?" part in the FAQ. hence why HWC is broken
Instructions:
Make sure TWRP has been installed and functional.
Download the latest build image and kernel linked below
Reboot to recovery
Wipe system, data and cache from the wipe menu
Select flash image in twrp, lower right side on the install menu
Flash the rom image as system (and gapps). DONT flash gapps. they are already included in the rom.
Flash the kernel image corresponding to your model as boot
Reboot and enjoy :victory:
Downloads:
Galaxy S9/S9+ Exynos semi-gsi image link: (G965/N960/F/FD/S/N): here
Kernel image link(important to use this. read more in FAQ):
S9 Exynos: here
S9+ Exynos: here
Note 9 Exynos: here
A pretty good (unofficial) mirror for (some of the) above files and more is this
Providing feedback:
You are more than welcome to provide any kind of feedback here.
(limited only to feature requests; it's called "pixel experience" for a reason and it should stay that way)
You can also msg me anytime on telegram @ Rainbow_Alex_Dash
Telegram group?
I usually like to hang around here . It isn't mine but hey.
For note 9 more specifically i hang around here too
Changelog:
12.10.2018:
Initial release Boi
Troubleshooting/FAQ:
Q:Can i use any other kernels with this gsi?
A:Nah, not really. I built this kernel specifically to work with this gsi and it includes a few major fixes (for example mtp won't work,major ui lag, no dual speakers etc if you switch to another kernel. But again. If you want to use other kernels, they should* boot. Endurance kernel even has my dual speaker patch and i confirm as working. But again expect bugs.
Q: Is there anything else i should know?
A: Ehhhhhhh, not really. I mean there are some stuff i'm really not proud of,for example to "fix" the ui lag i had to set the minimum gpu frequency to 455; this shouldn't create any issues(perhaps some battery drainage when screen is on) but afaik it doesn't impact sleep or anything else.
Q:Would this be preferred over a device specific rom?
A: Overall nah. The reason i didn't set on building device specific los16.....well actually i did and failed. But this is a pretty good placeholder until someone more skilled than me takes over and creates pie device trees.
Q: Safetynet doesn't pass?
A: Yeah, i guess that's a thing. Go into magisk and download some module called props hide or something. Don't forget to run it from terminal. It should work from there
Q: The rom isn't booting/camera doesn't work
A: Flash/make sure you have the BRI4 vendor, the linked kernel and try again.
Q: The rom is in a bootloop/google apps keep crashing
A: You did read the instructions and NOT flash any gapps riighhttt?? smh, wipe /system,/data and /cache and start over
Q: I have another bug; How can i tell it to you while slightly increasing my changes of it ever getting fixed.
A: You can tell me what's going on either here or on telegram WITH A LOGCAT attached(required);if rom isn't booting at all attach /proc/last_kmsg.
Q: I don't know what/how to logcat. Is it really necessary?
A: Logcat or gtfo
Q: How can i support you?
A: Awwww thanks; On most of my posts on the left side there's a "donate to me" paypal button; You can use that,donations are more than welcome, or if you don't have any $ to spare you can also post here about how awesome i am (this surprisingly helps very much)
Credits:
The lineageos team; device maintainers who did a wonderful job at creating device trees
The pixel experience team for creating the rom we so do enjoy
Many good people from the telegram group (linked above) that helped me create this project and spamming for etas
Big thanx to iqbal sareem best creationner ever; great help
XDA:DevDB Information
Pixel Experience 9.0 Semi-Gsi for the S9/S9+, ROM for the Samsung Galaxy Note 9
Contributors
Rainbow_Dash, phhusson,malinathani, eamo5, jesec
Source Code: https://github.com/rainbowdashh/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-10-12
Created 2018-10-12
Last Updated 2018-10-13
Thanks for sharing.
Wonder if this Kernal image will work with other GSI roms to get them running as smooth as this rom.
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
wenjie1234 said:
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
Click to expand...
Click to collapse
Spen does work as a pointer and to tap and even draw..
The spen button does nothing though. And obviously, the spen settings and apps are all Samsung made so they won't be working here. Highly doubt Spen would work ever on aosp like stock due to Samsung apps incompatibility
wenjie1234 said:
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
Click to expand...
Click to collapse
Spen went work without Sammy's framework but there are plenty of apps on play store that offered similar effects to Sammy's own. I used them on my note tablet when I ran any other rom then sammy roms.
Yes! I've been waiting for this. Thank you so much. Flashing right now. Will report back!
---------- Post added at 08:18 AM ---------- Previous post was at 07:39 AM ----------
Flashed it but no dual speaker or data. Do I flash the kernel to the system partition too? Doesn't say in FAQ?
s3xxt0y said:
Yes! I've been waiting for this. Thank you so much. Flashing right now. Will report back!
---------- Post added at 08:18 AM ---------- Previous post was at 07:39 AM ----------
Flashed it but no dual speaker or data. Do I flash the kernel to the system partition too? Doesn't say in FAQ?
Click to expand...
Click to collapse
I don't know what you mean by data but i do know the kernel is supposed to be flashed as boot
Problem with fingerprint here.
Only first touch for new finger is registered.
After that it's not working anymore.
Data as in mobile / cellular data as discussed in telegram.
For anyone who has no cellular manually add your APN info in network settings.
Fingerprint does work and adds, go to settings and add fingerprints the registration bit is a bit finnicky but it adds them and they work.
A theoretical question/crazy idea:
Will installing Magisk's xmlpak module enable us to download and use the Samsung camera and spen features in this mod? So we could get the super slow mo, etc, back? Thanks
I followed the instructions by flashing the proper kernel image without gapps, but still bootloops in the Google Screen.
sam razzy said:
I followed the instructions by flashing the proper kernel image without gapps, but still bootloops in the Google Screen.
Click to expand...
Click to collapse
Quoting tylerrw from the Note 9 Telegram group...
tylerrw:
Wipe data, cache (not system) > reboot recovery > install semi gsi image > install kernel > install no verity > install magisk
Reinstall (ARH6) vendor image too
After installing semi GSI
Click to expand...
Click to collapse
AlfaM03 said:
A theoretical question/crazy idea:
Will installing Magisk's xmlpak module enable us to download and use the Samsung camera and spen features in this mod? So we could get the super slow mo, etc, back? Thanks
Click to expand...
Click to collapse
No, there's no way to get these features to work in Aosp based roms.
Fingerprint is not working, too all other works fine thank you soooo much!
Dan_FFM said:
Fingerprint is not working, too all other works fine thank you soooo much!
Click to expand...
Click to collapse
Same Here
Do we have the gestures like the pixel 3?
wenjie1234 said:
Do we have the gestures like the pixel 3?
Click to expand...
Click to collapse
No, nur you can activate IT via ADB shell command
If I want to flash another rom after flashing this rom and kernel, can this kernel work well with other roms or should I flash another kernel instead?
My number 1 question is: does dual sim work?
wenjie1234 said:
Do we have the gestures like the pixel 3?
Click to expand...
Click to collapse
Yes - Go into gestures in settings and enable the swipe up gesture. It's under Settings>System>Gestures