[Recovery][15.03.18][3.2.1-1][SM-G965F/FD/N] TWRP star2lte - Samsung Galaxy S9+ ROMs, Kernels, Recoveries, & Ot

ONLY FOR EXYNOS MODELS (SM-G965F/FD/N)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This will trip knox to 0x1, your phones warranty will be voided, flash at your own risk. Also, this process will wipe your personal data!
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
DOWNLOAD:
Download via Mega
BUGS:
- Samsung encryption is NOT supported
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
DONATION:
Via PayPal
XDA:DevDB Information
TWRP star2lte, Device Specific App for the Samsung Galaxy S9+
Contributors
Tkkg1994
Source Code: https://github.com/Tkkg1994/android_device_samsung_star2lte
Version Information
Status: Stable
Current Stable Version: 3.2.1-1
Stable Release Date: 2018-03-15
Created 2018-03-15
Last Updated 2018-03-19

Changelogs
CHANGELOG for 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
CHANGELOG for 3.2.1-1:
* Added omc partition to the mount table
* Since we are using treble here I enabled that you can flash img files to the system/vendor partitions
* Fixed USB OTG issues

Reserved

Great man, thank you for your work!

@Tkkg1994
AWESOME!!!!Thanks for your work!!!
Greets Maik

@Tkkg1994 once again you are the man !!

Awesome Luca!

@Tkkg1994
Nice work mate
Good day

At What Point Do We Flash The Dm No verity opt. Could Anybody Explain The Proper Order Of Procedure If Possible Please And Many Thanks Great Work Luca.

Great work :good:
Development would not be possible without TWRP, the ROM's party has just begun

There is no "OEM unlock enabled" in developer option . sm-965f

mevorach said:
There is no "OEM unlock enabled" in developer option . sm-965f
Click to expand...
Click to collapse
for me its visible. German DBT G965F/Duos

I have R16NW.G965FXXU1ARC5 Build number , and no "OEM unlock enabled" in developer option

There's already a small update for this TWRP:
- Added omc partition to the mount table
- Since we are using treble here I enabled that you can flash img files to the system/vendor partitions
- Fixed USB OTG issues
Also I made a stock kernel which disables force encryption and dm-verity! Flash it as img to the boot partition!
TWRP 3.2.1-1
Patched stock boot.img
Guys from what I heard magisk 16.1 was causing bootloops!

mevorach said:
There is no "OEM unlock enabled" in developer option . sm-965f
Click to expand...
Click to collapse
My Dutch Exynon S9+ came out of the box with unlocked bootloader. If you own a non Amerikan Exynon device than i guess yours is unlocked as well.

Thank you - great to see you here!
Am I correct in understanding that When I flash TWRP - Wipe/Format Data - I can then flash your modified boot image and I don't have to flash the separate No Verity file found on other threads?
I know this makes me look stupid, but I am just wanted to be sure i understood correctly.
Thank you for all the development you do!
---------- Post added at 04:52 PM ---------- Previous post was at 04:48 PM ----------
mevorach said:
There is no "OEM unlock enabled" in developer option . sm-965f
Click to expand...
Click to collapse
In case you were not aware, If you don't see OEM unlock in Developer Settings it means you are locked out from flashing anything for 7 days. (Exactly 7 days, 168 hours. After that time frame is over - reboot your phone and go into developer settings and you should see OEM unlock there. Once you have it turned on - flash twrp and immediately afterwards, flash the RMM state Fix to make sure it doesn't happen again. If you ever flash new firmware in odin, it will very likely start the clock again and you will have to wait 7 days.
While you are waiting, you can turn off the phone - reboot if you need to - but don't remove the sim card and leave data on.
You can find the RMM State fix here with a detailed explanation about what it is - here:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Good Luck

BokkieAndijk said:
My Dutch Exynon S9+ came out of the box with unlocked bootloader. If you own a non Amerikan Exynon device than i guess yours is unlocked as well.
Click to expand...
Click to collapse
Thanks, but how do you know that your phone is unlocked ? do you miss the "oem unlock on" from developer too ?

At the moment mine is still in bootloop cause I'm downloading the stock Rom so I can't show you a screenshot but I'm sure I saw it in developer options last morning.

mevorach said:
Thanks, but how do you know that your phone is unlocked ? do you miss the "oem unlock on" from developer too ?
Click to expand...
Click to collapse
Not all Exynos are "unlocked". I dont knwo why some are and some are not - but the light at the end of the tunnel is that if you don't see OEM unlock now, if you wait 7 days - you will. You will just need patience. There isn't anything else you can do about it unfortunately.

From my findings it's Magisk that is causing the bootloop, I have tried 16.0 & 16.1 and also going back to 15.3 all causing bootloop. Think we need to wait a little for root :good:

Related

[RECOVERY] [OFFICIAL] TWRP for Shield Portable

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP for Shield Portable, Tool/Utility for the Nvidia Shield
Contributors
Steel01
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Created 2016-06-01
Last Updated 2016-05-31
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Steel01 said:
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Click to expand...
Click to collapse
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
r3pwn said:
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
Click to expand...
Click to collapse
Yeah, the only thing that changes is the aspect ratio, not the orientation.
Thank you! Thank you!
Just updated to 110, and installed TWRP you posted. All went perfect.
Just FYI, sometimes when I flash a new TWRP recovery, it doesn't take the first time, so I just flash it a few times, then test to see if it took, if it didn't take, I flash a few times more until it finally flashes.
Is there a specific key combo you can use to go right into recovery? Right now, I boot into the bootloader by pressing and holding the back, home and nvidia buttons till it boots into the bootloader, then I select recovery to go into TWRP. Just wanted to know if there's was a key combo to go directly into recovery.
Thanks again for providing and posting the latest TWRP for the Portable!!
Hello, quick question. I have a previous version of TWRP installed and want to update to the new one.
Is it possible to apply the OTA to 110 with this TWRP or do I need the stock bootloader?
If I need the stock one, does anyone have a link to it? I didn't make a backup, unfortunately
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Steel01 said:
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Click to expand...
Click to collapse
Ah, I didn't know nvidia published those files like that. That's actually really great!
I'm all up to date now, including the latest TWRP
Hmm I tried TWRP 3.1 from the TWRP website and the touch interface doesn't work. Also, 3.0.2 seems to have problems mounting and wiping data?
Meh, okay. I saw a similar touch problem on a local twrp build. I've requested that the build be removed from the official site. I'll look into the problem when I have time.
Haven't had any trouble on 3.0.2 myself. Did you enable encryption or adopted storage in your ROM?
Great, thanks!
I didn't enable encryption, and it was the latest stock rom. I'm not really sure what happened. It just seemed to be having trouble mounting and wiping a few partitions on the stock system rom, so I flashed the 3.0.0.0 TWRP from the multirom. I seem to recall that having issues wiping too though. However, now that I've flashed LineageOS onto the system partition, I don't get any errors with 3.0.0.0 anymore. I haven't updated to 3.0.2.0 to see if the errors are gone in that build (nor do I want to wipe anything at this point).
As I wrote in the LineageOS thread, I had the same problem with touchscreen. I was hoping to solve the non working touchscreen problem during Aroma OpenGapps install.. is there any hope it gets solved? I think it would be very useful to be able to choose exactly what to install on the Shield, considering its little system partition.
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
astuermer said:
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
Click to expand...
Click to collapse
I too have this issue. Seems they messed up screen as portrait mode.
I see the problem with touch on the newer builds. Would have sworn I had at least one of those removed due to issue, but it apparently came back. Looking into updating all the internal files for 7.1. Working on testing and fixing that right now. The problem is that the touch screen userspace is trying to start before selinux is set to permissive by twrp. So, I have to make sure everything is labelled correctly and that's causing issues. If I'm lucky, I'll be uploading a test build later today. But as with all this type of work, I can't 100% guarantee anything.
astuermer said:
Landscape would be nice.
Click to expand...
Click to collapse
The rotation code no longer exists, it was deemed too slow and hacky. I have to set it up in portrait or not at all, unfortunately.
Edit:
So, not having much luck with making it play nice on default settings. Here's a build with selinux explicitly disabled and touch works as expected. As I have time, I will continue to work on this and get it upstreamed. For the moment, use this 3.1.1 build.
twrp-3.1.1-0-unofficial-roth.img
Finally got around to pushing updates to official twrp. So if you've had issues in the past, please try again. Should be easier to test and fix stuff now that I've got all that pushed.
Side Note: This is fully a 7.1.1 recovery and build. Blasted recovery from N works better than the roms themselves...
Some updates have been pushed for this. 3.2.1.0 has been release as of a few hours ago. If any issues are found, please report.
When trying to flash the 2018-02-11 LineageOS nightly with 3.2.1.0, I get the following error;
Code:
Updating partition details...
...done
Full SELinux support is present.
Installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Checking for digest file...
Skipping Digest check: no Digest file found
Verifying zip signature...
Zip signature verified successfully,
[B]This package is for device: roth; this device is .[/B]
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Updating partition details...
...done
The flash does not proceed beyond this point - apparently can't identify the device type (see bolded text above). If I repeat the process using version 3.1.1-2 or version 3.0.2.0 it works fine, though.
Let me know if you'd like me to pull any logs etc

[ROM][S9+/S9][LineageOS 17.1][UNOFFICIAL][05-06-20][OTA]

What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020
temp
Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English
Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.
so everything good other than Android Auto? Well done!
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.
How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:
..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?
Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.
Great, glad all went good for you
Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse
Great work! ROM works great, even Google pay is working good!
I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel
Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!
oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse
Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.

[ROM][fajita][12]ArrowOS 12.0[DEAD]

Code:
*** Disclamer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
This is the ArrowOS for OnePlus 6t
Click to expand...
Click to collapse
Installation instructions
1. Install R Stock Rom onto your phone , follow some tutorial you can find in this forum
2. Flash boot.img and dtbo.img by typing fastboot flash boot boot.img and fastboot flash dtbo_a dtbo.img and fastboot flash dtbo_b dtbo.img
3. Wipe your userdata by typing fastboot erase userdata
4. Reboot the phone and immeditly do the recovery key combination
5. In Lineageos recovery select install and then sideload from adb
6. On your computer type adb sideload pathtotheromzip and press enter
7. The rom should now be flashed , flash gapps and other mods like magisk the same way
Click to expand...
Click to collapse
Download
ROM
RECOVERY
Click to expand...
Click to collapse
Changelog
Code:
Current changelog:08.11.2021
[note] 2nd Release of ArrowOS 12.0
[new] Audio works now , wifi works now , userdebug build
[changed] userdebug build now
[fixed] audio wifi
Older changelogs:
Click to expand...
Click to collapse
Code:
Current changelog:05.11.2021
[note] 1st Release of ArrowOS 12.0
[new] Android 12 R
[changed]
[fixed] Rom boots into OS
FAQ
What doesnt work ?
fingerprint,,and maybe others
This rom is for fajita only
VOLTE DONT WORK
For Gapps i recommend NikGapps
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@SGCMarkus
@LuK1337
Sources
Code:
[URL="https://github.com/J0SH1X/android_kernel_oneplus_sdm845"]Kernel[/URL]
[URL="https://github.com/J0SH1X/android_device_oneplus_sdm845-common"]Common[/URL]
[URL="https://github.com/J0SH1X/android_device_oneplus_fajita"]Device[/URL]
[URL="https://github.com/J0SH1X/proprietary_vendor_oneplus"]Vendor[/URL]
Wow first 12 build. But will be wait till fixing things by dev as described. Best of luck.
omg this is a good start
Thanks waiting
I don't see in the instructions what to do with the rootfs.tar.gz file from the Recovery link.
That's a good start.
digidude512 said:
I don't see in the instructions what to do with the rootfs.tar.gz file from the Recovery link.
Click to expand...
Click to collapse
you dont , the rootfs.tar.gz is for running full desktop ubuntu on oneplus 6t
small update audio is fixed wait for next build maybe even more till then
J0SH1X said:
small update audio is fixed wait for next build maybe even more till then
Click to expand...
Click to collapse
wifi fixed fp kinda works but not quite yet
Don't understand this thing
The flashing instructions you have listed don't seem to be working for me. When i enter recovery im still in stock recovery. the dtbo.img is flashed to both slots too as well as boot.img.
koobie777 said:
The flashing instructions you have listed don't seem to be working for me. When i enter recovery im still in stock recovery. the dtbo.img is flashed to both slots too as well as boot.img.
Click to expand...
Click to collapse
try to flash boot to slot a and b , also dont expect any touch recovery its normal e3 with some extra stuff added or do you mean oneplus recovery?
New Release with fixed audio and wifi bt audio may or may not work , also fingerprint sensor will be detected now but it fails to illuminate the sensor so systemui will crash
Release fajita-20211108 · J0SH1X/Lineage-OTA
host for json response file for supporting ota updates on unoffcial lineageos || EOL FIND ANOTHER IDIOT TO DO YOUR **** - Release fajita-20211108 · J0SH1X/Lineage-OTA
github.com
J0SH1X said:
try to flash boot to slot a and b , also dont expect any touch recovery its normal e3 with some extra stuff added or do you mean oneplus recovery?
Click to expand...
Click to collapse
Yeah it booted to OnePlus recovery, your instructions though mention using the recovery buttons command I tried vol. Down + power but I also tried just booting to recovery from bootloader, both booted to OnePlus recovery. I'll try to flash boot to both slots tonight. Testing out PE A12 GSI today while I'm at work. I'll have to MSM back to stock first to try your build out. I'll also test out bugs if I get it to boot and throw a logcat up.
Hey dev do you have any telegram group we people can hope in and ask for doubts xda seems to slow the process of asking doubts id someone stuck at recovery.
I will highly appreciate of telegram is there
Tushi001 said:
Hey dev do you have any telegram group we people can hope in and ask for doubts xda seems to slow the process of asking doubts id someone stuck at recovery.
I will highly appreciate of telegram is there
Click to expand...
Click to collapse
LineageOS 19 - OnePlus 6T
Group to discuss about the Alpha Builds of LineageOS 19 based on Android 12 for the OnePlus 6T.
t.me
Can get this to boot, but can't change the recovery from the standard OnePlus recovery. As a result, sideloading .zip files fails because of signature verification (I can't see any option to disable that in the standard recovery).
Wifi is also still flaky on the latest build. It did connect once but now won't reconnect.
Happy to see arrow OS on fajita! thank you
MrUrgit said:
Can get this to boot, but can't change the recovery from the standard OnePlus recovery. As a result, sideloading .zip files fails because of signature verification (I can't see any option to disable that in the standard recovery).
Wifi is also still flaky on the latest build. It did connect once but now won't reconnect.
Click to expand...
Click to collapse
okay can you maybe provide logs or so , i dont see any iusse with wifi anymore
Did Google open source wallpaper based color themeing? I didn't keep a track recently and wanted to know id its included in custom roms like this one.

[Recovery][TWRP 3.7.0][Unofficial][Mi 10T/Pro]

Please note that it is not mine if you are here, it means you know what you are doing and are solely responsible for what you are doing.
I see some users can't find twrp for this device and some links are broken. So I share here the last unofficial twrp developed by skkk. All credits and thanks goes to him.
If you have no recovery yet and you are not rooted, you need to use the usual adb commands: fastboot boot <twrp.img>
If you're rooted, you can use the official twrp app[https://play.google.com/store/apps/details?id=me.twrp.twrpapp ] Grant him root rights and flash the twrp image or flash directly from recovery for an update...
Download link
128 MB file on MEGA
mega.nz
or unzip this file to have twrp.img
*update January 15, 2023 (twrp.V-6.8)
*update January 17, 2023 (twrp.V-6.9)
*update January 18, 2023 (twrp.V-7.0)
*update January 30, 2023 (twrp.V-7.1)
*update February 2, 2023 (twrp.V-7.2)
*update april 25 , 2023 (twrp.V-7.7)
Thanks ............​
thanks for sharing and caring for us user of mi 10t/pro
If you have problem with data decryption please use this version twrp (credit to lilydess) and Flash DFE after your ROM.
Although it's version 3.6.2 seems to work better especially on A13 which has even more restrictions than A12.
Note : Unzip this file you will have Twrp.img+DFE.zip
• EROFS Support
• September 8th 2022
• Source Code
Commits · lolipuru/twrp_device_xiaomi_apollo
Contribute to lolipuru/twrp_device_xiaomi_apollo development by creating an account on GitHub.
github.com
Full House said:
If you have problem with data decryption please use this version twrp (credit to lilydess) and Flash DFE after your ROM.
Although it's version 3.6.2 seems to work better especially on A13 which has even more restrictions than A12.
Note : Unzip this file you will have Twrp.img+DFE.zip
Click to expand...
Click to collapse
thanks a lot for this, more powerrr to you sir
abrakadabraham said:
thanks a lot for this, more powerrr to you sir
Click to expand...
Click to collapse
Thank you for being grateful, many here are not grateful more than 100 people have downloaded not even 10 people thanked that's how human ingratitude.
nice work bro keep it up
Full House said:
Please note that it is not mine if you are here, it means you know what you are doing and are solely responsible for what you are doing.
I see some users can't find twrp for this device and some links are broken. So I share here the last unofficial twrp developed by skk. All credits and thanks goes to him.
If you have no recovery yet and you are not rooted, you need to use the usual adb commands: fastboot boot <twrp.img>
If you're rooted, you can use the official twrp app[https://play.google.com/store/apps/details?id=me.twrp.twrpapp ] Grant him root rights and flash the twrp image or flash directly from recovery for an update...
Download link
128 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thanks a lot!!
Thank you so much, thanks for sharing useful TWRP.
Thanks for this amazing recovery
Can it decrypt data on android 12? or even android 13? D:
Yes
plakonn said:
Can it decrypt data on android 12? or even android 13? D:
Click to expand...
Click to collapse
I recommend skk twrp for A12 roms and miui based roms it can decrypt but for A13 lilydess twrp is recommended.
big thanks to you, other recovery thit not stick got twrp bootloop this recovery works super europe xiaomi MI 10 t pro 5G thanks very happy
Full House said:
I recommend skk twrp for A12 roms and miui based roms it can decrypt but for A13 lilydess twrp is recommended.
Click to expand...
Click to collapse
where i can get lilydess twrp? (edit: i mean, from where did you get it?) i cant find it
edit2: it can rly decrypt storage, right? so i can use it without dfe and just write pin into twrp (or remove pin before rebooting to twrp)
plakonn said:
where i can get lilydess twrp? (edit: i mean, from where did you get it?) i cant find it
edit2: it can rly decrypt storage, right? so i can use it without dfe and just write pin into twrp (or remove pin before rebooting to twrp)
Click to expand...
Click to collapse
on telegram.
It depends on the ROM so yes in some cases no need for DFE flash if the ROM does not force encryption.
Yes you can boot to twrp with lock enabled.
Full House said:
on telegram.
It depends on the ROM so yes in some cases no need for DFE flash if the ROM does not force encryption.
Yes you can boot to twrp with lock enabled.
Click to expand...
Click to collapse
so there is no way i can have force encryption and twrp at the same time? (i need encrypted storage but i would like too keep ability to flash zips, ota updates etc. Can pixel experience recovery do it? (with lockscreen pin removed) i mean using pc "adb sideload" command...
plakonn said:
so there is no way i can have force encryption and twrp at the same time? (i need encrypted storage but i would like too keep ability to flash zips, ota updates etc. Can pixel experience recovery do it? (with lockscreen pin removed) i mean using pc "adb sideload" command...
Click to expand...
Click to collapse
I only use twrp ask pixel dev experience.
Anyway some recommend the use of their recovery even if it works with twrp this is due to the fact that there is no official twrp for Apollo.
indeed even if twrp cannot access internal data we can always use adb sideload or usb otg to flash what you want, the only problem in this case will be to access to data/adb/modules in case of bootloop and no twrp backup.
So bootloops caused by magisk module are solved how? By formatting everything?
Full House said:
I only use twrp ask pixel dev experience.
Anyway some recommend the use of their recovery even if it works with twrp this is due to the fact that there is no official twrp for Apollo.
indeed even if twrp cannot access internal data we can always use adb sideload or usb otg to flash what you want, the only problem in this case will be to access to data/adb/modules in case of bootloop and no twrp backup.
Click to expand...
Click to collapse
I dont want to annoy you any more... Is there any guide for this? (how to work with this kind of twrp?). I'm lowkey confused by the fact i can flash from otg but at the same time i can not view storage. ( i managed to destroy system once i tried to flash somethin so i started using DFE.zip but now i need encryption for work app...)
i used to know how it works but i forgot. Thanks for help 🫡

[ROM][PORT][13][One UI 5.1][A51 Port][M21 2020/21] TukiRom V1.3

Tuki Rom v1.3
Ported from Galaxy A51
Important notes:
Do not blame me if your sdcard dies or getting bootloop when you have data and for getting fired because alarm clock has been failed
Features:
Highly debloated for perfomance
Deleted samsung services
Feels like AOSP
Pseudo stereo sound
60Fps front camera
Build.prop Tweaks
Floating feature tweaks
Very smooth and fast
Csc tweaks
Taskbar from Fold devices
Bugs:
Pro mode
Nfc
Found any, tell me
Telegram channel
Download For Galaxy M21 (Mega)
Download For Galaxy M21 (TeraBox)
Please note that i'm using Prism and Optics from m31 and If you got bootloop on M21 please send logs
Kernel source
Credits:
Flylarb For helping and for T vendor
Royna For kernel
Screenshots:D
Change log:​
Spoiler: V1.0
Initial build of TukiRom
Spoiler: V1.1
Added taskbar
Even more debloated
Added more Floating feature tweaks
Added Csc tweaks
Even more smooth
Fixed mic
Spoiler: V1.2
Custom Wallpaper-res
Fixed More connection settings bug
Added some build.prop tweaks
Initial build for M21
Spoiler: V1.3
Added Image clipper
Added Live blur
Updated walpaper-res
Fixed Data usage bug
Improved perfomance
Improved Battery life
Added China Smart Manager
Added advanced settings menu
Added some build.prop tweaks
Added selectible tweaks in installer
Reserved
Thanks for making this dev. The community was waiting One Ui 5 and you made that happen. Give some details about kernel in the change log.

			
				
Fun fact when I 1st open the rom and saw the task bar I thought it got glitch then I turn the task bar off and then full AOSP rom with one ui , great .
Ultra fast.
Taskbar enabled by default, cannot hide navbar so they are multiplying buttons.
NFC not working.
How can I hide root for banking apps etc?
kwasior500 said:
How can I hide root for banking
Click to expand...
Click to collapse
Flash this file i attached below on magisk and wipe data for gms and playstore

			
				
i thick we should try magisk 26.1 in it. There are many fixes available like safety net fix , magisk hide , lsposed module like girgit and more.
I am currently on LPOS reborn for m21
Can i dirty flash it???
BobaBoi69 said:
I am currently on LPOS reborn for m21
Can i dirty flash it???
Click to expand...
Click to collapse
You only can do clean flash
Pachadomenic said:
You only can do clean flash
Click to expand...
Click to collapse
Soo do i have to flash the stock rom and reflash this one??
Wait is there any one ui 5.1 core for samsung m21??
BobaBoi69 said:
Soo do i have to flash the stock rom and reflash this one??
Wait is there any one ui 5.1 core for samsung m21??
Click to expand...
Click to collapse
Device used M21 2020 binary 3
Things you need to download before going for the process of installation twrp v3.7.0 , tukirom zip 1.2 , stock device firmware, odin v3.14.4
I have put the tukirom zip in my SD card for flashing from twrp.
Installation Process
Step 1 Unlock the Bootloader or oem unlock from developer option in settings. (Search for Bootloader unlocking in m21 you will find the solution on internet)
Step 2 Boot into Download mode (Search for download mode in m21 you will find the solution on internet)
Step 3 open ODIN software in administration mode on the pc or laptop.
Step 4 flash the stock firmware. ( it is easy , but if need help say it , I will add it )
Step 5 after flashing the stock firmware the device will reboot and boot into system. Fill up all the details as per your requirements. And after the 1st you have to unlock again the developer option. (You know how to do that right ! )
Step 6 view in developer option if the oem unlocking option is visible or not . If not then exit from setting the connect your device with a wifi and then see if it is visible now or not. If not then restart the phone and connect to wifi 1st and then go to setting as see if oem unlocking is visible.
Step 7 after you are sure oem unlocking , boot into Download mode . And use the odin software to flash the twrp.
Step 8 Connect the device which is in download mode to the pc if not connected.
" Added " log will show .
Click on options on the side of log icon and unclick reboot.
Step 9 Click on AP and and select the twrp v3.7.0 zip file . (M215FXXU3CWB1 twrp , I had used this varient for my device.)
Step 10 Click on start and within a shot amount of time twrp will be flashed into your device. After the successful flash press volume down and power button for 8 sec and then direct press volume up and power button until twrp page shows up.
Step 11 Flash the rom from SD card
Step 12 Wipe/Format data
Step 13 Reboot
Please note that first boot will be long and
And compele setup without Wifi.
I have done the complete setup with wifi.
Task bar is automatically on on the 1st boot so you have to manually turn off it.
BobaBoi69 said:
Soo do i have to flash the stock rom and reflash this one??
Wait is there any one ui 5.1 core for samsung m21??
Click to expand...
Click to collapse
I was flashing directly from crdroid9
kwasior500 said:
I was flashing directly from crdroid9
Click to expand...
Click to collapse
Did that work fine !?
I'd mentioned it if...
Pachadomenic said:
Tuki Rom v1.2
Ported from Galaxy A51
Important notes:
Do not blame me if your sdcard dies or getting bootloop when you have data and for getting fired because alarm clock has been failed
Features:
Highly debloated for perfomance
Deleted samsung services
Feels like AOSP
Pseudo stereo sound
60Fps front camera
Build.prop Tweaks
Floating feature tweaks
Very smooth and fast
Csc tweaks
Taskbar from Fold devices
Bugs:
Pro mode
Nfc
Found any, tell me
Telegram channel
Download For Galaxy M21
Please note that i'm using Prism and Optics from m31 and If you got bootloop on M21 please send logs
Kernel source
Credits:
Flylarb For helping and for T vendor
Royna For kernel
Screenshots:
Click to expand...
Click to collapse
Can it be install binary 2 device!?
Ajaythepower1606 said:
Can it be install binary 2 device!?
Click to expand...
Click to collapse
try
Ajaythepower1606 said:
Device used M21 2020 binary 3
Things you need to download before going for the process of installation twrp v3.7.0 , tukirom zip 1.2 , stock device firmware, odin v3.14.4
I have put the tukirom zip in my SD card for flashing from twrp.
Installation Process
Step 1 Unlock the Bootloader or oem unlock from developer option in settings. (Search for Bootloader unlocking in m21 you will find the solution on internet)
Step 2 Boot into Download mode (Search for download mode in m21 you will find the solution on internet)
Step 3 open ODIN software in administration mode on the pc or laptop.
Step 4 flash the stock firmware. ( it is easy , but if need help say it , I will add it )
Step 5 after flashing the stock firmware the device will reboot and boot into system. Fill up all the details as per your requirements. And after the 1st you have to unlock again the developer option. (You know how to do that right ! )
Step 6 view in developer option if the oem unlocking option is visible or not . If not then exit from setting the connect your device with a wifi and then see if it is visible now or not. If not then restart the phone and connect to wifi 1st and then go to setting as see if oem unlocking is visible.
Step 7 after you are sure oem unlocking , boot into Download mode . And use the odin software to flash the twrp.
Step 8 Connect the device which is in download mode to the pc if not connected.
" Added " log will show .
Click on options on the side of log icon and unclick reboot.
Step 9 Click on AP and and select the twrp v3.7.0 zip file . (M215FXXU3CWB1 twrp , I had used this varient for my device.)
Step 10 Click on start and within a shot amount of time twrp will be flashed into your device. After the successful flash press volume down and power button for 8 sec and then direct press volume up and power button until twrp page shows up.
Step 11 Flash the rom from SD card
Step 12 Wipe/Format data
Step 13 Reboot
Please note that first boot will be long and
And compele setup without Wifi.
I have done the complete setup with wifi.
Task bar is automatically on on the 1st boot so you have to manually turn off it.
Click to expand...
Click to collapse
i know all this in root detail bruh
all i asked was do i need to flash stock rom or a custom rom update dirty flash will do it

Categories

Resources