Related
Hi All,
sharing the guide to install the multiple Rom's in our Axon 7 (as we don't have multi-boot in place).. as the development already kicked with Noughot.. and multiple roms are landing here...
this is for people who can't move out of Stock (due to Audio issues including me) and want to sneak peak the other LOS based roms.
Dual Boot Patcher is an app created by chenxiaolong for S4 initially and it broadly supports more than 150 devices now, whoever used in S4 would be familiar with it.. this app allows you to have multiple ROMs on a single device.
If you loved his work, go to his thread say Thank You
Axon 7 is official supported
I have tried with RR as Secondary and it's working.. so thought of sharing this.
For More details on this Dual Patcher official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
Instructions: More details
Keep the Stock Rom as always Primary.
Use the Data slot and create a name for the folder, as the System/Cache space will be small for LOS Rom
If you want to flash the LOS, RR roms remove the below script in the update-script (ROM\META-INF\com\google\android)
Code:
assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
Issues:
- Encryption and Boot UI are not supported
- trustzone verification in the Update-script will fail while flashing the TWRP, remove the above code before flashing the zip file.
- Pins, patterns or passwords are wrong in one of the ROMs . Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
Warning: for me setting the PIN in one rom works, if i enabled PIN in 2 roms it's not working, everytime you have to delete the locksettings.db and boot into other rom. Fingerprint works in 2 ROMS
- if In-app flashing doesn't work, you have to use TWRP to flash the patched zip files (use the latest TWRP)
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!Note: If flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it...
Download
Download Dual Boot Patcher APP
Download Dual Boot Utilities
Credits to:
@chenxiaolong - for the great app and supporting till date.
@jimbo77 - for making Dual boot Axon 7 official support
@Glove007 - for additional details on workaround for Op3 - applies to Axon7
XDA Community
if i missed any plz let me know.
i can't find anyother thread related to this Dual Patacher, if it's available please merge the thread.
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Nik2424 said:
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Click to expand...
Click to collapse
No you won't lose any data when you flash this.. (But take a backup for safety)
Plz follow this steps.
Install the Dual patcher app and set the current Rom as primary
Make sure you patch the second Rom and Gapps (Super SU optional) in the Dual Patcher App before flashing in TWRP (or it will overwrite the Primary ROM)
in the patched rom remove the TrusstZone entries as mentioned in OP
then flash it via TWRP.
the Rom will be added to your Data or Cache based on the selection you made while patching the Zip file in the Dual Patcher (Preferable is data slot, and rom will be saved in Data>multiboot).
once logged in the Second rom, use the patcher to set the Rom as secondary.
when you want to switch rom, select the rom in the Dual Patcher app and reboot. (the app will move the correct boot.img to partion and selected rom will boot. )
if you want to Wipe Primary Rom or Second/Third Rom use the Dual Boot Utilities in the TWRP, this will wipe only the specified rom and you Second/third Rom won't get deleted. (if you wipe data/cache using TWRP menu, it will wiped your Second/third roms)
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Nik2424 said:
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Click to expand...
Click to collapse
those are added in the Rom to validate you're flashing in the right firmware.. like Noughot roms shouldn't be flashed in MM firmware.
Nothing wrong here in removing in those lines during flashing as secondary Roms..
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
I edit the update-script and remove the quoted lines
I install the dual boot patcher app
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs.
I boot to both ROMS and select stock as primary and LineageOS as secondary
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
Does this seem about right?
Thanks.
So glad this got brought to our phone
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
you should patch with Dual Patcher APK... -- Dual Boot utilities will be flashed in TWRP to install/wipe/update Primary Roms without impact to other Roms.
I edit the update-script and remove the quoted lines - yes
I install the dual boot patcher app - in primary Rom, yes
Open the App, give Root permission - it will prompt you for making the kernel as Primary, set it now - this is required so that App can switch between multiple Roms
1. basically the App will copy the boot.img of primary into storage>multiboot>primary
2. when you install the secondary rom and boot it up, install the app set the rom as secondary.
3. it will copy the secondary rom boot.img in to the same folder
4. whenever you switch rom, the app will copy the switched roms's boot.img to the Boot partiion so that corresponding rom will start on reboot
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
In-app flashing is failing for me, use TWRP to flash it.
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs. - yes
I boot to both ROMS and select stock as primary and LineageOS as secondary
Set the Primary when you installed the App in primary Rom itself.
and set the secondary when installed the app in secondary rom
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
I doubt App sharing is working correctly, please try and let me know
hope this helps
Does this seem about right?
Thanks.
Worked!
Great, this workd for me thanks!
thank you so much for this post
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Sebastian Fox said:
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Click to expand...
Click to collapse
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
`SBR` said:
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
Click to expand...
Click to collapse
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
mvortex3710 said:
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
Click to expand...
Click to collapse
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
`SBR` said:
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
Click to expand...
Click to collapse
Thanks very much for your fast reply.
When I checked the main thread it seems like this problem may be caused by not flashing a patched kernel as well, so I will try that presently and report back!
Edit: The patched kernel I'm using (AX7Kernel) is returning the error: "unable to find boot block location!", I've tried googling it but haven't found anything. Would you happen to know what might be causing this? Flashing in TWRP seems to have fixed this. Attempting boot now.
Edit 2: Boot didn't succeed, I was faced with 5 vibration then a restart to TWRP, where I used the Dual Boot utilities to change back to my Primary (stock) boot.
I'm going to try the other way round, with RR as primary and Stock as (secondary) data boot.
`SBR` said:
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
Click to expand...
Click to collapse
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Sebastian Fox said:
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Click to expand...
Click to collapse
thats not possible...
`SBR` said:
thats not possible...
Click to expand...
Click to collapse
Oh then it seems we reached a blocked road, is there anyway to convert the stock to f2fs??? Partitioning data???
I will try partitioning if possible but it's useless if the dualboot app/utility doesn't support it.
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Nik2424 said:
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Click to expand...
Click to collapse
for me i'm able to ptach RR and it's working in data slot..
did you try to install anything after patched RR and patched Gapps?
Long story short, this is a zip to debloat your S8 and probably other Samsung devices. Please modify it to suit your firmware. *As long as your rom is from Samsung, regardless of nougat or oreo, most of the package names should be the same thus this zip should still remove quite a lot of them by default, you will need some minor edits to match your rom perfectly though.
The attached zip is what I'm currently using, there's something that I had commented out because I use that feature and never tried disabling it. Please feel free to experiment with it and modify the script as per your need. However, do pay close attention to some of the lines as activating them will cause your phone fail to boot.
If you had any error or knowledge about what certain file does, please provide feedback so that we can improve this script. The ultimate goal is to know what we can stripe off from TouchWiz ROM until close AOSP state without breaking features that we use, that includes .apk files, files of any format and even related lines in build.prop.
Also, for anyone who wishes to use this script in any way, please feel free to do so. No need to inform or give credit.
Since I do not backup my file before testing, I'm using Github to do this for me. The most updated version will be on Github.
For more information please visit Github.
Credit
SoLdieR9312 for his OREO BETA6 Debloat zip as template.
foobar66 for his debloat shell script as a reference.
Google as well as several posts in XDA Developers forum
Hall of fame
1. Debloating Samsung Experience Service might lead to Samsung Account FC / bootloop. By: Saibot.XI
After this zip your phone will be left with:
Stock Samsung Audio (Adapt sound, SoudAlive, etc)
Stock Samsung AOD
Stock Samsung Calculator
Stock Samsung Calendar
Stock Samsung Camera & all plugin
Stock Samsung Clock
Stock Samsung Contacts
Stock Samsung Device maintenance w/ McAfee removed
Stock Samsung Gallery & related editor
Stock Samsung Game Launcher & services
Stock Samsung Live wallpaper picker
Stock Samsung Messages
Stock Samsung Music
Stock Samsung Phone
Stock Samsung Smart capture (Screenshot w/ crop, drawing features)
Stock Samsung Launcher
Stock Samsung Video Player
Samsung Desktop Smart Switch support .apk file
Google play etc among some preloads
And some files that IDK what they do/what will happen after removal
Over hundred of apk files will be removed.
Theme center and Samsung account will also be removed, if you want to use theme, please comment them out before flashing.
They can be removed after you applied your theme and will stick after reboot. This is what I did too.
How do i add themestore and remove it after applying theme? Also, flash in twrp?
Got it working nvm. Awesome work!
I'm on AQGL and used Flashfire but the script doesn't seem to work. I updated the script to reflect the boot device as /dev/block/platform/soc/1da4000.ufshc/by-name/system but that didn't work either. Any other hints or suggestions?
TIA.
kleen3r said:
I'm on AQGL and used Flashfire but the script doesn't seem to work. I updated the script to reflect the boot device as /dev/block/platform/soc/1da4000.ufshc/by-name/system but that didn't work either. Any other hints or suggestions?
TIA.
Click to expand...
Click to collapse
used the updated script from github and works perfectly!
is this working on 955N or 950N variant?
Very good ! VERY SMOOTH AND FAST!
Box3D said:
is this working on 955N or 950N variant?
Click to expand...
Click to collapse
I do expect people here to experiment with it, as I said in Github this is not (completely) noob-friendly.
You can cross check the script with your ROM, majority of the Samsung preloaded app will be the same, the difference usually is carrier apps. Maybe I shouldn't mention that I'm using AQL5.
XDA developer yeah, not XDA noobs.
kleen3r said:
I'm on AQGL and used Flashfire but the script doesn't seem to work. I updated the script to reflect the boot device as /dev/block/platform/soc/1da4000.ufshc/by-name/system but that didn't work either. Any other hints or suggestions?
TIA.
Click to expand...
Click to collapse
I've no idea what is flashfire, sorry about that.
ImbaWind said:
I've no idea what is flashfire, sorry about that.
Click to expand...
Click to collapse
It's an app that flashes zip files similar to TWRP. I have the snapdragon 955u variant so cant use twrp since the bootloader is locked. I do have root though.
kleen3r said:
It's an app that flashes zip files similar to TWRP. I have the snapdragon 955u variant so cant use twrp since the bootloader is locked. I do have root though.
Click to expand...
Click to collapse
I see, good to know. Im using an exynos version so cant really figure that out.
You can even delete folder/file one by one by using terminal/root explorer according to my updater-script, that shouldn't make much of a difference.
Will this work on oreo zra5? Actually tried flashing this but it didnt remove anything at all
I personally use the Package Disabler because I'm not that worried about space but the script helped me extremely on what to disable. Very helpful. (also on aql5 btw)
dr460nf1r3 said:
Will this work on oreo zra5? Actually tried flashing this but it didnt remove anything at all
Click to expand...
Click to collapse
That's weird, it should be able to delete what nougat and oreo have in common and there's quite a few.
porkslapchop90 said:
I personally use the Package Disabler because I'm not that worried about space but the script helped me extremely on what to disable. Very helpful. (also on aql5 btw)
Click to expand...
Click to collapse
System space is quite useless, but it makes people like me feel better when useless stuff is actually gotten rid of.
Plus it is able to remove files, that's beyond the ability of package disabler.
Work on 7.0 aql5? Renovate 7.5
Hey after flashing this tool i have problem : screen write is ereased and when i want to use root file to open system/app my device suddenly reboot what could be the problem?
Nathan5900 said:
Work on 7.0 aql5? Renovate 7.5
Click to expand...
Click to collapse
Im using stock aql5, how do you define 'work' tho?
EDIT: This zip basically removes stuff, so if your ROM contains the stuff that match the updater-script, it gets removed. Nothing magic happening here.
torhect said:
Hey after flashing this tool i have problem : screen write is ereased and when i want to use root file to open system/app my device suddenly reboot what could be the problem?
Click to expand...
Click to collapse
This script doesn't remove the function that allows you to draw on your screenshot cause I'm using that too, one of the actually handy feature added by Samsung...
The reboot part, I'm not sure. Somehow when I try to add back apks directly to system via explorer, my /data partition gets corrupted with
Code:
persist.security.tlc.otp structure needs cleaning
in TWRP, only format data fixes this, and this happened to me twice so I'd recommend you to flash them in instead using the rescue zip template I provided in Github.
The script is really good, I just read it line by line but since I see some issues reported for some people I prefer to try it out later
Edit: i was thinking on replace all Samsung needed apps with Google ones like phone and dialer, anyone knows a port from those?
Disclaimer: I am not responsible for anything bad that may occur with your device, but I will take all the credit you can give me if it works for you!
Finally, I would like to present first custom ROM for our device (Teclast T8)! It was ported by me from ASUS ZenPad 3S 10 Z500M and this firmware has lots of great features! It was tested for about a month before release, because I didn't want to share beta ROM with a lot of bugs/issues.
This version is only for flashing via TWRP! (it can be found here https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647)
Version Information
Status: stable (suits for everyday usage)
Created: 08.01.2019
Updated: 25.06.2020
Android version: kernel 3.18.35, android 7.0 Nougat
What's done/features
Added ROOT (Magisk)
No bugs with battery statistics (like it was on stock ROM)
Unique ASUS design and customization (icons, themes, etc)
New useful functions (split screen, quick launch apps on lockscreen, etc)
Advanced power/battery control tools
04.03.2020 - fixed issues with sound
25.06.2020 - fixed offline charge
Bugs
Double tap to awake function
Gestures on lockscreen
All other functions work great! (fingerprint, camera, etc)
Installation
Download firmware to internal storage
Reboot into TWRP
Do this wipes in Wipe section: system, cache, dalvik,data
Reboot recovery: go to reboot section -> choose Reboot recovery
Go to install section and choose .zip package
After installation completed just reboot device and enjoy
If you face error "failed to mount system" or something like this after installation completed - don't mind it and reboot
Screenshots
P.S After device is booted you can choose any language on system setup. I used MIUI icon pack here.
Download
The link is here - https://mega.nz/file/WxYTDSiI#tFXlrqjv3z9qgXI1aZoUM8NdTP99PvKI5eXJSmIeLEQ
If you would like to support further development - https://www.paypal.me/teclastT8development
Brilliant! Thank you Sword900 - GREAT JOB!
Thanks to the developer for this ROM and TWRP. It's a good device let down by lack of software support and removes all the Chinese native apps which I could not remove even with Titanium backup.
I was running TOS 2.0.1 but with a magisk patched boot image which I flashed a long time ago. This makes it simpler.
There are some issues with the TWRP but atleast I can update Magisk without having to patch the boot image and flash it every time.
The zip file in OP, the folder names have a comma after the number as pointed out earlier. Remove that before attempting any operations or you will face weird and wonderful behaviour.
Works like a charm !
I have problem with the sound. When i turn on the volume and play ssomething, i will hear annoying sound (ezzzzzz,,*%$)
zenacute said:
I have problem with the sound. When i turn on the volume and play ssomething, i will hear annoying sound (ezzzzzz,,*%$)
Click to expand...
Click to collapse
I too... any solutions?
zenacute said:
I have problem with the sound. When i turn on the volume and play ssomething, i will hear annoying sound (ezzzzzz,,*%$)
Click to expand...
Click to collapse
saddys said:
I too... any solutions?
Click to expand...
Click to collapse
Seems like I finally fixed it. You should install new version with all wipes listed, download link was updated. Let me know if you find any other issues.
How did you make this?
I'm trying to do the same with other Teclast tablets.(With P80X)
I would appreciate it if you could tell me.
(I used Google Translate)
few__ said:
How did you make this?
I'm trying to do the same with other Teclast tablets.(With P80X)
I would appreciate it if you could tell me.
(I used Google Translate)
Click to expand...
Click to collapse
I've just ported this ROM from another device with alike parameters (chipset, android os version, etc). There are lots of guides on the net which will help u. Another way is to find or make it manually kernel-source for your device, so u could compile firmwares on your own. But it requires appropriative knowledges in android development. Also u may take a closer look at GSI project as if your stock firmware is based on android 9.0.
ProtonAOSP
Android 11 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Usage with my Proton Kernel is recommended to get the most out of your phone. The ROM does not include Proton Kernel, so you will need to flash it yourself. The ROM will still work with other kernels, but you will not get the benefits of Proton Kernel.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Thank you very much for posting this. I'll definitely be checking it out. Your Proton kernel is quite good already. Interested to see how the ROM functions too.
Really appreciate you building and sharing this for us!
I saw in the P5 thread that it may be possible to get call screening to work if the dialer gets systemized. It's a feature that has really come in handy for me so just want to confirm it will get call screening working.
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
TIA
GoldElocks said:
Really appreciate you building and sharing this for us!
I saw in the P5 thread that it may be possible to get call screening to work if the dialer gets systemized. It's a feature that has really come in handy for me so just want to confirm it will get call screening working.
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
TIA
Click to expand...
Click to collapse
Check out the magisk module systemizer, it's pretty good. I think you're right about all that.
Says microg support. So is does that mean microg is included? Or are standard "gapps" included?
letrain02 said:
Says microg support. So is does that mean microg is included? Or are standard "gapps" included?
Click to expand...
Click to collapse
microG is supported on the non-gapps build, not included. The gapps build includes full gapps.
Thank you for awesome rom, big plus for microg support. Will flash as soon as my Bramble arrives.
did flash all. now google logo, then a fire with beaker on screen.
edit: nevermind...guess that was the loading screen. took a few minutes. didn't seem like a "loading screen"
I am new to ADB AS my old phone used TWRP. Do I need to unlock the bootloader? Is it recommented to Start Form stock ROM, because I am currently on LineageOS? It is MicroG ready, does it mean that install MicroG via F-Droid, or do I install it like it is drscribed there at the Installation instructions?
Estebanium said:
I am new to ADB AS my old phone used TWRP. Do I need to unlock the bootloader? Is it recommented to Start Form stock ROM, because I am currently on LineageOS? It is MicroG ready, does it mean that install MicroG via F-Droid, or do I install it like it is drscribed there at the Installation instructions?
Click to expand...
Click to collapse
You do need to unlock the bootloader. Switching from LineageOS should work, but you will need to wipe data as always.
microG should be installed from F-Droid after installing the ROM.
kdrag0n said:
You do need to unlock the bootloader. Switching from LineageOS should work, but you will need to wipe data as always.
microG should be installed from F-Droid after installing the ROM.
Click to expand...
Click to collapse
Thank you very much. I flashed it and it rebooted directly to the OS. Afterwards I installed your Kernel. The OS feels fast, but in comparison to Lineage for the same Phone, it feels slower. If you swipe for the action center, it is very slow and laggy. If you swipe for task manager and swipe through the recent apps, it lags. Are there any similar experiences?
Estebanium said:
Thank you very much. I flashed it and it rebooted directly to the OS. Afterwards I installed your Kernel. The OS feels fast, but in comparison to Lineage for the same Phone, it feels slower. If you swipe for the action center, it is very slow and laggy. If you swipe for task manager and swipe through the recent apps, it lags. Are there any similar experiences?
Click to expand...
Click to collapse
The lag in those specific locations is caused by the frosted glass blur effect. Disable it in developer options if you want to trade it off for performance instead. The blur performance problems should be addressed in future versions.
kdrag0n said:
The lag in those specific locations is caused by the frosted glass blur effect. Disable it in developer options if you want to trade it off for performance instead. The blur performance problems should be addressed in future versions.
Click to expand...
Click to collapse
Thank you for your reply. I am looking forward to a new release. For now I stick to LOS. Could you tell me the procedure for updating your ROM? Is it possible to dirty flash the update, so I don't need to backup my data externally?
GoldElocks said:
To confirm, I just need to put GoogleDialer.apk into product/priv-app?
Alternatively, could I just use something like Titanium backup to make it a system app?
Click to expand...
Click to collapse
Ocwa said:
Check out the magisk module systemizer, it's pretty good. I think you're right about all that.
Click to expand...
Click to collapse
I tried to use Magisk Systemizer and Titanium Backup to move this into a system app, but there's not enough free space in what I'm assuming is the system partition (Titanium Backup just labels it the "System ROM").
I tried to uninstall some of the system apps using Titanium Backup and SD Maid Pro but both failed to be able to remove any "expendable" system apps.
Estebanium said:
Thank you for your reply. I am looking forward to a new release. For now I stick to LOS. Could you tell me the procedure for updating your ROM? Is it possible to dirty flash the update, so I don't need to backup my data externally?
Click to expand...
Click to collapse
Yes, you can dirty flash updates to my ROM. Clean flashes are only necessary when switching from another ROM.
OptoChip said:
I tried to use Magisk Systemizer and Titanium Backup to move this into a system app, but there's not enough free space in what I'm assuming is the system partition (Titanium Backup just labels it the "System ROM").
I tried to uninstall some of the system apps using Titanium Backup and SD Maid Pro but both failed to be able to remove any "expendable" system apps.
Click to expand...
Click to collapse
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
kdrag0n said:
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
Click to expand...
Click to collapse
Dynamically sized partitions explains the "no free space" (and it makes total sense to layout the system partition this way). I was trying to use Magisk Systemize, took me revisiting it to realize that I didn't have Busybox installed. Installing the Magisk BusyBox module enabled me to Systemize the Phone app. Many thanks!
kdrag0n said:
Yes, you can dirty flash updates to my ROM. Clean flashes are only necessary when switching from another ROM.
With dynamic partitions, the system partition is perfectly sized to hold exactly the amount of data the ROM has in it, so there will always be no free space. You need to use Magisk to systemize apps.
Click to expand...
Click to collapse
Hello kdrag0n, I am thinking about switching phone service from Verizon to Google FI and I would like to root a Pixel 4a or an Pixel 4a.(5G). Can anyone tell me if this Rom has the Hotspot wifi tethering option included in the Rom? Thank You
wilspeak said:
Hello kdrag0n, I am thinking about switching phone service from Verizon to Google FI and I would like to root a Pixel 4a or an Pixel 4a.(5G). Can anyone tell me if this Rom has the Hotspot wifi tethering option included in the Rom? Thank You
Click to expand...
Click to collapse
Yes. The hotspot option comes with it from what I have tried.
J-I-N-X said:
Yes. The hotspot option comes with it from what I have tried.
Click to expand...
Click to collapse
Thank You for your time
I cant manage to root this rom with proton kernel even on stock cant root pixel4a 5g any guide or help apriciated....
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
AnonVendetta said:
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
Click to expand...
Click to collapse
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
5. Is it possible to moves apps to SD without enabling adoptable storage (on stock, I know custom AOSP firmwares will require AS, or a root app like Apps2SD and a 2nd partition on SD.
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And if I do buy, I am serious about becoming a developer.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
It looks like I can't delete the previous double posts, and editing causes it to be posted again. I hate the new XDA layout, the old was so much better.
AnonVendetta said:
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
Click to expand...
Click to collapse
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
LSS4181 said:
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
Click to expand...
Click to collapse
I am using the WIFI variant (SM-T870) on the latest stock release (T870XXU2BUC6) with root and Magisk 22.1 running just fine. Root was accomplished by flashing a Magisk modified boot image with Odin found here https://forum.xda-developers.com/t/...-updated-3-29-21.4159291/page-2#post-84843377 on this thread. I used Titanium Backup to debloat and have had no issues at all. The performance is great and the stability sound. I would suspect that a similar arrangement could accomplished on the other versions of the tablet but cannot speak from experience. Personally I have never had much luck flashing Project Treble GSIs on any of my devices. They tend to be very unstable and iffy at best and I always wind up returning to stock or another custom ROM choice.