CTR Recovery for Galaxy A5
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands
Related
Hello
This is TWRP v 2.8.1.0 for the S4 Mini. It works for the I9195 - I do not know if it works for similar devices.
The problem was that TWRP after version 2.7.1.0 did not boot up - the phone tried to enter recovery mode but eventually booted into android.
This is because of commit https://gerrit.omnirom.org/#/c/8471/ which does not seem to work nice with the S4 Mini.
DISCLAIMER : You apply this recovery at your own risk - if something breaks or bricks I am not responsible
IMPORTANT NOTE :
a) The attached file is NOT a flashable ZIP and I will not provide one. You have to unpack the attached file and use heimdall or dd. If someone wants to provide a flashable zip - I am fine with that.
b) There is no F2FS support.
c) I do not know if there are still problems with the recovery sometimes not booting up - I tried it a couple of times and it worked every time. Tell us if you experience booting problems.
d) I am no coder - so I cannot help with things like encryption, luks or similar wishes.
How to install:
a) Boot your phone to download mode
b) Connect phone to PC
c) Get root on your PC
d) Unzip attached ZIP file
e) Check md5sum
f) heimdall flash --RECOVERY recovery.img --no-reboot (dd should work as well - take care of the right partition)
Thanks goes to:
Teamwin
OliverG96
_that
Additional information:
If you want to build this by yourself from sources open file twrp-functions.cpp and search for line:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
You can change it like that:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
{
return 0;
std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;
This should fix the problem. According to one of the developers there should also be a flag for specifying a brightness file that one can probably set to /nobrightness.
It works great on my I9195 !
From your recovery, i created the Odin version and flashed it.
Thank you very much.
I attach the Odin version of your recovery (Instructions: unzip the .zip file, and flash the .tar.md5 file with Odin 3.09 into AP field)
Recovery flashable ZIP version of TWRP 2.8.1.0 attached.
Mounting both (Internal and External) doesnt work
mike_san said:
Mounting both (Internal and External) doesnt work
Click to expand...
Click to collapse
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
thomson.aa said:
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
Click to expand...
Click to collapse
I confirm this.
I tried to mount and unmount System, Data and micro Sdcard... all ok.
Will it work with f4k kernel ?
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Works great so far, noticed only one (minor) issue:
I need to use encryption for my phone and for its backups as well (I'm a sysadmin and my phone is fully equipped to access my datacenter). When using keyboard to type encryption/decryption passwords, somethimes I hit one key and completely another key gets pressed, can't be due to fat fingers because wrong key that gets pressed is usually very far from the original one. This was very iritating sometimes since I needed to type passwords for 3-4 times in a row for them to work. Figured out how to prevent this, I look at whole keyboard carefully on every keystroke and I'm usually able to see when it gets buggy and hits wrong key (keystroke animation is trigerred), but this isn't very fast or comfortable...
I think I had the same problem with early versions of TWRP 2.7 posted here but it has been resolved in newer ones. Otherwise, works as a charm, if someone added full F2FS support it would be totally perfect
PS If my memory serves me well, fix was build.prop related.
ericlnu said:
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Click to expand...
Click to collapse
works fine on aicp, Thanks
s.basketbuild.com/devs/F4k/twrp/serranoltexx
this one have F2FS
All CM13 and RR releases we have so far are using pretty old China Dev MIUI v.6.6.30 as base not even listed on Xiaomi Downloads anymore. This as some of us know is the cause of all bugs we've had with these custom ROMs and were fixed by replacing vendor files from newer MIUI versions. On top of that some helium users cannot reboot to recovery from Android, phone doesn't power off... things like that... which most likely is due to using the wrong hydrogen kernel in this builds. Some users including me are experiencing no data going thru on good connection... Not gonna even mention VoLTE etc. So we still have bugs...
The vendor files and kernel that comes from MIUI as base are the main part that makes the hardware working flawlessly with the Android OS. These files are proprietary files with closed code, we can't change them so we have to rely on whatever Xiaomi do to optimize device performance. But we can choose which version to use and that is my goal here... Test and find the best set that works with custom ROMs.
Here we go... I have been testing the latest Global MIUI as base for two days now and so far haven't seen any issues at all. That doesn't mean no bugs... More time and testing is needed. But at least they are not any worst than what we are using now.
The common sense and logic is(fixed bugs proved that) vendor files and kernel from latest stable Global MIUI for the particular device should have more bug fixes and optimizations for the world out of China(I hope)... So using the best of my knowledge I compiled these two sets for:
HYDROGEN:
Based on latest Mi Max official Global MIUI v.8.0.1 (miui_MIMAXGlobal_V8.0.1.0.MBCMIDG_3657fef420_6.0.zip)
Download: vendor-base801MG_update-HYDROGEN.zip
HELIUM:
Based on latest Mi Max Prime official Global MIUI v.8.0.3 (miui_MIMAX652Global_V8.0.3.0.MBDMIDG_2da4c7e9db_6.0.zip)
Download: vendor-base803MG_update-HELIUM.zip
These packages are not recovery flashable zips!!! Keep reading for install instructions!
The install will get all vendor proprietary files I know of, firmware and kernel properly updated for the device code. Let's hope we get the better and latest from Xiaomi...
INSTALL INSTRUCTIONS:
MAKE TWRP BACKUP OF SYSTEM AND BOOT PARTITIONS BEFORE ANYTHING TO REVERS CHANGES IF YOU NEED TO!!!
The installation process is a little bit involving due to replacing the kernel in the actual installed boot.img in your device. I can't supply universal updated boot.img because they might be different from one release to another. I want to update what you already have. Did my best to make it user-friendly as I can without coding special app or something. Thanks to this guy whoever he is for the boot.img tools https://github.com/xiaolu/mkbootimg_tools.
Follow the steps and you should be fine:
1. Download the appropriate zip for your device code and unzip it to the root of your internal storage. You should end up with /sdcard/vendor_update folder;
2. Open your favorite terminal emulator app and execute the following commands one at a time pressing ENTER after each line:
Code:
su
hit ENTER
Code:
cp /sdcard/vendor_update/vendor-updater.sh /data/local/tmp/
hit ENTER
Code:
chmod 777 /data/local/tmp/vendor-updater.sh
hit ENTER
Code:
sh /data/local/tmp/vendor-updater.sh
hit ENTER
Alternatively you can USB connect your phone to computer and run the same commands from adb shell.
For HYDROGEN users:
That's all you have to do. The script will update your kernel and automatically will reboot phone to recovery and update vendor files so save your work before running the commands!
For HELIUM users:
Due to that can't reboot recovery bug you have to reboot manually by holding POWER and VOLUME+ buttons or fastboot method... The vendor zip will be flashed automatically and phone reboots back to system. If not, install /sdcard/vendor_update/vendor_update-HELIUM.zip manually and that's it.
Simple stuff if you decide to test these packages...
To verify update you should see kernel and baseband versions in About Phone changed like in the attached hydrogen screenshot. I can't test helium so they might be a little different. Check WiFi also... If you can turn it on and works all is good...
Helium users see if you can reboot to recovery from Advanced Power Menu, check if you can Power OFF your phone etc... the usual bugs.
Let see if these updates change anything for good or bad.
Happy testing!:good:
EDIT: Looks like 3G bug is still present in latest MIUI modem files. Flash CM_3G_fix.zip and keep the rest of the update if 3G bug is back.
Thanks a lot.
You are welcome!
Please guys lets not quote the whole OP... It takes so much screen...
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Maybe not... Give me a mnute...
That's what happens when you code unix script on windows and forget to convert it.
@JulianJenner
EDIT: FIXED(i think)...Try now and let me know it works or not!? Helium feedback appreciated...
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
JulianJenner said:
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
Click to expand...
Click to collapse
Did you redownload the fixed zip? Do you have the "/sdcard/vendor_update" folder with the files in it?
Make sure you copy text line by line hitting ENTER after each one!!! That's 4 lines... su... cp... chmod... sh...
Hydrogen works for me... Can't test helium unfortunately...
Terminal running successfully.
Phone reboot.
But my BB and Kernel version did not changed...
Yours Mon Aug 29
Mine Wed Jun 29
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No. I will download again. A.S.A.P.
---------- Post added at 11:18 PM ---------- Previous post was at 11:01 PM ----------
Working.
It was my fault.
"...line by line hitting ENTER after each one..."
Firstly I did not understand it.
I pressed Enter after at the end once...
Click to expand...
Click to collapse
Phew... I thought I screwed up again...
Run this in terminal emulator:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Upload /sdcard/boot.img somewhere... I will update kernel and you will flash it... Let see if version changes. Maybe Xiaomi haven't updated helium kernel yet!? But it is definitely different from the hydrogen latest one byte by byte...
Baseband was probably already updated if you are running ajsmsg78's RR.
I did.
Upload...
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
I did.
And now?
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Go to sdcard and you will find boot.img in there, upload it somewhere and give me the link...
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Just checked helium kernel with hex editor and the date is Fri Sep 2 23:22:31 CST...
Have no idea why it didn't update since script did not throw any error, right? Did the phone reboot to recovery and flashed the vendor zip?
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
Did the phone reboot to recovery and flashed the vendor zip?
Click to expand...
Click to collapse
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
Where is this vendor zip ( okay, I find it. vendor_update-HELIUM.zip)? Can I flash it from TWRP?
I have stock recovery, I used TWRP from Fastboot mode 'fastboot boot recovery.img' command...
Click to expand...
Click to collapse
Yes you can but first kernel has to get updated or wifi won't work.
And thats not the point... I want to see why script did not do the job but I will debug it with someone else...
Here is updated kernel link removed
Download it to /sdcard/boot_updated.img and run this in terminal:
Code:
su
hit enter
Code:
dd if=/sdcard/boot_updated.img of=/dev/block/bootdevice/by-name/boot
hit enter
After that reboot to recovery and flash that vendor_update-HELIUM.zip
Post versions, please...
OK. I think solved by myself.
Ran script again in adb shell.
And when phone tried to reboot recovery.
I stopped it with buttons.
Reboot in Fastboot mode with buttons.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
Click to expand...
Click to collapse
Aaah, I got it... that can't reboot recovery bug for helium ... I will change script to not boot automatically and let helium users boot to TWRP manually and it will flash vendor zip automatically. Didn't get that bug under consideration.
Thank you for opening my eyes Hate when I can't test things...
This is mine, helium, seems it has been success, I use the one you posted at the first.
@nijel8... your work is a hard work!
I am proud to be working with you.
laolang_cool said:
This is mine, helium, seems it has been success, I use the one you posted at the first.
Click to expand...
Click to collapse
Great...:good: Seems like you don't suffer from hydrogen kernel.
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock
this twrp will work on 7.1.2 ? i'm now on aex rom
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!
CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212
teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
It's possible to make password for twrp
DELETED.
lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above
CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end
Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?
All TWRP version is not compatible with the OneUI3.1 update samsung has released a few days ago. So in order to be able to flash custom ROMs or other things you need to use this recovery instead.
Notes:
- You can only flash files from USB thumb drive (OTG drive), from an external sdcard or using adb sideload
- Only FAT32 thumb driver (OTG drive) are supported. So make sure you formate your drive to FAT32 before using it with lineage recovery, otherwise, it won't be able to read your drive
- this recovery version only supports latest ADB version so make sure you're using it
Installation:
1. Reboot to download mode
2. Flash the file using odin
Download:
LineageOs-18.1 Recovery
ADB and fastboot
Bugs:
- Data decryption doesn't work
- Fastbootd
- Can't flash file from device internal storage
Change Log:
16th of March 2021
- Initial Release
F.A.Q:
How to flash files using adb side load?
1. Reboot to recovery
2. Select apply update then adb
3. plug your device using usb cable to your phone
4. open a new terminal/cmd in the same folder the file you want to flash
5. Type " adb sideload file_name.zip "
#reserved 3
Does VoLTE and proximity sensor work in this ROM?
msurg said:
Does VoLTE and proximity sensor work in this ROM?
Click to expand...
Click to collapse
This is not a ROM. It's lineage-18.1 recovery.
Please, read the title carefully
LahKeda said:
F.A.Q:
How to flash files using adb side load?
1. Reboot to recovery
2. Select apply update then adb
3. plug your device using usb cable to your phone
4. open a new terminal/cmd in the same folder the file you want to flash
5. Type " adb sideload file_name.zip "
Click to expand...
Click to collapse
please can you explain more , because i am beginner in this subject . my experience since note 2 , and now i buy galaxy m51 , please answer me.
M H N said:
please can you explain more , because i am beginner in this subject . my experience since note 2 , and now i buy galaxy m51 , please answer me.
Click to expand...
Click to collapse
This recovery is kind of abandoned. use TWRP 3.5.1 if you're on one ui3.1 or twrp 3.4 if you're on oneui 2.5
LahKeda said:
This is not a ROM. It's lineage-18.1 recovery.
Please, read the title carefully
Click to expand...
Click to collapse
My mistake. Apology.
@LehKeda I have a general question: am I right that LOS 18.1 recovery *in general* does not have native USB OTG support, but that you added it manually into your edition?
RootedLee said:
@LehKeda I have a general question: am I right that LOS 18.1 recovery *in general* does not have native USB OTG support, but that you added it manually into your edition?
Click to expand...
Click to collapse
it supports it, but sometimes you need your device usb.init.rc file to initialize USB and OTG stuff
Hi @LehKeda Aha. I'm having compatibility/ reliability issues with another device's USB OTG sometimes working and sometimes not in TWRP regardless if it was flashed the recommended way into the existing LOS 18.1 boot as RamDisk (via the new "Flash Current TWRP") or if it was flashed to boot directly to boot instead system.
Regarding LOS 18.1 recovery, just now this second I finally see the LED lid up on my flash drive connected via USB cable.
All this is intermittent, and I tend to need to go through several hoops to finally have USB OTG working. To make things even more convoluted, it's definitely worse with the latest LOS 18.1 recovery/ boot I just applied yesterday, then TWRP added (again as RamDisk). I do not know if TWRP uses its own USB OTG drivers if run flashed to RamDisk, or if it relies on whatever is present in the LOS section of the boot partition after repackaging by TWRP.
I don't want to hijack this thread, so let me detail the issue in the other thread. I'll post the link shortly. I'm sure it's just a few files missing like the one you mentioned, or a 100% correct config inside such a file.
I appreciate your expertise and will be back shortly
@LehKeda here: Nokia 6.1 TWRP 3.6.0/ 3.4.0 USB OTG Instructions
The TWRP in question: from the TWRP for DRG_sprout page, the latest official 3.6.0
LOS recovery/ boot images from Builds for PL2. The recovery I've been having best results with as base for TWRP is lineage-18.1-20220118-recovery-PL2.img.
I'm aware the Nokia 6.1 (my phone) and the 6.1 Plus (the one that TWRP was developed for) aren't exactly the same, but with everything else working, I doubt that the slight model differences are the cause for the USB OTG being unreliable; plus TWRP 3.4.0 [UNofficial] for the Nokia 6.1 has the same issue..
Maybe you have an idea over there how this can be stabilized
[EDIT]: I'll be offline now for around 24 hrs, so there will be a delay in response from my side, just that you know
Update: March 24 2022: This ROM has been retired and a new one based on LOS 19.1 (and TWRP based on Android 11) have taken its place. New thread here: https://forum.xda-developers.com/t/...4-2020-lineageos-19-1-and-twrp-3-6-1.4421365/
---
Update 9:46am EST July 15 2021: new builds of TWRP and LineageOS with TWRP touch fixed and LOS w/ space for Gapps is now live.
WARNING: USE AT YOUR OWN RISK.
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the steps to follow:
Update your device to the latest stock ROM (as of this writing) either using the built-in system updater or via Odin. You want the build that ends with "3BUF3".
Unlock device bootloader using instructions from other threads. This will wipe your device.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Boot device back into download mode and flash TWRP via Odin in the "AP" slot. If you boot up into the stock ROM rather than booting directly back into download mode then go through the initial setup process of the stock ROM and enable developer tools and ensure OEM Unlocking is still enabled (VaultKeeper can possibly undo OEM Unlocking if you get to the ROM but don't go into Developer Tools and view OEM Unlocking is enabled, so make sure to do this).
Boot device into TWRP (recovery mode) and format (not wipe) your data partition. Then reboot back into TWRP.
Push LineageOS (super.new.ext4.img) to device. Ideally push it to an SD card formatted with ExFat or EXT2/3/4 (FAT/FAT16/FAT32/VFAT won't work due to file-size limitations).
Install LineageOS image to "Super" partition. Make sure to select "Install from Image" in order to show .img files in the install selector screen.
(Optional) Push NikGapps Omni to your device and install the zip. Make sure you include a "nikgapps.config" file in your "/tmp" folder that is configured to install to "system" rather than "product" or "default".
Reboot to system. You should now be in LOS with Gapps.
(Optional, but recommended): Install Magisk via TWRP
(Optional, but recommended): Run fix script to fix brightness slider not working and to make Magisk work. If you didn't install Magisk but only want the brightness fix, just enter "n" when prompted in the script. To run the script:
NOTE: Script has .txt file extension to allow hosting on AFH. Remove that so it's just .sh to match the instructions below.
Download and push to device when booted into TWRP
adb push sm-t500_fixes.sh /tmp
Enter an adb shell
adb shell
Change directories and set permissions
cd /tmp
chmod +x /tmp/sm-t500_fixes.sh
Run script
/tmp/sm-t500_fixes.sh
Tips:
If you are not seeing all of your storage space in the OS on the internal flash, boot to TWRP and format data.
Flash TWRP via "AP" slot and flash VBMeta_Disabler via "Userdata" slot in Odin.
Flash LineageOS as an Image, not as a Zip.
For Gapps, use the latest NikGapps for ARM64 and Android 11/R.
For Gapps, make sure you install to the System partition and not Product. To do this you need to slightly modify a nikgapps.config file. Instructions on that can be found on the NikGapps site.
Downloads:
LineageOS 18.1 20210615 Beta 2: https://www.androidfilehost.com/?fid=14943124697586369438
TWRP 3.5.2 Beta 3: https://www.androidfilehost.com/?fid=14943124697586369439
vbmeta_disabled_R: https://www.androidfilehost.com/?fid=14943124697586369440
Fixes for brightness and Magisk (sm-t500_fixes.sh): https://www.androidfilehost.com/?fid=14943124697586369521
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
Brightness controls don't work: Fixed via "sm-t500_fixes.sh script.
TWRP touch screen doesn't work (use USB keyboard or adb). Should be fixed with TWRP Beta 3.
TWRP formatting external SD card may hardbrick device. Do not do this! Fixed with TWRP Beta 2.
Source (device tree for TWRP from my Github): https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Source (kernel sources from Samsung): https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
agreenbhm said:
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the rough steps to follow:
Unlock device bootloader using instructions from other threads.
Patch stock ROM (AP) using Magisk, then flash rooted ROM. Will likely need to wipe device after this.
Boot into rooted ROM and ensure "OEM Unlocking" is still enabled in "Developer Tools".
Boot back into download mode and flash "vbmeta_disabled_R.tar" to disable verified boot.
Boot device back into rooted stock ROM to ensure things are still functional (may require a device wipe at this step).
Boot device into download mode and use ODIN to flash TWRP recovery.tar file via "AP" slot.
Boot device into TWRP to verify functionality (hold Vol-Up + Power during boot).
Access TWRP via adb using "adb shell" or with USB mouse (touch functionality currently not working).
Format data partition on device.
Via ADB shell: twrp format data
Via USB mouse: Wipe -> Advanced -> Format Data
Boot device into download mode.
Via ADB shell: twrp reboot download
Via USB mouse: Reboot -> Download
Flash LineageOS tar file via ODIN using the "AP" slot.
If device boots into TWRP after flashing LineageOS, use USB mouse to select: Reboot -> System
Device should boot and stall for ~1m at the Samsung logo screen with red text below, then should go blank and then display LineageOS boot image.
Downloads:
LineageOS 18.1 20210615 with TWRP 3.5.2: https://mega.nz/file/vMVglThZ#TepIHvdEypezq3z4S_4Lln7FRFVfC7CUjVGq3ByFb6U
TWRP 3.5.2: https://mega.nz/file/GYU1yCCQ#JsthI8BYNtfB08Pzt1eeXta2Lb1zCkUI185Zm88dEW4
vbmeta_disabled_R: https://mega.nz/file/iMFx3CQI#8cP4mPoRaQNwDATqt0vKD8wxqRWSTz1EL79U0fNpW8M
Click to expand...
Click to collapse
Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.
awesome. Will try after work. Also I think you posted in the wrong section.
Which slot to flash the vbmeta?
wizzdome said:
Which slot to flash the vbmeta?
Click to expand...
Click to collapse
AP
Thanks,
After flashing the vbmeta it booted into recovery automatically after what looked like a bootloop in progress, so I wiped with factory reset and then it rebooted fine. (still not sure exactly what the vbmeta does I was hoping it would make it so i didnt get that stupid pop up asking me to hit power button to continue booting due to it having the patched os) anyhow booted fine and twrp installed as you stated without touch screen but mouse with otg works fine. (great job so far) On to LOS... I think I should have checked oem lock before flashing LOS as when I installed I get stuck at boot screen that says oem lock is on... must have been from my factory reset... (facepalm)
Nope... Still sticking on boot with the following showing on the screen...
RPMB fuse not set
RPMB Provisioned
Current BInary: Custom (0x30f)
FRP Lock : OFF
OEM Lock : ON (U) {this was off verified before flash}
KG Status : Checking
Waranty Void : 0x1 (0xE02)
Quallcomm Secureboot : Enable
RP SWREV : B3 (1,1,1,3,1,1) k3 s3
secure download : enable
grdm status : normal (d0000501)
did : 041ce2d22dba
this is displayed in the corner on the bootscreen and looks like it belongs on the download screen, anyhow booting into twrp from this point works however factory reset fails with unable to mount key(something and key(something else) i figure i will let it sit a while as I know sometimes it just takes first boot a while to go through however it doesnt seem to be the problem. Have you had a positive install of the LOS? I am wondering if I had maybe gotten a bad copy of the file. When i go to install I get a pass in odin so not quite sure where to go from here other than back to the factory image any help to get this going would be great... I took on this task cause i needed someting to take my mind off the severely crappy week I have had... so looking forward to anything you can share here...
Actually, userdata is the slot I always use. It might work in both though.
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Nevermind what I said here.
jayzarry84 said:
Anyone get this to work? I just flashed the TWRP part but have not been able to get into TWRP
Click to expand...
Click to collapse
Get adb access in the OS and then run "adb reboot recovery"
agreenbhm said:
Get adb access in the OS and then run "adb reboot recovery"
Click to expand...
Click to collapse
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
You may need to get an otg cable for a USB mouse and choose "reboot system" from the gui. Alternatively, look at the /dev/block/by-name/misc partition and try blanking that out with dd. That has worked sometimes.
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
agreenbhm said:
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
Click to expand...
Click to collapse
Not working. I'll wait for my otg cable to come in
jayzarry84 said:
Not working. I'll wait for my otg cable to come in
Click to expand...
Click to collapse
I was able to use adb to run the TWRP Format Data command and it rebooted the tablet and now LOS has booted up. I think I'm good!
Looking forward to see how this develops
Rom is fast and snappy. Brightness control does not work. I haven’t played too much because of work but that’s what I’ve found so far
Can a mod move this to the rom release section?
agreenbhm said:
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Click to expand...
Click to collapse
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
lewmur said:
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
Click to expand...
Click to collapse
I will look into that, but I'm not optimistic it will work. This device does not separately present the system partition, rather it uses a super partition which contains system, vendor, product, and odm. TWRP only shows me the super partition for working with. I was able to resize the system partition by expanding the Lineage image and file system on my pc to match the original stock system partition, then rebuilt the super image with the other partitions it needs.