New member, had to post it in this section.
This is a test version of MultiROM.
WARNING
It is DANGEROUS to flash MultiROM to your device. It can cause data loss. If you have important files on your phone, NEVER try to do that.
Introduction
MultiROM is a boot manager that allows you to flash multiple roms into the device.
This port for Polaris is based on Tasssadar's work and Vasishath's modification. It seems to work fine now.
You can refer to Vasishath's original post for installation guide.
Reference Links:
[XDA Thread] https://forum.xda-developers.com/poco-f1/development/multirommiui-custom-roms-gsi-t3868734
[Github][MultiROM] https://github.com/ARTI5T/multirom
[Github][Modified-TWRP] https://github.com/ARTI5T/android_bootable_recovery
Download link is below.
Notes:
* You can use MultiROM only with decrypted devices.
* Flash a patch to disable force encryption after flash a ROM with force encryption.
* Don't manually encrypt your data in any ROMs.
* If you want to flash treble GSI, choose A-only images.
** Flashing A/B GSI is theoretically possible if you flash it to a secondary ROM which supports system-as-root. (NOT TESTED)
* Unfortunately, until now, we cannot update a secondary ROM with treble GSI. Now you can update a secondary ROM with system.img.
* Always backup your file before flashing. Especially boot.img or boot partition.
* Be careful with your lockscreen password. You can only set password in either primary ROM or secondary ROMs. Refer to vasishath's thread for more details.
* Not all ROMs are compatible with MultiROM.
* Android 10 can be flashed as a primary ROM. If you have an android 10 ROM as primary, you need an android 9 boot.img and vendor.img in case you have GSIs based on android 9.
Known issue:
* Sometimes touch in TWRP or MultiROM boot screen doesn't work. If you are in TWRP, just reboot. If you are in boot screen, you can also reboot or use volumn +/- instead.
* If you want to uninstall MultiROM, you may need to flash the stock boot.img (In case it can't boot). So please backup your boot.img before flashing.
* Still some bugs with system/vendor compatibility verification. If you meet such errors, please flash a "base firmware" (e.g., MIUI) first, and then flash your zip in "List ROMs".
* In some rare cases, flashing a zip in secondary ROMs may cause primary ROM damage.
This port is only for DECRYPTED device. Don't flash if your device is encrypted.
Please BACKUP before you flash MultiROM.
We're not responsible for any loss caused by this modification.
Download link:
[Google Drive] https://drive.google.com/drive/folders/1C2d3GQT5WVsw83XU6J5qA_oJOYMxyXNX?usp=sharing
Update Log:
28-01-20: Support Android 10 as secondary ROMs. Fix bugs which in some cases cause error 7 when flashing.
17-08-19: Add "Install system.img/vendor.img" in "List ROMs".
16-08-19: Add "skip compatibility verify". Fix some small bugs.
15-08-19: Merge omnirom 3.3.1 source code.
14-08-19: Initial release
Tested on:MIUI11(Android10);ArrowOS(Android 10);LOS17;Flyme8(Android9)
Fantastic. Will try it tomorrow morning and report. Looking forward to it!
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
edit:
Started completely over from scratch. Completely wiped data, installed latest vendor/firmware/ etc...
Still have the same issue, but different flashing error:
With pixel3rom
"string resource 'zip_compatible_err' not found.
Using default value.
ZIP Treble compatibility error!
invalid zip file format.
And then it just aborts.
With arrow OS:
Zip treble compatibility error
invalid zip file format
And then it just aborts.
Firipu said:
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
Click to expand...
Click to collapse
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
__ART1st__ said:
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
Click to expand...
Click to collapse
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Okay. I'll try to update my code. Perhaps a looooooong time
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Now you can try the new recovery.img with version 3.3.1 and let me know the result. It may fix that issue (haven't tested yet myself)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Just remove the asserts lines in updater scripts. That would do it.
Sent from my Pixel 3 using Tapatalk
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
It always happened to me with multirom and dualbootpatcher. You have to delete locksettings files in data/system directory...
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Lucas_Maximiliano said:
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Click to expand...
Click to collapse
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Click to expand...
Click to collapse
If you have the password problem, go to vasishath's thread and download a patch to clear password.
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Install fw+vendor 9.7.25.eu,for me resolve the problem
Sent from my [device_name] using XDA-Developers Legacy app
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Are you sure your are using MIX2S Polaris? Not Mi8 or Poco F1 or MIX3?
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Writesin said:
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Click to expand...
Click to collapse
Did you boot any version of MIUI successfully? Could you try another version to see if it can boot? It can sometimes be the ROM's problem. If it still fails to boot, please tell me the version that can boot and the version which can't boot. But I am a student so maybe not too much time on debugging.
Related
Thanks to @chenxiaolong DualBoot is possible on LG G5 (root and twrp needed)
Original thread for DualBoot patcher is located here:
http://forum.xda-developers.com/showthread.php?t=2447534
Bugs report or questions for the developer please post in original thread.
Questions about how to use DualBoot you can ask here.
Download patcher app from here:
https://dbp.noobdev.io/files/9.1.0....tcherAndroid-9.1.0.r38.g5d5b401-snapshot.apk
DualBoot Patcher is still under development, expect bugs.
I'm not responsible for bricked phones.
You have been warned!
How to:
First make nandroid backup in TWRP!
1. Install DualBoot patcher apk, open an app and go to ROMs section
2. Set the current running kernel as kernel for Primary ROM (app will ask you to do so)
3. Download CM13 or any different AOSP ROM, Gapps and go to "Patch zip file" section.
Use minimal Gapps if you installing on stripped /system partition.
4. Patch the CM13 ROM zip (for LG G5 choose "secondary") and patch Gapps ("secondary")
a) Go to settings of the app and install Boot UI.
25.11.2016 -> Note for H830 users,go with data slot instead of secondary until the secondary slot is fixed.
5. Flash patched ROM and Gapps in TWRP or ROMs section in DualBoot app, click red button to do it.
6. Go to ROMs in the app and tap on the rom you want to boot
7. Reboot
You second system should start. (if you get a black screen,wait a bit,first boot usually takes a while)
How to switch between ROMs:
1. Both ROMs needs DualBoot patcher installed, in "ROMs" section you should see ROMs list.
2. To switch the ROM simply tap Primary or Secondary, tick indicator should appear on ROM.
3. Reboot
To check partition sizes and free space, go to "Free space" section.
App sharing probably still don't work, I didn't try it but most likely after you try it you will need to restore your nandroid.
Location explanation :
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
Lockscreen security solution:
On all ROMs you must set lockscreen to have the same lock e.g. a pattern lock with the same pattern on each ROM to unlock.
The issue has something to do with the secondary ROM overwriting the gatekeeper.pattern.key file, so then when you switch to primary you have a pattern lock but with no correct pattern even set, hence why the pattern you enter is always incorrect.
Steps:
1. Set lockscreen security (what ever you decide to use, fingerprints,pin,password, pattern) in the secondary rom first.
2. Set the exact same lockscreen security in the primary rom
3. That's it,now it works on both roms
Tested on LG G5 H850, I'm running stock lg rom as Primary and CM13 as Secondary.
Tested stock roms with aroma installer,doesn't work as secondary,only as primary.
Tested on LG G5 H830, everything works now.
Stock can't be dual booted as secondary due to size,so go with other slots like,for example, data slot
If in app flashing doesn't work,use twrp to flash the patched ROM and the patched gapps
Since the 25.10.2016 the SD card bug on second rom is fixed,link above updated.
Since 25.11.2016 LG G5 H830 is supported, thanks to jeffsga88 for helping with that.
Updated: 04.12.2016
Awesome, thanks....
Enviado desde mi LG-H850 mediante Tapatalk
I can comfirm this works well running stock rooted and cm13 beta with no issue. Many Thanks
It doesn't seem to work on the h830 : (
eminem5055 said:
It doesn't seem to work on the h830 : (
Click to expand...
Click to collapse
Can you explain that a bit more,did you followed the steps,what happened after reboot,did you chose to boot in cm13 before restarting?
onestyle007 said:
Can you explain that a bit more,did you followed the steps,what happened after reboot,did you chose to boot in cm13 before restarting?
Click to expand...
Click to collapse
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
eminem5055 said:
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
Click to expand...
Click to collapse
I also have the h830 and got the same error message.
---------- Post added at 10:30 PM ---------- Previous post was at 09:47 PM ----------
eminem5055 said:
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
Click to expand...
Click to collapse
The issue is not with rom, the issue is with the patcher. I believe that as of now, the patcher supports only the h850 version.
If the issue is with the patcher then I'm sure it won't be that hard to fix.
Yeah I've just looked at the zip created by the app, it automatically sets it for h850. Thanks for letting me know
onestyle007 said:
Thanks to @chenxiaolong DualBoot is possible on LG G5 (root and twrp needed)
DualBoot Patcher is still under development, expect bugs,currently on LG G5 there is an sd card bug on second rom,shows as corrupted,hopefully it will be fixed soon!
Click to expand...
Click to collapse
Any news regarding the sd card bug?
Thank you in advance
kafisc said:
Any news regarding the sd card bug?
Thank you in advance
Click to expand...
Click to collapse
No news yet. If anything changes I'll inform everyone about it in the first post
Can I have CM 13 as primary and Stock ROM as secondary using a flashable zip?
nima0003 said:
Can I have CM 13 as primary and Stock ROM as secondary using a flashable zip?
Click to expand...
Click to collapse
I had a problem with aroma,so if you have stock zip without aroma you can patch it and use it as secondary
onestyle007 said:
I had a problem with aroma,so if you have stock zip without aroma you can patch it and use it as secondary
Click to expand...
Click to collapse
OK thanks!
So if I wanted it to work on h830, I would have to port the patched ROM to work on h830?
nima0003 said:
So if I wanted it to work on h830, I would have to port the patched ROM to work on h830?
Click to expand...
Click to collapse
I would assume so, the rom would have to be compatible with H830. From what i can tell the Boot Patcher allows you to patch a rom to work on a different partition/slot. It uses a certain set on scripts before to allocate where the files will go then the rom is installed as it normally would.
Please correct me if im wrong anyone
Hi, is the version here different in any way from the original version? Thanks
bonotheedge said:
Hi, is the version here different in any way from the original version? Thanks
Click to expand...
Click to collapse
Version that is posted here has support for LG G5,and since lg g5 is not fully supported (sdcard issue) it's not added to the original version. That's the difference
Thanks. That's what I thought. I hope that this version in some point will also support h830.
Any news about his being available on the h830?
ViperOS for markw is here!
Thanks to qwertyTom, karevn, Razziell, Anomalchik,TheScarastic for working on the source code for MARKW.
Kernel: Nosgoth V3 +
Security system from Dec'17
Current version 24/12/2017: Final
Highlights:
1) Beautiful animations.
2) Beautiful design.
3) Advanced functionality settings.
4) Shuster.
5) Very fast fingerprint scanner. (Personally, tester's fingerprint scanner fires very quickly, faster than on other OSes)
Changelog:<full>
Code:
24-12-17
-Final version
-Enabled camera2api (hal3)
28-11-2017
* kernel/xiaomi/markw/
5ccdc6f core_ctl: disable at config [Nikolay Karev]
5b37dcc DTS housekeeping [Nikolay Karev]
70a3c66 Merge branch 'core_ctl' into experimental_work [Nikolay Karev]
Downloads:
20171224-Server, MD5:
20171224-Gdrive
20171128-Gdrive
20171116-Gdrive
Original Thread: 4pda
Final update announcement!
Shared here instead of ROM section as sources are not disclosed.
Hello my Friend,
Please share screenshots for this ROM.
Mithrandir107 said:
Hello my Friend,
Please share screenshots for this ROM.
Click to expand...
Click to collapse
You'll find screenshots on 4pda thread.
I haven't tried this rom yet. In distant future, maybe. I'll post my own screenshots then, and move this thread on rom section.
Here you go...
Mithrandir107 said:
Hello my Friend,
Please share screenshots for this ROM.
Click to expand...
Click to collapse
How is battery life brother?
saravuthream said:
How is battery life brother?
Click to expand...
Click to collapse
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
BJumperBR said:
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
Click to expand...
Click to collapse
Can you share the thread you followed for dual boot? Or write a thread on it? I've dual boot patcher apk, ends up booting into recovery every time I want to boot into secondary rom. If the ramdisk file of primary rom is modified, it also ends up booting into recovery.
I remember having some partition encryption issues when I first started using DBP and I had to format data/system partition to remove encryption.
As you can see from the screenshot I posted, I've been using all ROMs as "DATA" slots. Secondary ROMs don't work for me either.
kibria.mgk said:
Can you share the thread you followed for dual boot? Or write a thread on it? I've dual boot patcher apk, ends up booting into recovery every time I want to boot into secondary rom. If the ramdisk file of primary rom is modified, it also ends up booting into recovery.
Click to expand...
Click to collapse
BJumperBR said:
I remember having some partition encryption issues when I first started using DBP and I had to format data/system partition to remove encryption.
As you can see from the screenshot I posted, I've been using all ROMs as "DATA" slots. Secondary ROMs don't work for me either.
Click to expand...
Click to collapse
I have data partition formatted, phone shows not encrypted now. I'll try installing in data slot.
No extra tweaks are required then?
Just patch the ROM zip to a new data slot and flash it from TWRP.
And remember to patch all zip files you want to flash on the ROM (GAPPS, SuperSU/Magisk) to the same slot you used for the ROM.
kibria.mgk said:
I have data partition formatted, phone shows not encrypted now. I'll try installing in data slot.
No extra tweaks are required then?
Click to expand...
Click to collapse
Nice rom. But Vpapers did not work.
BJumperBR said:
Just patch the ROM zip to a new data slot and flash it from TWRP.
And remember to patch all zip files you want to flash on the ROM (GAPPS, SuperSU/Magisk) to the same slot you used for the ROM.
Click to expand...
Click to collapse
Many thanks. Applied rom in data slot booted up successfully.
BJumperBR said:
Here you go...
Click to expand...
Click to collapse
Thank you friend!
New 281117 build.
Download: Server, Gdrive
Changelog: <textfile>
hello,friend,can you help me to tell ZMIJGORYN something?i find Lineage OS 14.1 Extended one issue,can't set USB to Charge this device only work on Transfer files when i connect the mobile to computer,thanks a lot.And i waiting for him Lineage OS version
lovekobeme said:
hello,friend,can you help me to tell ZMIJGORYN something?i find Lineage OS 14.1 Extended one issue,can't set USB to Charge this device only work on Transfer files when i connect the mobile to computer,thanks a lot.And i waiting for him Lineage OS version
Click to expand...
Click to collapse
Have you checked the settings in Developers option? You can switch default usb option there.
kibria.mgk said:
Have you checked the settings in Developers option? You can switch default usb option there.
Click to expand...
Click to collapse
Yeah,i try it to solved that,thanks.
New 20171222 build is up, comes with hal3.
Download: server
BJumperBR said:
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
Click to expand...
Click to collapse
Hi. Im new to flashing and I want to use the dual boot. Where can I download it and how can I use it? A thread for our device would be nice. Thanks
I tried to download the latest build from qwertytom.cloudapp.net but the site can't be reached. Is there another download link?
Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.
Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"
Or simply join the telegram group.
Peace.
Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol
Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.
Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.
Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery
Update:
Added Magisk news;
Added stock PRA ramdisk
UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?
Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.
The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot
How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka
I'm proud to present the first dual boot project for the Samsung Galaxy S9+ Snapdragon version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
NOTE
Treble-based ROMs are NOT supported(yet)! In-app ROM changing may not work on stock ROM (maybe it works, maybe not) so you have to use utilities.zip or flash the boot.img of every ROM! I do not own a S9+ so I rely on you guys!
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Patcher: Download
Utilities: Download
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy S9+ Snapdragon/Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Epic htc 1 said:
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Click to expand...
Click to collapse
Yes root is needed, but the patcher does not support treble ROMs at this point. Maybe in the future.
Im not a programmer, I just add support for devices and compile it. The real programming is made by the official devs
please support for exynos
Joad said:
please support for exynos
Click to expand...
Click to collapse
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
simon151102 said:
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
Click to expand...
Click to collapse
Thanks .
View attachment 20190225.101831.tar.gz
Joad said:
Thanks .
Click to expand...
Click to collapse
Will compile a new version with S9+ Exynos support in the next few days
Update
Support for S9+ Exynos version
Patcher: Download
Utilities: Download
Does anyone have a root for s9 plus (snapdragon)
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Epic htc 1 said:
Does anyone have a root for s9 plus (snapdragon)
Click to expand...
Click to collapse
Use magisks built-in root, works perfect on most devices
Joad said:
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Click to expand...
Click to collapse
I will look into this.
But I cant guarantee for a fix because I have no skills in programming
Thank you very much,if anyone has any information about this plz let me know I'm really interested in this program
Does this work for anyone? and if so, using which roms.
Thanks
cvamoose said:
Does this work for anyone? and if so, using which roms.
Thanks
Click to expand...
Click to collapse
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
simon151102 said:
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
Click to expand...
Click to collapse
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
cvamoose said:
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Click to expand...
Click to collapse
Yes, treble devices arent supported (yet?).
I dont know if the S9+ is treble based, but it seems like this version of DBP works for most S9+ users
kykint said:
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
Click to expand...
Click to collapse
Sorry, Im not a "real" dev.
All I did was following the instructions from the DBP wiki.
Is there anyone that can make a modded version of this that will work on non rooted phones and it doesn't have to be a dual boot patcher but just to get a different ROM running on top or VNC into and use. Maybe like a dual ROM runner.
Hello! So this is my first post, i actually just made an account specifially to post this because i noticed there was no instructions anywhere
I have a Moto G8 Plus that's running Lineage OS 17.1, i sucessfully ran AOSP, Havoc and Bliss with a perfect experience across the board, the install process for the GSI is super easy and does not involve TWRP or any recovery for that matter
Software wise, you're going to be needing two things: ADB and FASTBOOT, which can be obtained easily through a google search, then you need the usb drivers for your phone, which should also be easy to find
SO, here's the steps, do backup your phone beforehand as what you're about to do will wipe your phone clean:
1. Power off the device
2. Hold Power and Vol Down to enter Fastboot
3. Now that your phone is in fastboot, you need to flash a stock rom onto it, i used lolinet for my android 10 stock rom (in the RETLA region, be sure you get the right region rom), doing that is quite simple, just copy the g8flash.bat file into the same folder where you extracted your stock rom, open the .bat file i provided and let it do it's thing, it'll close when it's done, you have now installed a stock rom on your phone
4. download a GSI https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list (From android 10 to Android 12, haven't got 9 to work), you should get a .img or a .bin file
5. put the GSI in the same folder as your stock rom and rename the file GSIROM (don't change the .bin or .img, i will put 2 files to deal with this)
6. copy either GSI_INSTALL_IMG.bat or GSI_INSTALL_BIN.bat inside the folder
7. run the bat file and let it do it's thing, once it's done, you are ready to reboot your phone and enjoy your new rom
If you have issues, feel free to post about it and i'll try answering as soon as i can, i wish all of you good luck!
Hey thanks for the post. I tryed to download HavocOS-4.5-official-arm64-ab-gapps.img (3.3153489 KB) but it won't let me install. Error message says flashed image is larger than partition size.
So i check on TWRP -WIPE -partition options for system. and i got this:
Size: 2991MB - Used: 2771MB - Free: 219MB Backup Size: 2771MB
so any tips ? i'm on stock rom right now.
daniel_lvs said:
Hey thanks for the post. I tryed to download HavocOS-4.5-official-arm64-ab-gapps.img (3.3153489 KB) but it won't let me install. Error message says flashed image is larger than partition size.
So i check on TWRP -WIPE -partition options for system. and i got this:
Size: 2991MB - Used: 2771MB - Free: 219MB Backup Size: 2771MB
so any tips ? i'm on stock rom right now.
Click to expand...
Click to collapse
Hi! Did you use fastboot or TWRP? You should have the default recovery after flashing the stock ROM
Make sure to get the latest stock for your software channel (I'm on RETLA) https://mirrors.lolinet.com/firmware/moto/ and flash it in fastboot using the .bat files I provided
Hope that helps!
hi thanks for reply. i did use fastboot and also your files. After i got the error on fastboot, i used a twrp.img to boot just to check the partition but its not flashed/saved in memory recovery. i also download lastest stock rom from your link. mine is RETBR.
i tryed the havoc file without gapps and it worked (file size to flash is smaller and fits partition) but i coudn't get to work google account or play store.
the havoc file with gapps included keeps saying is larger than partition size.
daniel_lvs said:
hi thanks for reply. i did use fastboot and also your files. After i got the error on fastboot, i used a twrp.img to boot just to check the partition but its not flashed/saved in memory recovery. i also download lastest stock rom from your link. mine is RETBR.
i tryed the havoc file without gapps and it worked (file size to flash is smaller and fits partition) but i coudn't get to work google account or play store.
Click to expand...
Click to collapse
Hi, can you try to flash this GSI instead of Havoc? If it works, the problem may be the havoc GSI you're using, if that's the case i'll start looking on my end for a working Havoc GSI:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS.img.xz/download
Make sure to select the right variant when getting a GSI, here i already selected the right one
i got this arm64-ab; is that correct?
HavocOS-4.5-official-arm64-ab-gapps.img file size 3.315.489 KB (coudnt flash duo size)
HavocOS-4.5-official-arm64-ab-vanilla.img file size 2.466.145 KB (it worked but does not work google account)
i'll try your file now
daniel_lvs said:
i got this arm64-ab; is that correct?
HavocOS-4.5-official-arm64-ab-gapps.img file size 3.315.489 KB (coudnt flash duo size)
HavocOS-4.5-official-arm64-ab-vanilla.img file size 2.466.145 KB (it worked but does not work google account)
i'll try your file now
Click to expand...
Click to collapse
Hey there sorry for the late answer, I've been trying out GSI's and from what I've experienced, Google Play services won't work on Android 11 GSI's, at least for the G8 Plus.
I'm currently running an Android 10 version of Havoc and everything is working perfectly
MappleBunny said:
Hey there sorry for the late answer, I've been trying out GSI's and from what I've experienced, Google Play services won't work on Android 11 GSI's, at least for the G8 Plus.
I'm currently running an Android 10 version of Havoc and everything is working perfectly
Click to expand...
Click to collapse
did u even try to report to Phh regarding gapps issue?
hey thanks for reply. Gapps worked after i registred the device id for validation on google's page.
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
Does it root the device?
daniel_lvs said:
hey thanks for reply. Gapps worked after i registred the device id for validation on google's page.
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
Click to expand...
Click to collapse
Hey thanks for the info!
jcamelo said:
Does it root the device?
Click to expand...
Click to collapse
Depends on the GSI, if it's not rooted you should be able to use MAGISK using the boot img method
Nice! I didn't even knew about this GSI thing. How far things have come since gingerbreak/kitkat times!
I'll save it for when the guarantee runs out! Thanks!!!!
I just wanted to say thank you for this. I have a xt2019-2 and I couldn't figure out which firmware to download from lolinet so I just did RETAIL and it worked thanks to your instructions.
MappleBunny said:
If you have issues, feel free to post about it and i'll try answering as soon as i can, i wish all of you good luck!
Click to expand...
Click to collapse
Many thanks! succesfully flashed lineage 18.1 on g8 plus!
sorry for the noob question but how do I need to rename the img, just GSIROM or how?
Jairsantana said:
sorry for the noob question but how do I need to rename the img, just GSIROM or how?
Click to expand...
Click to collapse
Nope.
methuselah said:
Nope.
Click to expand...
Click to collapse
So no rename to the gsi?
Hi,
so i was able to flash to stock rom , but any gsi rom i try fails, it stops at the flashing system 1/x, so the phone just boots into the stock rom
Edit : i was able to get havoc android 10 to install , trying the lineage 18 linked in the thread and havoc androind 11 didnt work
lesion said:
Many thanks! succesfully flashed lineage 18.1 on g8 plus!
Click to expand...
Click to collapse
Did bluetooth works?
Thanx