Develop Bugs

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible

Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image

I dont get it
Sent from my Nexus 4 using xda app-developers app

gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch

Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl

hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake

Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?

hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?

Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?

hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.

Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?

hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery

Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!

hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?

Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.

Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails

Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..

subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation

Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files

Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk

Bootloop after flashing AOSP 8.0.0 to Pixel XL.

Hello everyone. I have a problem.
I'm building AOSP 8.0.0_r11 for Pixel XL and when I flash the result zip I'm getting a bootloop.
How am I building?
1) Select java 1.8
2) cd AOSP_8.0
3) source build/ensetup.sh
4) lunch aosp_marlin-userdebug
5) make -j9 updatepackage
6) wait a couple of hours
7) PROFIT
I know the ROM needs vendor blobs, I have them downloaded, extracted and extracted from .sh files.
How does the bootloop look?
Power On->Message about unlocked bootloader->0.5 second of white screen with Android on it-> reboot->repeat.
How do I flash the ROM?
I tried:
1) fastboot update -w aosp_marlin-img-eng.user.zip
and
2) extracted everything from zip and fastboot flash --slot _a PARTITION IMG_FILE
What am I doing wrong? Did anyone have success in building AOSP for this phone?

Did you "make clobber" after installing the drivers? If not, run it then try your make command again.
Alternatively, try "make otapackage" instead of "updatepackage" and then flash it in fastboot.
Also, why are you using the -j9 parameter?

noidea24 said:
Did you "make clobber" after installing the drivers? If not, run it then try your make command again.
Alternatively, try "make otapackage" instead of "updatepackage" and then flash it in fastboot.
Also, why are you using the -j9 parameter?
Click to expand...
Click to collapse
I did "make clobber". It just removes the build directory like "make clean". And this step is redundant if you never built the system before (with or without binaries).
Why make -j9? Because it shows better performance than just make. I know the build system should get the cores number and set the number of build threads, but for some reasons it doesn't do it very well.
P.S. I tried to "make" without -j9 and it is MUCH slower than with -j9.

Are you using the most updated fastboot and adb and sure your computer's variables aren't using an older one also? That was my issue when flashing Oreo.

buru898 said:
Are you using the most updated fastboot and adb and sure your computer's variables aren't using an older one also? That was my issue when flashing Oreo.
Click to expand...
Click to collapse
I'm using those that come with Android Studio 2.3.3 updated to latest versions of all components. That's not the problem with slots support - everything flashes without errors.

Slavon-93 said:
Hello everyone. I have a problem.
I'm building AOSP 8.0.0_r11 for Pixel XL and when I flash the result zip I'm getting a bootloop.
How am I building?
1) Select java 1.8
2) cd AOSP_8.0
3) source build/ensetup.sh
4) lunch aosp_marlin-userdebug
5) make -j9 updatepackage
6) wait a couple of hours
7) PROFIT
I know the ROM needs vendor blobs, I have them downloaded, extracted and extracted from .sh files.
How does the bootloop look?
Power On->Message about unlocked bootloader->0.5 second of white screen with Android on it-> reboot->repeat.
How do I flash the ROM?
I tried:
1) fastboot update -w aosp_marlin-img-eng.user.zip
and
2) extracted everything from zip and fastboot flash --slot _a PARTITION IMG_FILE
What am I doing wrong? Did anyone have success in building AOSP for this phone?
Click to expand...
Click to collapse
More than those blobs are necessary. Look at a invisibleks marlin lineageos device tree to get an idea of what files need to extracted and put in vendor.

Make clobber also cleans out configuration files, in case some of them had been created before the drivers/binaries have been extracted. Speaking of binaries again, did you install the Qualcomm ones?
My build environment is a i7 3770, with 8gb ram, and two blues in raid 0. To get my build compiled correctly, I had to disable ninja and I used -j8.
******
Tomorrow, I'll run a update and build Oreo on my machine from a clean directory and I'll get back with times before end after ccache is filled.

npjohnson said:
More than those blobs are necessary. Look at a invisibleks marlin lineageos device tree to get an idea of what files need to extracted and put in vendor.
Click to expand...
Click to collapse
Well, I don't know about Pixel, but when I had some experience in building AOSP for Nexus 5, Nexus 6, Nexus 9, binaries from Google and Qualcomm were a required minimum to get system booted. And if I wanted to get rid of some errors in logcat, I had to add some additional libraries, but the system booted and worked.
noidea24 said:
Speaking of binaries again, did you install the Qualcomm ones?
Click to expand...
Click to collapse
Yes, of course. I went to google binaries section, selected marlin 8.0.0 and downloaded two .sh files - one from Google, and the other from Qualcomm. Then I extracted them and got a vendor forder which has google_devices/marlin and qcom/marlin folders inside.

I'm curious to know how your process to flash the rom zip works? I've been sitting on a rom build for days because I can't get Twrp to work properly. Also, if your worried about your blobs/vendors the repos are starting to show up on GitHub.

cjkacz said:
I'm curious to know how your process to flash the rom zip works? I've been sitting on a rom build for days because I can't get Twrp to work properly. Also, if your worried about your blobs/vendors the repos are starting to show up on GitHub.
Click to expand...
Click to collapse
I'm sorry if I misundestood the question. I don't undestand why you should need TWRP because you just get the sources, get the blobs, compile them and get a zip file which can be flashed with fastboot command. So, no TWRP in this process is needed. I still don't know how all these ROM creators make zips for flashing with TWRP...

So I was able to get AOSP booting using the basic steps and blobs provided from the script. Even was able to activate the always on display

Zavon said:
So I was able to get AOSP booting using the basic steps and blobs provided from the script. Even was able to activate the always on display
Click to expand...
Click to collapse
Can you, please, describe in details these things:
1) What Linux did you use for building?
2) What revision of AOSP 8.0.0 did you download?
3) What version of blobs did you use?
4) Did you just download the 2 blobs .sh files to the root of the sources and execute them?
5) What AOSP configuration did you choose for building? (I mean aosp_marlin-userdebug or aosp_marlin_svelte-userdebug or aosp-sailfish-userdebug)
6) What command did you use for building?
7) Did you use ccache?
8) Did you flash Google Factory image of Oreo before flashing AOSP?
9) What command did you use to flash?

Slavon-93 said:
Can you, please, describe in details these things:
1) What Linux did you use for building?
2) What revision of AOSP 8.0.0 did you download?
3) What version of blobs did you use?
4) Did you just download the 2 blobs .sh files to the root of the sources and execute them?
5) What AOSP configuration did you choose for building? (I mean aosp_marlin-userdebug or aosp_marlin_svelte-userdebug or aosp-sailfish-userdebug)
6) What command did you use for building?
7) Did you use ccache?
8) Did you flash Google Factory image of Oreo before flashing AOSP?
9) What command did you use to flash?
Click to expand...
Click to collapse
I'm using a base ubuntu vm I built with 2 cores and 8gb ram. I used r11 if memory serves correct. I used the scripts from google and extracted from the factory image. The configuration I used is 21 (marlin-userdebug). I just used make -j8. Could careless about an update zip. And the factory image was on before I flashed using fastboot.
Side note, I also have ElementalX and SuperSU installed. suhide was giving me issues and I just have to figure out the Gapps (I'm a cop so time is hard to come by). I also enabled always on display but just remembered to enable the burnin protection

Can't root through SuperSU or Magisk on open beta 25 (android O)?

I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?

Not yet. Did this really require a thread of its own ?

skymera said:
Not yet. Did this really require a thread of its own ?
Click to expand...
Click to collapse
I just want to know how much will take so that it will be available.

rsm23 said:
I just want to know how much will take so that it will be available.
Click to expand...
Click to collapse
Nobody here can see in the future...

https://forum.xda-developers.com/showpost.php?p=74161852&postcount=3634
here try this Good Luck !

On my phone SuperSU 2.82 SR5 works fine. On other phones not, or SR3 woks....
Magisk 1.4 or 1.42 beta not working. I did not get boot loops, but not working.

rsm23 said:
I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?
Click to expand...
Click to collapse
Follow this guide brother

Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
How did you achieve this?

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
This is a good news. Cannot wait for more details!

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?

ashokmor007 said:
Follow this guide brother
Click to expand...
Click to collapse
Thanks, but I don't like SuperSU
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
mr.charlie said:
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?
Click to expand...
Click to collapse
Thanks, but too much of a hassle for me right now.
I think I'll just wait for an official Magisk update to be released, at this point

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
! We are looking forward to your description: how to take the steps? !

papzi57 said:
! We are looking forward to your description: how to take the steps? !
Click to expand...
Click to collapse
Be carefully, you can lose you data!!! For me all work fine)))
1.Flash Oreo via trwp
2.Downgarde bootloader for DM-Verity
3. Flash Magisk via twrp
4. Turn off the phone manualy
5.Turn on & boot in twrp
6.Do the backup of boot
7.And edit boot.win in hex editor on pc
Code:
androidboot.selinux=permissive
screen in attachment
8.And flash boot back, reboot.
P.S When you set selinux permissive via fastboot you'll have freeze (braking) in system - i don't know how it say

baskaflyfer said:
edit boot.win in hex editor
Click to expand...
Click to collapse
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK

Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Sent from my Pixel 2XL using XDA-Developers Legacy app

papzi57 said:
Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Click to expand...
Click to collapse
I am not able to tell you how safe this method is.
Yes, i did a dirty flash of OOS Open Beta 25, but some apps lost their data (Jodel, photoTAN, ...) but not Google Authenticator :fingers-crossed:
I think the modification of the boot.img is device-specific. I can not tell you details about this because i don't know that either.
There might be another way to set selinux=permissive as recently described in this thread, but your bootloader need to allow the following command:
Code:
fastboot oem selinux permissive
If you are able to perform this command in fastboot mode, maybe you don't need to modify the boot.img manually. Just reboot to fastboot mode after the installation of Magisk in TWRP and type that command.

davidlueder said:
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK
Click to expand...
Click to collapse
Is Magisk stable? Did you try any modules and which ones? Are they working fine?

ishanp said:
Is Magisk stable? Did you try any modules and which ones? Are they working fine?
Click to expand...
Click to collapse
I did not try any modules but multiple apps that require root: AirDroid, AFWall+, Amaze (Root enabled). They're working fine.
Additionally, this magically fixed my ctsProfile. Magisk's SafetyNet-Test is successful on my device now.
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.

davidlueder said:
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.
Click to expand...
Click to collapse
Try in terminal after boot:
Code:
su
setenforce 0
Restart ViperFX app. Please report, I am on SuperSU but will jump the moment my fav modules start working
Also I'm using Viper4Arise (bundled with Magnum Opus) right now. If that didn't work you can use that.

[ROM] BeyondROM V5.8 [15/11/19] [9.0 ASK1] [November Patch] [G973-G975-F/FD]

BeyondRom V5.8
Based on Android 9.0 - G975FXXU3ASK1
Devices Supported: G973F(D), G975F(D)
​
ROM Features
<*>Aroma choices: full/dirty wipe, debloating, Bixby key remapping, Emoji</*>
<*>Supports G973F(D) and G975F(D)</*>
<*>Base SM-G975F G975FXXU3ASK1 odex/deodex November 2019 patch level</*>
<*>CSC features (camera sound menu, call recording, LTE only mod, camera during call, etc)</*>
<*>Knox removed, 1170 fonts by Winb33, AppLock</*>
<*>Included the security bypass from Ian’s multidisabler</*>
<*>build.prop tweaks: multiuser, Bluetooth Aptx driver, call ring delay, SHealth fix, WiFi and BT passwords remember</*>
<*>Dual SIM + SD Card, allow ss in secure apps, disable sig verification, SecureFolder</*>
<*>Reboot directly into rooted system from power menu, disable high volume warning</*>
<*>Possibility to choose in aroma to remove the boot warning</*>
Added/fixed in v5.8
<*>November ASK1 sw level</*>
Credits
- John Wu for Magisk
- Ianmcd for his multidisabler
- Ianmcd & Geiti for the TWRP
- Winb33for the fonts app
- SuperR for his kitchen
- fOmey for his smali patcher
- Khongloi for Secure Folder fix
- Corsicanu for his help and advices
- Sannoc for his help and support
- All people from Telegram group for testing (especially Nathan, Carlos, Raphael, Jay, Alan
Download Link
Google Drive
Digi Link
Flashable patched TWRP S10 (G973F)
Flashable patched TWRP S10+ (G975F)
Installation procedure for upgrade from BeyondROM v5.4 / v5.5
- Take a full TWRP backup
- Dirty flash or clean flash is ok
Installation procedure for upgrade from BeyondROM less than v5.4
- If you are on stock ROM, follow the attached guide
This ROM version needs minimum ASIG BL and ASIG TWRP/recovery or it won't boot !!!
1. Boot in TWRP and take a full backup before flashing BeyondRom 5.8 ROM zip
2. Copy the ROM zip to your phone (Ext SD preferably)
3. Download Ian’s Multidisabler v1.6 or higher and copy it to your phone
4. Download Ian’s TWRP 3.3.1-11, copy it to your phone and patch it with Magisk Manager or use the patched TWRP from gdrive folder
5. Download the stock FW for your device (S10 or S10+) – Frija is a good tool to use
6. Extract the AP from stock FW, copy it to a temp folder on your internal SD
7. Patch in Magisk Manager the AP
8. Copy the patched AP to your PC and replace the recovery.img inside the AP with the patched TWRP from point 4. Rename the patched TWRP to recovery.img before replacing it into the patched AP
9. Open Odin 3.13.1 or 3.13.3 and fill all slots with: patched AP, BL, CP and HOME_CSC. Uncheck the automatic restart and start flashing.
10. Once flashing completed, long press VOL DOWN + POWER until screen becomes black. IMEDIATELY the screen gets black, press VOL UP + BIXBY + POWER BUTTON to enter to TWRP recovery.
11. Once in TWRP, flash the Multidisabler v1.6 and right after flash BeyondROM v5.8 No need to reboot in between.
12. After flashing the ROM zip, save the aroma log, go back to TWRP root menu and select Reboot --> Recovery
13. Wait for the boot up (5-7 minutes) and setup your ROM to your liking
14. Enjoy the release of BeyondROM
Advises
1. Clean install if you have issues with dirty flash; don't start flashing BR5 without a twrp backup of your existing rom
2. If you have flashing issues: check rom zip MD5 hash
3. If you consider that the moded services are the culprit for your SnapChat ban, use stock services.jar provided in the download folder
4. If you like my work, consider buying me a coffee (PayPal link)
Helpful links
Telegram chat
Happy flashing good people!

Always good to see a new rom for the S10(+)
:good::good:

i dont have LTE, only 4G.
what CSC should I chose when flashing?

mcn1970 said:
i dont have LTE, only 4G.
what CSC should I chose when flashing?
Click to expand...
Click to collapse
They're the same thing. It's just the way your phone is reporting the connection.
Regards,
Nathan

sevsman said:
They're the same thing. It's just the way your phone is reporting the connection.
Regards,
Nathan
Click to expand...
Click to collapse
features of the ROM presents LTE instead of 4G mod.
this is what I mean

mcn1970 said:
features of the ROM presents LTE instead of 4G mod.
this is what I mean
Click to expand...
Click to collapse
You have to choose it in the aroma. You may well have missed the option and a dirty flash will fix it.
Regards,
Nathan

sevsman said:
You have to choose it in the aroma. You may well have missed the option and a dirty flash will fix it.
Regards,
Nathan
Click to expand...
Click to collapse
i don't have this in Aroma

another one

??? Good luck with flashing it guys!
I can confirm it is working well on S10 G973F.
Thanks a lot @Andrei1973 @starbucks2010

Thank you for the update! :good::good::good:

Wow July update. !!!
:fingers-crossed::fingers-crossed::fingers-crossed:

Installed. So far working fine. Thanks OP.

how can I install TWRP for Galaxy S10+
and kernel?

tried this at least half a dozen times and get stuck at the same spot. I can root and get Magisk and be fine. Then I patch the appropriate TWRP file for my kernel (S10+ twrp-beyond2lte-3.3.1-3.1_ianmacd.img) and then I open the .tar file. I exchange out the recovery.img with the newly patched one. Then I repackage as a tar using B1 free archiver (this may be the issue, but it seems fine). It creates a new AP file. I insert that into Odin (the same version that worked previously) along with the corresponding BL, CP, and CSC files (I have tried both CSC and Home CSC). I boot into download, hook up my phone, hit flash and VOILA...NOTHING!!!! It says, "file analysis" and crashes every time. After a while I got sick of trying so I made an attempt to flash the recovery.img file straight through TWRP app by itself. All that did was cause an infinite boot loop. Can anyone please help me? Here are my rom file names.
AP_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_low_ship_meta_OS9.tar.md5
BL_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_low_ship.tar.md5
CP_G975FXXU1ASE5_CP12748354_CL16003457_QB23792291_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_G975FOXM1ASE5_CL16003457_QB23792291_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_G975FOXM1ASE5_CL16003457_QB23792291_REV01_user_low_ship.tar
MM Pre-patched AP + TWRP name is "magisk_patched + TWRP.tar."
The TWRP file I downloaded was: twrp-beyond2lte-3.3.1-3.1_ianmacd.img which I of course renamed to recovery.img.
THEN AFTER I GET THIS WORKING, DO I JUST FLASH STRAIGHT THE ZIP FOR THE CUSTOM ROM INSIDE TWRP AND THAT'S IT?
TIA

I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.

kevinjmoore said:
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
Click to expand...
Click to collapse
I think your archive editor isn't up to scratch, install 7zip from here Download
Try using this recovery, its a working pre magisk patched image G973F_magisk_patched3.3.1-3.1.img
Rename it to recovery.img and replace the one inside your magisk patched version of AP_G975FXXU1ASE7_CL16003457_QB24029035_REV01_user_ low_ship_meta_OS9.tar.md5 using 7zip. Then flash with odin.
Hope this helps

kevinjmoore said:
I just noticed that every time I create the tar file it eliminates the .MD5 extension. Can I just edit the file name to include the .MD5 or do I have to do something special to actually modify the file? Thank you.
Click to expand...
Click to collapse
Just delete md5 extension, you don't need that. Odin will flash *.tar file without any problems

Thank you for the reply. There are three things that I'm not sure about. All the versions of 7zip that I have used can't create or edit tar files. The second is my device is 975F not 973. Finally, what are the exact steps to replace the recovery file in 7ZIP? That seems to be where it's having the hangup.
@oggi21 I only added that extension as a last resort. It won't flash the regular tar file once I add the patched AP with TWRP recovery using the B1 archiver. Any help would be appreciated.

Any chance of US CSC's like TMB could be implemented?

kevinjmoore said:
Thank you for the reply. There are three things that I'm not sure about. All the versions of 7zip that I have used can't create or edit tar files. The second is my device is 975F not 973. Finally, what are the exact steps to replace the recovery file in 7ZIP? That seems to be where it's having the hangup.
@oggi21 I only added that extension as a last resort. It won't flash the regular tar file once I add the patched AP with TWRP recovery using the B1 archiver. Any help would be appreciated.
Click to expand...
Click to collapse
The best way is to take any tar file (AP or whatever) and open it in 7zip. Then put yours files in it and delete all others that was inside

Themes / Apps / Mods Universal HArd AF Debloating script (Non-Root) A12, A13 (Aosp , OOS12.1, OOS13)

Use it on your own risk​
Pre requesties :
- Windows/Linux computer
- USB debugging enabled (Developer settings)
- platform tools
Tested on :
pex rom
pixel6p
oos12.1
oos13
color os
How to use​extract attached Debloat_platform_tools zip file (scripts are present inside the zip file)
step1- extract the attached zip ( scripts are present inside)
step2 - run cmd inside the folder
step3 - now drag the script file to cmd screen while connecting your phone with usb debugging on
step4 - run and enjoy debloated android
Note: don't forget to run fix.bat after debloat scripts.
aosp.bat is for asop roms(A12 and A13)
oos.bat is for oos12 and oos13
In case anyone wants to restore all debloated apps :
Revert script (click here)

could u make a note for what apps will be debloated ?

MostaphaHida said:
could u make a note for what apps will be debloated ?
Click to expand...
Click to collapse
you can check with notepad, but i have tested on most of the roms and it works fine , just dont forget to run fix.bat after doing debloat

bluebirdsysx said:
Use it on your own risk​
Pre requesties :
- Windows/Linux computer
- USB debugging enabled (Developer settings)
- platform tools
Tested on :
pex rom
pixel6p
oos12.1
oos13
color os
How to use​extract attached Debloat_platform_tools zip file (scripts are present inside the zip file)
step1- extract the attached zip ( scripts are present inside)
step2 - run cmd inside the folder
step3 - now drag the script file to cmd screen while connecting your phone with usb debugging on
step4 - run and enjoy debloated android
Note: don't forget to run fix.bat after debloat scripts.
aosp.bat is for asop roms(A12 and A13)
oos.bat is for oos12 and oos13
Click to expand...
Click to collapse
How do i bring back debloated apps?

Salilsarkar said:
How do i bring back debloated apps?
Click to expand...
Click to collapse
i will attach a revert script

Salilsarkar said:
How do i bring back debloated apps?
Click to expand...
Click to collapse
thread is updated, you can download revert script and run it

list of debloated apps?

Trojan.Malware.300983.susgen
VirusTotal
VirusTotal
www.virustotal.com

bluebirdsysx said:
​
aosp.bat is for asop roms(A12 and A13)
Click to expand...
Click to collapse
Bro wants to debload aosp

Y'all's customizations a killing me here....deblote with ADB......

bluebirdsysx said:
i will attach a revert script
Click to expand...
Click to collapse
There's a system recovery app made by OnePlus I can link it to you if you need it and let you reinstall any system app if not there's an app manager that will let you reinstall apps that are still left on your system because you can't actually fully uninstall them or if you have ADB I can show you how to go through your system and reinstall them via the actual file on your phone