I've seen a couple of requests for the F2FS file system support in some of the CM12.x based rom threads and did some googling on why anyone would want F2FS instead of EXT4. There are also reports, by Nexus 7 users, that converting to F2FS fixes their performance issues.
So after some learning/failing, I'm releasing this zip file that updates (theoretically) any kernel to add F2FS support for the /cache partition. This is not necessary for the /data partition as it has always been F2FS formated (stock Moto or CM roms) for ghost :good:
The modification works by adding a mount options for the F2FS file system (in addition the the EXT4 file system mount option) to the fstab in the current kernel on your ghost.
ghost zip is for AOSP/CM based roms only!
MOTO 4.x.x is for KitKat Stock/Moto based roms only!
MOTO 5.x.x is for Lollipop Stock/Moto based roms only!
I used the information on HTC dev @jrior001's thread so I'll include some of the info he provided:
Original thread here: http://forum.xda-developers.com/htc-desire-hd/development/f2fs-acecm12-lp-aosp-t2995418
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
Does it work?
Ghost already benefits (per Anandtech's post) from F2FS formated /data so there isn't going to be a massive difference in performance. However, my phone seems to be a little quicker/smoother FWIW.
Switch to F2FS cache file system:
1. Update to TWRP 2.8.x.x and boot into recovery.
2. Create a backup of your device (you can get away with a backup of /boot only).
3. Goto WIPE > ADVANCED WIPE.
4. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > F2FS.
5. Flash the attached zip file.
6. Reboot.
Switching back to EXT4 cache file system:
1. Boot into recovery.
2. Goto WIPE > ADVANCED WIPE.
3. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > EXT4.
4. Reboot.
Devs can add this to their builds by simply inserting the following line into fstab.qcom prior to building boot.img:
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
Credit:
@jrior001
@infectedorganism (gave me the heads up to check fstab.qcom)
@tdhite (I used your zip file as a basis to create the flashable zip)
As always, I'm not responsible for any loss of data; always make a backup prior to messing around :laugh:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So did u notice any performance difference? CM12.1 is smooth and fast as it is so I can't imagine our baby might be even faster
Edit: OK I missed that part about a bit smoother etc I will give it a try though and report back
chaoslimits said:
I've seen a couple of requests for the F2FS file system support in some of the CM12.x based rom threads and did some googling on why anyone would want F2FS instead of EXT4. There are also reports, by Nexus 7 users, that converting to F2FS fixes their performance issues.
So after some learning/failing, I'm releasing this zip file that updates (theoretically) any CM12.x based kernel to add F2FS support for the /cache partition. This is not necessary for the /data partition as it has always been F2FS formated (stock Moto or CM roms) for ghost :good:
The modification works by adding a mount options for the F2FS file system (in addition the the EXT4 file system mount option) to the fstab in the current kernel on your ghost.
This is for CM12.1 (and possibly AOSP) based roms only.
I used the information on HTC dev @jrior001's thread so I'll include some of the info he provided:
Original thread here: http://forum.xda-developers.com/htc-desire-hd/development/f2fs-acecm12-lp-aosp-t2995418
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
Does it work?
Ghost already benefits (per Anandtech's post) from F2FS formated /data so there isn't going to be a massive difference in performance. However, my phone seems to be a little quicker/smoother FWIW.
Switch to F2FS cache file system:
1. Update to TWRP 2.8.x.x and boot into recovery.
2. Create a backup of your device (you can get away with a backup of /boot only).
3. Goto WIPE > ADVANCED WIPE.
4. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > F2FS.
5. Flash the attached zip file.
6. Reboot.
Switching back to EXT4 cache file system:
1. Boot into recovery.
2. Goto WIPE > ADVANCED WIPE.
3. Select CACHE > "REPAIR OR CHANGE FILE SYSTEM" > EXT4.
4. Reboot.
Devs can add this to their builds by simply inserting the following line into fstab.qcom prior to building boot.img:
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
Credit:
@jrior001
@infectedorganism (gave me the heads up to check fstab.qcom)
@tdhite (I used your zip file as a basis to create the flashable zip)
As always, I'm not responsible for any loss of data; always make a backup prior to messing around :laugh:
View attachment 3399179 View attachment 3399180
Click to expand...
Click to collapse
Can I use this mod for stock Android 5.1 ?
md07 said:
Can I use this mod for stock Android 5.1 ?
Click to expand...
Click to collapse
This is for only Cm12.1 based rom or for aosp based roms
md07 said:
Can I use this mod for stock Android 5.1 ?
Click to expand...
Click to collapse
I doubt this will work for stock 5.1. Can you check /fstab.qcom and see if it mentions /cache partition?
Megatron007 said:
This is for only Cm12.1 based rom or for aosp based roms
Click to expand...
Click to collapse
Pretty sure it will work for your AOSP (looked at r6 build) and all motorola/msm8960dt-common tree based roms (unless there are some major changes to the kernel which prevents it from being rebuilt). :good:
where screenshots from?
I doubt this will work for stock 5.1.
Click to expand...
Click to collapse
not boot on stock 5.1
chaoslimits said:
I doubt this will work for stock 5.1. Can you check /fstab.qcom and see if it mentions /cache partition?
Pretty sure it will work for your AOSP (looked at r6 build) and all motorola/msm8960dt-common tree based roms (unless there are some major changes to the kernel which prevents it from being rebuilt). :good:
Click to expand...
Click to collapse
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
md07 said:
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
Click to expand...
Click to collapse
Restore "boot" from your nandroid. I stated that this was for CM/AOSP roms only
Zorge.R said:
where screenshots from?
not boot on stock 5.1
Click to expand...
Click to collapse
md07 said:
i flashed this mod for stock 5.1. Phone stucked at bootloader unlocked warning screen, and not boot.
Click to expand...
Click to collapse
I can't test since I'm not on stock, but the STOCK zip in the OP should boot stock moto firmwares 4.x.x or 5.x. Same instructions:
1. Nandroid
2. Flash zip
3. Change cache to F2FS in TWRP.
chaoslimits said:
I can't test since I'm not on stock, but the STOCK zip in the OP should boot stock moto firmwares 4.x.x or 5.x. Same instructions:
1. Nandroid
2. Flash zip
3. Change cache to F2FS in TWRP.
Click to expand...
Click to collapse
I downloaded the MOTO_5.x.x_F2FS_enable_v2.zip and placed it on my phone and followed your instructions and it seems like I am stuck, was there another zip?
mastarifla said:
I downloaded the MOTO_5.x.x_F2FS_enable_v2.zip and placed it on my phone and followed your instructions and it seems like I am stuck, was there another zip?
Click to expand...
Click to collapse
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
chaoslimits said:
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
Click to expand...
Click to collapse
I understand that it has to optimize apps, but it wasn't making it that far, it was stuck on the boot logo like other people have mentioned
I changed it back to EXT4 and restored the BOOT partition, and its back to normal
chaoslimits said:
Where are you stuck? It'll take a while to boot as it has to optimize the apps on boot again. If it doesn't boot after a 5 or so minutes, go back to recovery and verify that the change to F2FS stuck. You can switch back to EXT4 and it'll boot.
At worse just restore "boot" from your nandroid.
Click to expand...
Click to collapse
i tested V1 on AICP, worked good ! How about V2? you must test on stock before release
md07 said:
i tested V1 on AICP, worked good ! How about V2? you must test on stock before release
Click to expand...
Click to collapse
Not sure what you're saying. OP doesn't say it works on stock yet. I asked someone with stock, who was willing to test to try it. Also all V2 are for moto firmware not for CM or AOSP roms.
I'll load stock when I am able but TWRP flash logs would help me figure it out quicker. I'm 99% sure the boot.img isn't being rebuilt due to rramdisk name inconsistencies.
V2 also not worked with stock 5.1 . stuck at bootloader warning screen, not continue boot
md07 said:
V2 also not worked with stock 5.1 . stuck at bootloader warning screen, not continue boot
Click to expand...
Click to collapse
Thanks for getting back to me. Found a silly typo in the scripts. v3 should work for you. Can you test?
chaoslimits said:
Thanks for getting back to me. Found a silly typo in the scripts. v3 should work for you. Can you test?
Click to expand...
Click to collapse
Well well, finally, V3 worked on stock 5.1.
Tks for your hard work!
md07 said:
Well well, finally, V3 worked on stock 5.1.
Tks for your hard work!
Click to expand...
Click to collapse
Great! Please post if you notice any performance changes. I'm curious if it's a placebo or if there's real improvement
Confirm, v3 worked on stock 5.1, thanks for work!
I think in order for this to work on stock 5.1, the kernel has to support fsfs, which so far there aren't any custom kernel available on 5.1. It does however work on CM roms perfectly well although to be perfectly honest I don't see any difference except for the hassle of reformatting the cache partition back to ext4 everytime I want to flash stock.
Sent from my Moto X
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for LG G PAD 8.3 (V500). It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or TWRP to flash it.
MultiROM - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file or TWRP Backup and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/multirom-v500/multirom
Modified TWRP - https://github.com/multirom-v500/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/multirom-v500/android_device_lge_v500
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
XDA:DevDB Information
MultiROM, Tool/Utility for the LG G Pad 8.3
Contributors
beroid, nkk71
Source Code: https://github.com/multirom-v500
Version Information
Status: Stable
Created 2016-11-25
Last Updated 2017-01-30
Downloads
AndroidFileHost
No-kexec workaround
Mini FAQ:
Q: What is the no-kexec workaround?
A: The no-kexec workaround by @nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
@beriod can i install Malladus In this Or Stock 4.4.2?? You only say dont add Stock Lollipop Rom?
Bootloop!
Install Multirom and TWRP Patched By Multirom, then Add Rom And I flash is Validus (5.1.1) Romafter it go on list rom, click the validus in list, flash zip, (GAPPS) and (Patched kernel), and bootloop
Jansxel said:
Install Multirom and TWRP Patched By Multirom, then Add Rom And I flash is Validus (5.1.1) Romafter it go on list rom, click the validus in list, flash zip, (GAPPS) and (Patched kernel), and bootloop
Click to expand...
Click to collapse
You need to have kernel with kexec-hardboot patch only in your primary ROM!
beroid said:
You need to have kernel with kexec-hardboot patch only in your primary ROM!
Click to expand...
Click to collapse
Oh Ahaaha Sorry i try it later. This is the first time i use this.
@beroid can you link me to your kernel v500 sources so i can patch up my cm12.1 kernel, to use kexec hardboot? already doing it on Z2.
thanks.
Can anyone patch stock kernel ? Haven't enough knowledge to that,but I want very much have stock as primary
Написан с LG-V500. Работает на XDA Forums Pro
Maraudeur said:
Can anyone patch stock kernel ? Haven't enough knowledge to that,but I want very much have stock as primary
Написан с LG-V500. Работает на XDA Forums Pro
Click to expand...
Click to collapse
I was thinking about just installing CM12.1 , why do I want to keep stock as primary? if I might ask?
i've integrated that kexec hard-boot patch on my v500 kernel, working fine, but theres an issue...
the screen starts very dimmed, and stays that way until it fully boots CM12. it reminds me of the issue we have with the 4.2.2 base and the 4.4.2 base.
infected_ said:
i've integrated that kexec hard-boot patch on my v500 kernel, working fine, but theres an issue...
the screen starts very dimmed, and stays that way until it fully boots CM12. it reminds me of the issue we have with the 4.2.2 base and the 4.4.2 base.
Click to expand...
Click to collapse
brightness: MiltiRom -> Settings -> Screen Brightness
beroid said:
brightness: MiltiRom -> Settings -> Screen Brightness
Click to expand...
Click to collapse
you must have some sort of issue reading my posts, or my explaining skills suck ..
its not on MR recovery the issue.... its after boot, when the MR menu shows to select ROM, the screen is dimmed, and stays that way until it fully boots to CM12.
nevermind... you we're right... this doesnt happens on sirius, so it was a new prob for me.
thanks and regards!
Update is up (MultiRom + Kernel).
MultiRom Now Supports Stock rom V30A-Korea as secondary
hmmm... @beroid, can you explain the fact, deleted 3 secondary ROMs, after that i flashed 20E as secondary, booted fine..
next thing i am twrp, my internal partition only has 8223MB ? already wiped it 3 times, changed recovery, reflashed CM12.. same thing.
i suppose i will have to flash 4.2.2 and then upgrade to CM12 to fix it, right?
ps: screen in attachment is after the 3 wipes i did...
TWRP shows free space of partition.
in attachment:
Capacity: 11 Gib
Used: 3 Gib
Available: 8 Gib
beroid said:
TWRP shows free space of partition.
in attachment:
Capacity: 11 Gib
Used: 3 Gib
Available: 8 Gib
Click to expand...
Click to collapse
i dont have any secondary ROM installed... those 3GB are the system partitions of the host ROM?
11 GiB are 11.8GB
16GB are 14.90Gib
where did the 3.4GiB (3.6GB) + 3 GiB (3.2GB) went?
sorry for all the noobish questions but is the first time i ever used MR on the v500, and i suppose i never noticed the complete internal memory size.
check /data/media/0/multirom/
beroid said:
check /data/media/0/multirom/
Click to expand...
Click to collapse
ok give me a minute.
---------- Post added at 11:31 ---------- Previous post was at 11:28 ----------
beroid said:
check /data/media/0/multirom/
Click to expand...
Click to collapse
empty. the folder doesnt even exists 'cause ive uninstalled MR and the MR twrp.
infected_ said:
ok give me a minute.
---------- Post added at 11:31 ---------- Previous post was at 11:28 ----------
empty. the folder doesnt even exists 'cause ive uninstalled MR and the MR twrp.
Click to expand...
Click to collapse
Multirom uses only /data/media/0/multirom/
From device with Korean LP (never installed MultiRom).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is only for Huawei Mate 8 (NXT)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-next.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_next/releases/download/3.1.1-1/twrp-3.1.1-1-next.img"][U]download twrp-3.1.1-1-next.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which Mate 8 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
[TWRP][3.1.1-0][MATE 8][DECRYPTION SUPPORT], Tool/Utility for the Huawei Mate 8
Contributors
OldDroid, XePeleato, surdu_petru
Source Code: http://ttps://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-04-08
Last Updated 2017-06-11
Reserved
TWRP 3.1.0-1 next for encrypted/ decrypted data
This post has been deplaced here. I'll remove it when the TWRP above will work for encrypted/ decrypted data.
Thanks for comprehension!
I'm glad, that we can help the Mate 8 community
Thanks for distribution ...
The themes are here now.
Thanks!
Thak you very much.
I have your "Boot_Insecure_B560_Fix-adb_dm-verity.img" installed. Do you recomend to go back to stock boot and use this TWRP for any flashing? Or shoud i stay in a insecure boot?
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Us there 2 differnt versions of this twrp 1 for decripted data and 1 for formated data ??
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
franzyroy said:
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
Click to expand...
Click to collapse
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads : twrp-3.1.0-next-v2.img md5 : 7ee1833ea51bf3835efc23851ad9a011
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
It seemed to me that dexz had tested it like that.
If I can test it, I'll do it. In the week, it's not really possible for me. @dexz should can do it.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
With the TWRP here, the root works too.
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
dexz said:
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
Click to expand...
Click to collapse
jac10000 said:
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
Click to expand...
Click to collapse
Perhaps you should make that and send the console.recovery.log to @surdu_petru or @OldDroid because if they have made the TWRP with mine, it's perhaps the cause.
@surdu_petru
---->logs
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
I say that because :
I have no issues with a prerooted boot
It's also with Decrypted data boot
I can install a zip without to see an error
I see the internal storage
I can also see the size, not 0 MB
Only thing which doesn't work fine, when I mount the data, it's unmounted in the 5 seconds.
surdu_petru said:
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
Click to expand...
Click to collapse
Thank you. Looking forward to it.
Sorry I'm out of like bullet :laugh:
New Test Version 3 !
Downloads : twrp-3.1.0-next-v3.img md5 : d969789ee06d3d323a98d9f028e6f475
Thank you for the feedback
TLDR:
1: MAKE A BACKUP. Seriously.
2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for OnePlus 2. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still experimental!
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via USB-C OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_oneplus2_YYYYMMDD.img) - download the IMG file from second post and use fastboot to flash it.
MultiROM (multirom-YYYYMMDD-vXX-oneplus2.zip) - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/nkk71/multirom/tree/master (branch master)
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project (branch android-7.1-mrom)
Device tree: https://github.com/MZO9400/device_oneplus_oneplus2-mrom -b twrp-mrom
Thanks
This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.
Issues
- None that are known. If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it in the thread
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
Changelog
Here
Downloads
Downloads in second post
NOTE:
Third party kernels with kexec-hardboot support (can be flashed to primary ROM): THIS IS NO KEXEC MultiROM, you don't necessarily need kexec hardboot supported kernels
Extra Information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error
XDA:DevDB Information
MultiROM for OnePlus2, Tool/Utility for the OnePlus 2
Contributors
MZO, nkk71, martinusbe
Source Code: http://github.com/multirom-dev
Version Information
Status: Stable
Current Stable Version: v33b
Stable Release Date: 2017-05-13
Current Beta Version: v33b
Beta Release Date: 2017-04-20
Created 2017-04-20
Last Updated 2017-05-13
MultiROM (folder):
DOWNLOAD
MultiROM v33b
TWRP MultiROM v3.1.1
MultiROM Uninstaller
MultiROM manager modified with OP2 commits has been attached to this post
Method of flashing multirom.
________________
1. Go to TWRP 3.1.0 officially that u already have
2. Flash the multirom image file .. and select recovery when it asks whether u want boot or recovery.
3. When successful go back to maim page and hit reboot recovery
4. Now its multirom
5. Flash the provided multirom zip file. An auto reboot will occur. Hit cancel and go to MISC tab to hit reboot recovery
6. Now the existing rom u had , is primary
7. Go to 3 dot menu of TWRP on upper right corner.
8. Select add rom
9. Flash desired rom
10. Reboot recovery again when successful
11. Go to 3 dot menu again and select list rom
12. Tap on add zip file and add gapps here... That is whatever u file want to flash on a rom just select that rom from rom list and add zip from there
[when flash a secondary, u have to flash zip, then back, and add zip and flash gapps]
13. Hit reboot system.
14. Now a screen will appear even before boot to.ask which rom u want to flash. For the very first time the option is set to, if u don't select any it will boot to primary after 5 seconds, so u hit cancel on that screen (pop up actually)
15. Select the desired rom , double tap on it and it will boot.
First boot of a new rom takes at least 15 to 20 real life minutes.
Notes:
__
To change the option of count down of rom booting selection, go to settings of multirom twrp and turn off option from there. Now every time u reboot.. it will ask which rom u want to boot. And if u don't select any it will stay on same screen till u click something
Tested so far:
Nougat based ROMs
OOS stock
OOS based ROMs
H2OS
MIUI
FlyME
Okay so @Tomsgt has made an amazing guide on how to set up and run MultiROM for our device (or any device), you can find his video right here:
<Mod Edit: Link removed for promoting paid service.>
Awesome work
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
martinusbe said:
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
Click to expand...
Click to collapse
Fixed!
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
[email protected] said:
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
Click to expand...
Click to collapse
Probably because of the ROM. It might need more tags since we can't agree on ONE name
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
Its working fine now...awesome work... :good:
Great man, thanks a lot.
Sent from my ONE A2003 using XDA-Developers Legacy app
MZO said:
Fixed!
Click to expand...
Click to collapse
cool, thanks for keeping authorship btw
martinusbe said:
cool, thanks for keeping authorship btw
Click to expand...
Click to collapse
My pleasure used your commits and you helped me in the final stage — well deserved!
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
martinusbe said:
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
Click to expand...
Click to collapse
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
MZO said:
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
Click to expand...
Click to collapse
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
martinusbe said:
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
Click to expand...
Click to collapse
Yep it worked with commas. Uploading now two more names: Oneplus2 (pretty common), onePlus2 (what was I thinking??)
Will i need to wipe internel storage for first time
ShaDow18 said:
Will i need to wipe internel storage for first time
Click to expand...
Click to collapse
No you won't.
MZO said:
No you won't.
Click to expand...
Click to collapse
What about recovery do i really need fastboot mode or flasify can also do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Moto G5S Plus. It can boot any Android ROM, besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action in general.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. But it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_sanders_YYYYMMDD-xx.img) - download the IMG file from second post and use fastboot or Normal TWRP recovery if you have or any other third party image installers from Google Playstore.
MultiROM (multirom-YYYYMMDD-v33e-UNOFFICIAL-sanders.zip) - download the ZIP file from second post and flash it in recovery.
2. Via MultiROM Manager app
We do not have Official Support, an unofficial APP can be downloaded from second post)
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/MR-op3/multirom (branch mr-7.1)
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery (branch mr-7.1)
Device Tree - https://github.com/MR-op3/device_motorola_sanders (branch mr)
Credits
nkk71 (For no-kexec workaround)
XDA:DevDB Information
[MOD][OCT 16][Sanders] MultiROM v33 || no-kexec workaround, Tool/Utility for the Moto G5S Plus
Contributors
premaca, syed sajid, GeneticEnginer
Version Information
Status: Beta
Current Beta Version: v33
Beta Release Date: 2017-10-16
Created 2017-10-17
Last Updated 2017-10-31
Changelog and Downloads
If you have come across with WRONG-PIN on Primary after the installation of secondary, flash the following Lock Fix.
Lockfix.zip
20171114
multirom-20171114-v33e- UNOFFICIAL-sanders
TWRP-multirom_sanders_20171114-01.img
20171016
multirom-20171016-v33e-UNOFFICIAL-sanders.zip
TWRP_multirom_sanders_20171016-02.img
- Initial Release
Flash this ZIP file multirom_uninstaller.zipto remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Multirom manager APP: Will be uploaded Soon.
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.I have not tested it yet, as i never used ENCRYPTION on my device, will try to see if there are issues and more users for this use case
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.By default /external_sd is mounted and is used to store the ROMs.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will Motorola Stock works as Primary or Secondary ROM?
Yes, Motorola Stock version works with Multirom as Primary ROM, It is not advised to install stock as Secondary, use only as Primary ROM. You can then install other Android ROMs as secondaries.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
Enabling no-kexec workaround
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
[url]http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4[/URL]
Reserved
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
nkk71 said:
Congrats on the release
But you may have missed a few commits, especially if you're going to be dealing with Oreo and/or sdcardfs
Click to expand...
Click to collapse
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
premaca said:
Sure. Let's get them in. This is initial release, will pick the commits. Needed for our other devices too.
Click to expand...
Click to collapse
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
nkk71 said:
They're still only on my repo, not merged with multirom-dev yet
https://github.com/nkk71/multirom/commits/master
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
There's Android 8.0 file_context fixes, and especially that nasty sdcardfs fix (it's a long commit message, but should be thorough enough)
Also the auto detect legacy props isn't in there (didn't push it, as technically it's supposed to be part of 8.0twrp branch), so if someone get the "assert failed this is for device xxx but your device is '<blank>' " then that's the deprecated legacy property problem.
Really up to you if you want to use these commits (I/we are), but the sdcardfs issue can become really nasty, eg here (he just nuked all his secondaries :/ )
Click to expand...
Click to collapse
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------
i tried this it asked me for password to decrypt data it says wrong password even when i enter right one
i tried the same password for normal twrp it worked
its notworking out with this
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
winpooh said:
Format data button?? I don't know for sure if this is the answer for multi Boot mod but to flash anything in TWRP I had to format data which will also decrypt the phone. As follows... Boot to TWRP, press wipe and then on the right side of the screen above the "slide to wipe" icon is a button that says format data... IT WILL WIPE ALL DATA ON THE INTERNAL STORAGE!! PICTURES, DOWNLOADS, ETC...
Click to expand...
Click to collapse
Yes ,it can work after reset only, you have to do a backup first.
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
abhinav2hd said:
Thnx for ur work mate.. i really needed it to test out oreo roms without losing the stock one & it's working grt..!!
Click to expand...
Click to collapse
Be careful and do read the instructions also.
syed sajid said:
Be careful and do read the instructions also.
Click to expand...
Click to collapse
I've used multirom before.. i know how it works ?
abhinav2hd said:
I've used multirom before.. i know how it works ?
Click to expand...
Click to collapse
That's good, I'm not talking about how to use multirom?
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
[URL="https://androidfilehost.com/?fid=889964283620765983]https://androidfilehost.com/?fid=889964283620765983[/URL]
Do I have to wipe data again after updating?
gaurav.saroya said:
Do I have to wipe data again after updating?
Click to expand...
Click to collapse
Nope, just flash it as normal..
syed sajid said:
Nope, just flash it as normal..
Click to expand...
Click to collapse
Okay thanks
syed sajid said:
Update Multirom Recovery !!!
TWRP-multirom_sanders_20171114-01
https://androidfilehost.com/?fid=962021903579492365
multirom-20171114-v33e- UNOFFICIAL-sanders
https://androidfilehost.com/?fid=889964283620765983
Click to expand...
Click to collapse
Second link not working
gaurav.saroya said:
Second link not working
Click to expand...
Click to collapse
Working ...afh too slow wait till open..
syed sajid said:
Working ...afh too slow wait till open..
Click to expand...
Click to collapse
It's working now
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link above - this is latest twrp with system_image support, it need to restore system treble images
2. download system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Known Issues
1. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
2. SM-T580 only: gps
Links
Treble images
SM-T585:
1. 20180827: initial treble: https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/1cTEXJb9n5oZad0O3DXT5nlEhnlBDP6QB/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/1C0MfHt0SNYL4hD-BtOj3i7O_qBBPD25t/view?usp=sharing
SM-T580:
1. 20180828: initial treble: https://drive.google.com/file/d/1sgB1xQjRWyGM1OfF73Yhl5vRNunP04iK/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/13WL9_Q_WoStf0WVHbmoYaL2CHbCluzNO/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/15dN2DugPBjhi_m0SOy4qYwVmR03nyY69/view?usp=sharing
Root
Use Magisk, it's should work. If during install Magisk give error about missed /vendor, run my prepare script and the install Magisk: https://drive.google.com/file/d/10JnOtyF5Y_4q1OE3FOZYPDcR7TK1jRhA/view?usp=sharing
GApps - Pie only!!!
Right now on T580\T585 pie images with gapps dnw, it's stuck on the start wizard, what is strange.
Solution: flash image without gapps and then flash gapps. It's working. I'm playing right now with aosp 9.0 and gapps.
We have 32bit recovery and right now standalone gapps think about arm and 6.0.1 version, what is wrong. I took gapps from https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141 and fix script inside to arm64 and right sdk version, this is gapps with my fix, what should work on T580\T585: https://drive.google.com/file/d/1kkHUPSznfibcER0DV89GhDdepEjqjCl9/view?usp=sharing
How install gapps:
1. install treble image, then pie system image
2. boot to system
3. restart to twrp and install gapps
4. boot to system, go to play market and login
For now working only this sequence
Recovery
SM-t585:
1. twrp-3.2.3-0: https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
SM-T580:
1. this is original twrp (from https://dl.twrp.me/gtaxlwifi/twrp-3.2.3-0-gtaxlwifi.img.html), I just added system_image support and repack: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
All firmware say about wrong vendor version. This is normal, just press OK.
System images:A only and 64Bits
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
Installation
1. (optional): "Wipe\Format Data": type yes and press ok
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. wipe data: "Wipe\Advanced Wipe" and select "Dalvik/ARP Cache" / "Data" / "Internal Storage" / "System" / "Cache"
3. install treble: "Install", then navigate to lineage-15.1-20180827-treble.zip and "Swipe to confirm Flash"
4. install system: "Install", then press "Install Image" then navigate to system images, then select "System Image" and "Swipe to confirm Flash"
5. reboot
let's experiment together!
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. go to the current twrp and full wipe
2. flash my twrp - this is latest twrp with system_image support, it need to restore system treble images (twrp-3.2.3-0-gtaxlltexx.img): https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
3. flash zip with vendor data and boot image (lineage-15.1-20180827-treble.zip): https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
4. now you device is ready to flash any treble system image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development - download img, copy to sdcard and then flash as system image in twrp
5. if you wanna check another rom, just make 1-4 again
Known Issues
1. video-recording
2. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
All firmware say about wrong vendor version. This is normal, just press OK.
System A only
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
let's experiment together!
Click to expand...
Click to collapse
You are amazing dude thanks so much for releasing this to us. Keep up the great work.
Wow, can you Do the same for the WiFi Version SM-T580?
This is by far the best news for our device. I am wondering if when we'll get official Oreo, Samsung will provide us with a treble rom as well.
Thanks Valera for you support.
I get "No OS installed"
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
paulo boë said:
I get "No OS installed"
Click to expand...
Click to collapse
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
alanloax said:
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
Click to expand...
Click to collapse
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Valera1978 said:
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Click to expand...
Click to collapse
Oh I understand. Luckily I use little the gps. At least to try haha.
Thank you very much again for contributing to these devices, very good work!
Valera1978 said:
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
Click to expand...
Click to collapse
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
paulo boë said:
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
Click to expand...
Click to collapse
Did you flashed anything other than rom? Magisk, gapps?
EugenStanis said:
Did you flashed anything other than rom? Magisk, gapps?
Click to expand...
Click to collapse
Nope, but I kinda forgot to mention that I use it on the T580
Hey, very good job. Please make a 580 version, GPS doesn't matter. You said it was experimental.
paulo boë said:
Nope, but I kinda forgot to mention that I use it on the T580
Click to expand...
Click to collapse
It's cannt work on T580 right now, because treble require changes in DTB. Without DTB changes system cann't mount /cache as /vendor and you will get boot before animation.
Will try build T580 today.
Please someone check version for T580
Valera1978 said:
Please someone check version for T580
Click to expand...
Click to collapse
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Also can you post some screenshots with a link to the treble rom that works?
paulo boë said:
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Click to expand...
Click to collapse
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Valera1978 said:
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Click to expand...
Click to collapse
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
paulo boë said:
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
Click to expand...
Click to collapse
can you send me /data/tombstones and /proc/last_kmsg?
SM-T285YD
Hi,
I have twrp for SM-T285YD but I cannot find any rom for my SM-T285YD. So can I flash this rom in my SM-T285YD.
If not then tell me what I need to do to get it working in my SM-T285YD and also I have the twrp but tell me how can make my twrp treble supported twrp....
Best regards....