[Android 10][Recovery][A715F]TWRP 3.5.0 [ianmacd] - Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot

[Android 10][Recovery][A715F]TWRP 3.5.0 [ianmacd] - Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* 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 doing this to your device
* 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.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.0_10-4.img by ianmacd
twrp-a71-3.5.0_10-4.tar by ianmacd
Multidisabler zip by Ianmacd
VBMeta disabler
Previous Versions:
TWRP 3.5.0 10-2
TWRP 3.5.0_10-2.tar by Ianmacd
TWRP 3.5.0_10-2.img by Ianmacd
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
TWRP 3.5.0_10-4
This minor release accommodates the new (currently canary only) packaging of Magisk.
Future versions will no longer come as a separate .zip file, but will have the Magisk payload embedded inside the Magisk Manager .apk file.
To this end, TWRP will now also list any files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files.
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71

Join Ian's TWRP Telegram group
Code:
Check out the latest TWRP releases and notes on Ian's Telegram group
For anything already released, please ask here in XDA
Link: Telegram Group
Join our A71 Telegram group
Code:
Check out the latest projects on our Telegram, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Spanish General Android Telegram group
Code:
Grupo para los que hablamos español en donde discutimos Android en general /// Group made for Spanish speakers to discuss Android in general
Link: Telegram Group

How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.

so this will NOT work on an unlocked A71 A716U?

sixisixsix said:
so this will NOT work on an unlocked A71 A716U?
Click to expand...
Click to collapse
I don't think so, not sure. I don't have that device.

ShaDisNX255 said:
I don't think so, not sure. I don't have that device.
Click to expand...
Click to collapse
thank you for the response! So this model will work A71 SM-A715F/DS (amazon link)

Well it works on SM-A715F, I think the DS just stands for Dual SIM.

ShaDisNX255 said:
Well it works on SM-A715F, I think the DS just stands for Dual SIM.
Click to expand...
Click to collapse
ahh ok thank you. Samsung has an asinine amount of sku's/model which makes it extremely confusing especially in the US where you have to seek out global versions and cannot buy locally

sixisixsix said:
ahh ok thank you. Samsung has an asinine amount of sku's/model which makes it extremely confusing especially in the US where you have to seek out global versions and cannot buy locally
Click to expand...
Click to collapse
Thats the truth. I've been a Samsung user for years and I still get confused with all their variants

Hi, thank you for your work.
I am getting "Invalid Zip Format" and "directory) Error opening" errors with this method at TWRP. I followed the steps, put the image into gsi folder and renamed it to system.img. Any help?
ShaDisNX255 said:
How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.
Click to expand...
Click to collapse

taha2626 said:
Hi, thank you for your work.
I am getting "Invalid Zip Format" and "directory) Error opening" errors with this method at TWRP. I followed the steps, put the image into gsi folder and renamed it to system.img. Any help?
Click to expand...
Click to collapse
Probably was zipped incorrectly. Not sure.

Yeah you're right. Should've known better to zip 3 folders together instead of the parent one. It's working now and I'm testing Havoc-OS. Great, thanks.
ShaDisNX255 said:
Probably was zipped incorrectly. Not sure.
Click to expand...
Click to collapse

New TWRP is up! 3.5.0_10-4
Check out the changelog and the new download links in the OP

ShaDisNX255 said:
How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.
Click to expand...
Click to collapse
@ShaDisNX255 apologies for going a bit off topic.. But could you tell if any GSI rom is stable for our device?

karan5chaos said:
@ShaDisNX255 apologies for going a bit off topic.. But could you tell if any GSI rom is stable for our device?
Click to expand...
Click to collapse
I'm sorry but I don't use GSI. I'm quite contempt with Samsung software lol.

Will this work with A71 5G? I have SM-A716U

cyclesrxnder said:
Will this work with A71 5G? I have SM-A716U
Click to expand...
Click to collapse
No, it won't.

Thanks!

A7160可以用吗
Translation: Can A7160 be used

Is it possible to add password on TWRP?

Related

TWRP 3.2.0.0 Moto Z2 force [Nash]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
21.08.2021 - Add Symlinked dynamic partitions to fstab
09.08.2021 - Fix haptic feedback
- Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
01.03.2021 - Initial Release.

Boss!

Boss

Thanks boss..

Boss!

Omg.... Boss and Heroes

Any custom rims for this device yet? Maybe a Pixel Experience ROM?

Any news on rom development by chance?, Just curious thanks.

It will take a big while before custom ROMs, don't expect them too soon

Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.

siriow said:
Hello everyone, I only have one question, besides the Twrp and the vbmeta_disabled_R.tar do you also need to flash a Multidisabler via Odin? Thank you.
Click to expand...
Click to collapse
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.

FreeRunner2017 said:
You just need to go to advanced then open terminal in TWRP, and type multidisabler, then wait, then type it again.
Click to expand...
Click to collapse
Ok, Thank you

siriow said:
Ok, Thank you
Click to expand...
Click to collapse
Your welcome, any issues feel free to PM me

I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.

Burt Squirtz said:
I wish there was a very easy way to patch AP to keep TWRP after a dirty flash manual upgrade.
Click to expand...
Click to collapse
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.

dr.ketan said:
1.Easiest option - Go with custom ROM (If available)
2.Second easy, modify AP and patch it.
Extract all the contents of AP file - delete recoevry and vbmeta images - Repack as tar (You can use 7zip or similar) - Patch it with magisk
After flashing, straightway go to TWRP - and apply multidisabler before booting device.
Click to expand...
Click to collapse
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?

JazonX said:
This would clear the User data / Accounts also, yeah ?
@afaneh92 _ Bro, I think the existing TWRP doesnt mount Data on the Newest March Security Patch.
I had no issues with the February Firmware.
Could you have a look ?
Click to expand...
Click to collapse
You asked for dirty flash trick right? If erasing data and acc then it's not dirty flash.
I don't have any issue on March secure patch

What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.

JazonX said:
What could be causing this issue?
Did a full stock flash as well, and repeated the TWRP process.
Click to expand...
Click to collapse
Run multidisabler script in twrp terminal

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S7/S7+ Series (Snapdragon)

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
- Fix haptic feedback
28.07.2021 - Initial Release.

Amazing!! will try asap!

Any news bout T870/T875 development?

tabs s7 sm-t875 twrp please

I have posted a test build for the T870 here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
Please let me know if it works for you.

Good morning sir is good for tab s7+ sm-t975? tanks in adcance

Marx71 said:
Good morning sir is good for tab s7+ sm-t975? tanks in adcance
Click to expand...
Click to collapse
You can test, but make full backup and know how to recover soft brick by reflashing stock recovery/firmware.

tank you. But recover soft brick possible whit fastboot?

No, samsung disabled fastboot by default.

If I don't care about flashing in TWRP (yet) can I just flash recovery and see it running? (Basically is the wipe data optional)

parkerlreed said:
If I don't care about flashing in TWRP (yet) can I just flash recovery and see it running? (Basically is the wipe data optional)
Click to expand...
Click to collapse
Flashing vbmeta disable will wipe data

I have SM-T870, After point #4, its just in the loop. Cannot get to recovery.

To clarify, US tab s7+ (SM-T970N) snapdragon requires the paid token unlock before this can be flashed?

gpz1100 said:
To clarify, US tab s7+ (SM-T970N) snapdragon requires the paid token unlock before this can be flashed?
Click to expand...
Click to collapse
No, T970N is Korean not US!

tyracz said:
I have SM-T870, After point #4, its just in the loop. Cannot get to recovery.
Click to expand...
Click to collapse
If it doesn't boot on T870 then its not supported.

afaneh92 said:
No, T970N is Korean not US!
Click to expand...
Click to collapse
Hmm.. Costco has it wrong?
https://www.costco.com/samsung-galaxy-12.4%22-tab-s7%2b-128gb---mystic-black---includes-keyboard.product.100684979.html

afaneh92 said:
If it doesn't boot on T870 then its not supported.
Click to expand...
Click to collapse
I have rooted my SM-T870 by inserting Magisk into AP file and flashing it with odin. Only problem is that now i have in magisk A/B - NO. Which means my partitions are not flashed. I run into problems trying to execute some root programs where they crash since they dont have access to both partitions. Is there any way to root partition A/B?

tyracz said:
I have rooted my SM-T870 by inserting Magisk into AP file and flashing it with odin. Only problem is that now i have in magisk A/B - NO. Which means my partitions are not flashed. I run into problems trying to execute some root programs where they crash since they dont have access to both partitions. Is there any way to root partition A/B?
Click to expand...
Click to collapse
our device is not A/B its A only

afaneh92 said:
our device is not A/B its A only
Click to expand...
Click to collapse
Thank you for answer. If I root SM-T870 with Magisk via AP insert, is this considered full root ? or is this root like partial?

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S8 Series (Snapdragon)

Changelog:
GitHub History Tab S8
GitHub History Tab S8+
GitHub History Tab S8 Ultra

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section

You have no idea how excited I got when I saw this. I'm going to try this first thing tomorrow and post my results! One question though; When you said "You need a custom permissive kernel to boot with R/W vendor.", is that the one that you've linked in the initial post?

SavXL said:
You have no idea how excited I got when I saw this. I'm going to try this first thing tomorrow and post my results! One question though; When you said "You need a custom permissive kernel to boot with R/W vendor.", is that the one that you've linked in the initial post?
Click to expand...
Click to collapse
Yes its.
Also if anyone have the regular Tab S8 send me recovery.img here or on telegram

Sure, this is for X700XXU1AVCD/X700OXM1AVCD/X700XXU1AVCD (Tab S8 Wi-Fi Middle East).
I used this to root but it may be corrupt so you might wanna check.
Download

Hello ,
Is it possible with this twrp version to use the sd card also ? Thank you for your answer .

I see magisk v25 change log mentions
Fix vb meta extraction implementation.
So does that mean magisk v25 will disable vb meta automatically now?

Techguy777 said:
I see magisk v25 change log mentions
Fix vb meta extraction implementation.
So does that mean magisk v25 will disable vb meta automatically now?
Click to expand...
Click to collapse
I belive so. IIRC, if you've rooted your tablet by patching the AP file with Magisk and flashed it in Odin, then vbmeta should already be disabled. Magisk, and therefore root, will still persist even after a factory data reset because your device is running Magisk as a system app.

Finally awake. Gonna go ahead and flash TWRP on my Tab S8+ and share my results!

SavXL said:
I belive so. IIRC, if you've rooted your tablet by patching the AP file with Magisk and flashed it in Odin, then vbmeta should already be disabled. Magisk, and therefore root, will still persist even after a factory data reset because your device is running Magisk as a system app.
Click to expand...
Click to collapse
I don't know about magisk becoming a system app I own the tab s6 I'm on one UI 4.1 and have magisk v25 And it doesn't install the system app so I don't know about that. I don't own s8 tablet

Techguy777 said:
I don't know about magisk becoming a system app I own the tab s6 I'm on one UI 4.1 and have magisk v25 And it doesn't install the system app so I don't know about that. I don't own s8 tablet
Click to expand...
Click to collapse
Then don't spam every thread with tab s6 topics

I come baring results. I flashed TWRP and vbmeta in Odin as described in the initial post, and it booted into TWRP! However, the good news ends there. The touch screen doesn't seem to work when in TWRP, and interestingly, when I have the keyboard attachment on, the install button darkens as if I'm pressing it no matter what I do on the trackpad. I've tried rebooting the tablet by holding pow + vol- but all it does is reboot once and then put me back in TWRP. I can use ADB to go into download mode, but I can't boot back to Android. Looks like I'm gonna need to flash my patched firmware and try again when this gets fixed. For context, I flashed the gts8p TWRP tar because I have a Tab S8+, but the WIFI only variant (X800), which is in the supported versions list, so I'm not sure what went wrong.

SavXL said:
I come baring results. I flashed TWRP and vbmeta in Odin as described in the initial post, and it booted into TWRP! However, the good news ends there. The touch screen doesn't seem to work when in TWRP, and interestingly, when I have the keyboard attachment on, the install button darkens as if I'm pressing it no matter what I do on the trackpad. I've tried rebooting the tablet by holding pow + vol- but all it does is reboot once and then put me back in TWRP. I can use ADB to go into download mode, but I can't boot back to Android. Looks like I'm gonna need to flash my patched firmware and try again when this gets fixed. For context, I flashed the gts8p TWRP tar because I have a Tab S8+, but the WIFI only variant (X800), which is in the supported versions list, so I'm not sure what went wrong.
Click to expand...
Click to collapse
Thanks for the feedback, will look into it soon. If you can send me vendor/firmware folder will try to fix touch.

afaneh92 said:
Thanks for the feedback, will look into it soon. If you can send me vendor/firmware folder will try to fix touch.
Click to expand...
Click to collapse
How do I do that? Is it a command I can run in adb?

SavXL said:
How do I do that? Is it a command I can run in adb?
Click to expand...
Click to collapse
Use root explorer, zip the folder and upload it

afaneh92 said:
Use root explorer, zip the folder and upload it
Click to expand...
Click to collapse
Alright, will do once I get back into android.

afaneh92 said:
Use root explorer, zip the folder and upload it
Click to expand...
Click to collapse
Alright, here's the vendor folder! It's compressed from the original size (~2.15GB).
715 MB file on MEGA
mega.nz

SavXL said:
Alright, here's the vendor folder! It's compressed from the original size (~2.15GB).
715 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Wow, I asked for firmware folder from vendor not the whole vendor.

afaneh92 said:
Wow, I asked for firmware folder from vendor not the whole vendor.
Click to expand...
Click to collapse
Ohhhhhhhhhh, I'm sorry LOL. When you said vendor/firmware I assumed you said to upload the vendor folder OR the firmware folder. I'll remember that for next time. XD

Development [UNOFFICIAL] LineageOS 20 for the Motorola Edge 30 Ultra (eqs)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include "std_disclaimer.h"
/*
* 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.
*/
What's working:
RIL (Calls, SMS, Data)
Fingerprint (FOD)
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
IMS (VoLTE/VoWifi)
What's not working:
Receiving SMS on chinese variants (or just carriers) may not work, more debugging required
Flashing Instructions:
Requirements:
Unlocked bootloader!
Learn these instructions by heart
PC with working adb/fastboot
Downloaded:
LineageOS zip
copy partitions zip
optional:
gapps
magisk
<insert other mod here>
Make a backup of EVERYTHING on your internal storage you dont wanna lose
reboot to bootloader
Code:
adb reboot bootloader
or reboot the device, and hold power and volume down
Flash the lineage recovery to both slots
Code:
fastboot flash recovery_a recovery.img
Code:
fastboot flash recovery_b recovery.img
reboot to recovery
use volume keys to select recovery reboot option and press power to confirm
in recovery use volume keys and power to navigate
stock vendor_boot does not contain touch drivers, so live with this for a bit
Select "Apply Update"
Select "Apply from ADB"
If you come from stock, this is REQUIRED:
Code:
adb sideload copy-partitions-20220613-signed.zip
Code:
adb sideload <lineageos zip>
Go back (Volume up can select the back button)
Advanced
Reboot recovery
You can use touch now
factory reset
-----Optional, Gapps/Magisk------
Select "Apply Update"
Select "Apply from ADB"
Code:
adb sideload <path/to/gapps.zip>
Code:
adb sideload <path/to/Magisk.zip>
Code:
adb sideload <path/to/some/other/mod.zip>
-----End Optional-----
Reboot system now
First boot, especially with Gapps, may take a while
Telegram group: https://t.me/MotoEdge30Ultra
Downloads:
copy partitions: https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
LineageOS 20 (no gapps): https://drive.google.com/file/d/11hDmheZHVUey22upXOC-Yq1IqGC5-Fbq/view?usp=sharing
LineageOS 20 (with gapps): https://drive.google.com/file/d/11k64BFOhVbVl7OsUcpIAPXTRCl-FlViz/view?usp=sharing
Sources:
device tree/kernel: link
vendor: link

Changelogs:20221119:
Initial Release
20230523:
Up-to-date LineageOS sources
common vendor from bronco T1TBS33.32-8-9-7-2
eqs specific from S3SQS32.16-72-31-3 (mainly camera, firmwares)
Main kernel compiled from T1TBS33.32-8-9-7-2
Updated kernel device tree from T1TBS33.32-8-9-7-2
other changes I might have forgotten...

Reserved Post number 2

hola, alguien lo ha instalado?

我是酷安吸引过来看看的，不准备刷，小白鼠先上，我坐等PE系统。
Mod edit: English please!
Google translation:
I was attracted by Kuan to take a look. If I don’t plan to brush, the mouse will go first, and I will wait for the PE system.

Thank you for all your efforts!!! Hoping we could get more custom ROM to run later

Tiene gapps incluidos? I have already seen that it does not have what gapps do you recommend? thanks for the job

Awesome, thanks for your work! Should be possible to compile TWRP with your device tree and kernel now as well, right?!
Would you mind explaining why copy-partitions is needed and what it does?

Any experiences? Does Netflix work?

I have stock ROM, but magisk with unlocked bootloader... Putting it on the zgisk list, and using Safernet module updates via Playstore normally. But without hrd only in SD.
grove said:
Any experiences? Does Netflix work?
Click to expand...
Click to collapse

iron maiden said:
Tiene gapps incluidos? I have already seen that it does not have what gapps do you recommend? thanks for the job
Click to expand...
Click to collapse
I'm using Nikgapps currently
Killuminati91 said:
Awesome, thanks for your work! Should be possible to compile TWRP with your device tree and kernel now as well, right?!
Would you mind explaining why copy-partitions is needed and what it does?
Click to expand...
Click to collapse
Should work, i guess. And for TWRP no special kernel is needed. The recovery partition just contains a ramdisk (the recovery itself), with no kernel. During boot the bootloader merges the available ramdisks (depending on the boot mode ofcourse).
E.g. when you start the device normaly, it will merge the ramdisks from boot and vendor_boot (soc specific kernel modules)
When you start recovery it will merge the ramdisks from boot, vendor_boot and then recovery.
Copy partitions copies all slotted partitions (_a ad _b ones) from the current active slot to the inactive slot (e.g. when youre on slot a, it will copy all of them to their _b counterparts).
This is needed because motorola does not ship the second slot populated. So in case you have a fresh device (no OTAs and so, or you just flashed stock again), the second slot will be completely empty (no bootloader, no nothing). And A/B devices switch slots after every flash of a ROM, so the device would then try to boot into an empty slot, which fails and would kick you into qualcomms emergency download mode (9008).
If blankflash would help you in that state, im not sure.
grove said:
Any experiences? Does Netflix work?
Click to expand...
Click to collapse
Using it for like 2 weeks now as a daily driver. Netflix should work, but as L3 (idk if L1 would work, my device never was L1, so cant test that)

SGCMarkus said:
I'm using Nikgapps currently
Should work, i guess. And for TWRP no special kernel is needed. The recovery partition just contains a ramdisk (the recovery itself), with no kernel. During boot the bootloader merges the available ramdisks (depending on the boot mode ofcourse).
E.g. when you start the device normaly, it will merge the ramdisks from boot and vendor_boot (soc specific kernel modules)
When you start recovery it will merge the ramdisks from boot, vendor_boot and then recovery.
Copy partitions copies all slotted partitions (_a ad _b ones) from the current active slot to the inactive slot (e.g. when youre on slot a, it will copy all of them to their _b counterparts).
This is needed because motorola does not ship the second slot populated. So in case you have a fresh device (no OTAs and so, or you just flashed stock again), the second slot will be completely empty (no bootloader, no nothing). And A/B devices switch slots after every flash of a ROM, so the device would then try to boot into an empty slot, which fails and would kick you into qualcomms emergency download mode (9008).
If blankflash would help you in that state, im not sure.
Using it for like 2 weeks now as a daily driver. Netflix should work, but as L3 (idk if L1 would work, my device never was L1, so cant test that)
Click to expand...
Click to collapse
No SMS received after root

@SGCMarkus does 200Mpx mode works? manual, raw...

ailikes said:
No SMS received after root
Click to expand...
Click to collapse
You on the chinese variant and/or on a chinese carrier?
Currently thats a known issue... needs more investigating. But kinda difficult without more people who test it, as it works here on my (european) device in austria.
TF1920 said:
@SGCMarkus does 200Mpx mode works? manual, raw...
Click to expand...
Click to collapse
MotCamera4 is included, and all features should work.

Hi, I got the phone just now, I wonder what role does the "copy partition" play in the flashing process? Like some modem? or something else?

C_CWang said:
Hi, I got the phone just now, I wonder what role does the "copy partition" play in the flashing process? Like some modem? or something else?
Click to expand...
Click to collapse
Check post #11 here
also will write a FAQ later for that i guess

@SGCMarkus
What are your plans for this ROM ? Will you maintain it for a while ?

SGCMarkus said:
You on the chinese variant and/or on a chinese carrier?
Currently thats a known issue... needs more investigating. But kinda difficult without more people who test it, as it works here on my (european) device in austria.
MotCamera4 is included, and all features should work.
Click to expand...
Click to collapse
Can a telegram group be created

Can you create a telegram? I'm from China. I can help test it. I'm looking forward to it. Come on, developers

Thank you for you sharing your builds, I want flash your rom without using root and I have some questions:
1- did you plan to make offical lineage
2- play store certified or not
3- can we running the bank app without any security issue

Database Develop

welcome