Develop Bugs

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 10/+/5G Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note 10/+/5G​Only for exynos variants - N970F / N975F / N976B (Europe - Global, Single/Dual-SIM), N971N, N976N (South Korea)
Disclaimer
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 recovery 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.
Kernel Features:
latest kernel source release
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
spoofed config for firmware checks
Recovery Features:
built in full 64 mode
toybox/busybox support
compatible with Android 10.0 and above
Downloads:
Note 10 - d1 - N970F
Note 10 5G - d1x - N971N
Note 10+ - d2s - N975F
Note 10+ 5G - d2x - N976B/N976N
avb disabled vbmeta
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download avb disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download avb disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - d1 / d1x / d2s / d2x
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9820/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
07.03.2022 - TWRP 3.6.1
Security patch: 2022-02-01
Compatibility: only GVA*/GVB* firmwares, OneUI 4.0
Spoiler: Archive
09.01.2022 - android 12 support
Security patch: 2022-01-01
Compatibility: only GUL* firmwares, OneUI 4.0
08.01.2021 - android 11 support
Security patch: 2020-12-01
Compatibility: only ETL* firmwares, OneUI 3.0
27.12.2020 - TWRP 3.5.0 bringup - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
09.12.2020 - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
05.12.2020 - Initial release
Security patch: 2020-11-01
Compatibility: DTJ* firmwares
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Patch TWRP with Magisk
Use recovery to boot up rooted
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version and only if you don't plan to boot rooted with TWRP (some kernels deliver root prebuilt in kernel), or Rollback protection will kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

official builds will be up in few hours

Nice, congrats!

Hi, i'm getting the Note 10 soon & remember when i've tested the S10 months ago that i had trouble with twrp encryption/decryption : can you confirm after wiping data that you can encrypt it (system) and twrp will be able to decrypt it after you enter your pattern..? Thanks.

Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
PS: N971N does not have a build compatible with OneUI 3.0 since no public release of that yet, it will be built once samsung starts pushing the update for that phone.
Regards!

corsicanu said:
Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
PS: N971N does not have a build compatible with OneUI 3.0 since no public release of that yet, it will be built once samsung starts pushing the update for that phone.
Regards!
Click to expand...
Click to collapse
is the latest TWRP 3.5.0_9-4-d1 compatible with the latest Samsung ROM update? Below are the details of the firmware update I'm referring to:
ModelSM-N970FModel nameGalaxy Note 10VersionAndroid 11Changelist21054212Build dateThu, 18 Feb 2021 05:15:51 +0000Security Patch Level2021-03-01Product codeXTCPDAN970FXXU6FUBDCSCN970FOXM6FUBD
Thanks in advance!
Edit: based on this article it's One UI 3.1

Hi,
Is this method works and safe for N971N?
Android 12

nilofino said:
Hi,
Is this method works and safe for N971N?
Android 12
Click to expand...
Click to collapse
Actually I tried and it works

Is it safe after installing TWRP to RE-LOCK the bootloader???

tried using with android 12 trough magisk and i got phone blocked on samsung logo, also i was unable to select storage on wipe menu, any insight?

nilofino said:
Actually I tried and it works
Click to expand...
Click to collapse
HOW?!
I have the same SM-N971N, but I Got the error of showing less storage than it has after flashing. Like, -192GB/60GB and in settings it shows 16GB, Constantly says the TA Downloader has stopped.
So it messed up totally in my case ; and i reverted back
So Help me how did you managed?!

Rafin Rahman said:
HOW?!
I have the same SM-N971N, but I Got the error of showing less storage than it has after flashing. Like, -192GB/60GB and in settings it shows 16GB, Constantly says the TA Downloader has stopped.
So it messed up totally in my case ; and i reverted back
So Help me how did you managed?!
Click to expand...
Click to collapse
Just follow the instructions!
It seems that you have selected "repartition" option (in odin options),
You can find the solution easly. Maybe installing the stock Rom helps, but plz search for the solution before doing any further actions

nilofino said:
Just follow the instructions!
It seems that you have selected "repartition" option (in odin options),
You can find the solution easly. Maybe installing the stock Rom helps, but plz search for the solution before doing any further actions
Click to expand...
Click to collapse
No to be honest, i never messed with that part lol
But if it really is how you say, then let me try this pain once again :")

nilofino said:
Just follow the instructions!
It seems that you have selected "repartition" option (in odin options),
You can find the solution easly. Maybe installing the stock Rom helps, but plz search for the solution before doing any further actions
Click to expand...
Click to collapse
can you help me finding the twrp flashable zip for N9710N?

I used the original one from official website
Rafin Rahman said:
can you help me finding the twrp flashable zip for N9710N?
Click to expand...
Click to collapse

nilofino said:
I used the original one from official website
Click to expand...
Click to collapse
OK I DID IT! But man, twrp got installed, but no magisk, nothing is installing/flashing via TWRP, idk whyy!! :")
Maybe its android 12 thats causing problem
It did successfully installed TWRP as Custom Recovery, but as for superuser, Im handcuffed now , Sed Lyf:")

Intento instalar Twrp junto con Vbmate en mi N971N y me tira este error y si solo instalo Twrp no pasa del logo de Samsung

Thank you for your hardwork!

[Development and Testing][COMPLETE] Android 11 on Huawei Honor 6x.

UPDATE : An Android 11 ROM (Fluid OS) has been successfully tested and a new thread was opened. Feel free to use this thread in future if you're working on a different android 11 ROM.
This thread is dedicated for the development and discussions on different android 11 ROMs and GSI's that work on our device.​Already tested ones : (need fixes and any help is appreciated)
> @phhusson 's android 11 builds (treble experimentations, v308)​Issues : ​Works fine on first boot but reboot/subsequent boots are causing bootloops. only fix found is that it is requiring a factory reset with stock recovery on every boot.​Procedure followed : ​
Boot to recovery from stock emui 8 / any custom one that was installed on emui 8.​
Factory reset with twrp by typing "yes".​
push system image with adb to device after extracting it with 7zip from .xz file.​
Flash system image.​
Flash stock recovery.​
Boot to stock recovery and perform factory reset and wipe cache (in a random order, many times for satisfaction ).​
Choose reboot and wait.​
Fixes tried :​> Booting fix from @Hami_Do from this thread. This didn't fix the issue but as a side effect, the device stopped booting.​ Conclusion : This is not the right patch for the issue that was encountered.​​> Waiting for others to try out different ROMs/GSI's and inform(post in this thread).​Builds that can be tried :​# @DarkJoker360 's builds.​# Other GSI's​# Other ones that you know which might work.​​*This thread will be updated with every fix that worked, procedures, ROMs/GSI's and patches used whether worked or not so that development will be easy.
Thanks to @Djiban for the idea of starting a development thread for accelerating the development.
***Please try out every rom you could (if your willing to) and use different patches and post your observations in this thread so that the development will be active.***
Feel free to give out your suggestions about different patches that can be tried.​

RESERVED.​

The best but time-taking way : Compiling rom directly from the android source, device trees etc.
If anyone has required hardware and time, try it if you are willing to.

Hello. As some users of the Honor 6x managed to install @DarkJoker360 AOSP 10 for P8lite, until july 2020 version (later release didn't boot). I tried to compil every succesfull tricky install process of this rom on another devices than the P8 lite. And as @DarkJoker360 released an AOSP 11 for P8 Lite, maybe this compilation of install steps could make it work on our Honor 6x. Below are the conclusion of my reseach, surely some steps are not mandatory:
- Upgrade to EMUI (Warning for last stock firmware version, for P8 light for example: I recommend .360 firmware or .400. Newer firmwares with newer security patches may refure to boot due to some Huawei changes for avoiding modding)
- Remove the saved fingerprints and Google Accounts just in case
- Download the TWRP recovery from pretoriano80 (https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so ou https://eu.dl.twrp.me/prague/)
[Sinon from @Dil3mm4 (https://forum.xda-developers.com/p8...lopment/unofficial-twrp-3-2-1-0-oreo-t3773970) or use this recovery https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view ou https://sourceforge.net/projects/hi...WRP/twrp-3.4.0.0-v1-hi6250-emui8.img/download]
- fastboot flash recovery_ramdisk recovery.img
- TWRP-flash fstab.hi6250b.zip (https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/fstab.hi6250b.zip/download)
- Wipe and Format Data>yes then reboot. You should reboot into ugly looking stock rom.
- In settings>security>more you should see Encrypt phone that means storage is decrypted.
- Enable debug and confirm via adb and boot into TWRP
- go to TWRP -> Wipe -> Advanced Wipe, and do a full wipe (system, data, cache, dalvik/art cache), Don’t Format Data again because most probably you'll lose Internal Storage
- extract img from AOSP 11 main file
- TWRP-Flash system.img : TWRP -> Install -> Install Image (OR reboot to bootloader and "fastboot flash system drag and drop <drag system.img here>")
- Resize the system partition: press "Wipe" Then choose "Advanced Wipe". After that select/check "System" box and then press on "Repair or Change File System" and then you will see down "Resize File System", press on it and done ur System has been resized. (DO NOT FORMAT!), u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb
- Install NikGapps core with SetupWizard add-on
- Install NFC_fix.zip
[ NON !!! - MUST flash Magisk Phh 19.3]
- (Required) Install prague patch
- After installing all things you will need to install stock recovery and wipe cache and try to do factory reset(i tried to but i got error massage)
- after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier (huawei update extractor ?)
- do factory reset and wipe cache, after that load to bootloader again
- finally flash huaweitwrp.img https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view
- reboot into that twrp
- chooose advances; fix encryption
- Reboot and wait, then you can access internal memory
- After first boot, you need to, format data in erecovery
Click to expand...
Click to collapse
Unfortunatly, I have no time at the moment for Honor 6x, but if some of you want to comment/try/discuss about these steps...

The problem I faced was also mentioned in developers.android.com (power cycle one).
Is there any fix for this?
{
"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"
}

@Djiban
I need your help to test out the same process I've done in post #1 for AOSP 11 but this time along with flashing fstab.hi6250.zip. @Hami_Do suggested this. But I'm not having a spare device to test it out. Please do it when you have some free time.

1) when in the process should I flash fstab.hi6250.zip according to you ?
2)you wrote:
Boot to recovery from stock emui 8 / any custom one that was installed on emui 8.
Factory reset with twrp by typing "yes".
the factory reset can be done with either stoc or TWRP recovery, there is a contradiction here.
3) do you use this .xz file: system-roar-arm64-ab-vanilla.img.xz
4) witch stock recovery to flash and where to find it? ( in the xz file ?)
I'll check your complete guide to install AOSP 10 to be sure!

Djiban said:
when in the process should I flash fstab.hi6250.zip according to you ?
Click to expand...
Click to collapse
I don't actually know about that. Maybe before installing the system image and if the rom again bootloops after rebooting, flashing it again..?

Venkata Lochan Nune said:
I don't actually know about that. Maybe before installing the system image and if the rom again bootloops after rebooting, flashing it again..?
Click to expand...
Click to collapse
see my last post, I did edit with more questions when you did this answer.
for darkjoker's rom fstab.hi6250b.zip is flashed just after flashing the very first TWRP recovery (see post #4) , I'll give it a try like that.
I'm waiting for your answers 2 3 4 from my last post

Djiban said:
1) when in the process should I flash fstab.hi6250.zip according to you ?
2)you wrote:
Boot to recovery from stock emui 8 / any custom one that was installed on emui 8.
Factory reset with twrp by typing "yes".
the factory reset can be done with either stoc or TWRP recovery, there is a contradiction here.
3) do you use this .xz file: system-roar-arm64-ab-vanilla.img.xz
4) witch stock recovery to flash and where to find it? ( in the xz file ?)
I'll check your complete guide to install AOSP 10 to be sure!
Click to expand...
Click to collapse
2) I meant to boot to TWRP from stock emui 8 rom or AOSP 10 which I've posted a guide on or any other builds.
It in more simpler terms means to boot to TWRP from any of the roms you are currently using.
3) I used the a-only one not ab. Honor 6x supports a-only versions and not ab. ab is for devices launched with Android 9 or later.
4)I attached the stock recovery in the AOSP 10 post #1. It is the stock recovery which we will find in EMUI 8 update.zip file.
Additional : you can use 7zip to extract xz file.
Did I make myself clear?

Venkata Lochan Nune said:
2) I meant to boot to TWRP from stock emui 8 rom or AOSP 10 which I've posted a guide on or any other builds.
It in more simpler terms means to boot to TWRP from any of the roms you are currently using.
3) I used the a-only one not ab. Honor 6x supports a-only versions and not ab. ab is for devices launched with Android 9 or later.
4)I attached the stock recovery in the AOSP 10 post #1. It is the stock recovery which we will find in EMUI 8 update.zip file.
Additional : you can use 7zip to extract xz file.
Did I make myself clear?
Click to expand...
Click to collapse
2) do you think a factory reset in the stock recovery (if TWRP recovery is not installed) will not work as well? I think so.
In fact to flash fstab.hi6250b.zip, you havce to have TWRP recovery. This means that this rom cannot be install to a full stock EMUI, yiou have to install TWRP recovery first
3) ok
4) ok, sorry
i,ll give a try today I hope
5) do you also recommend those steps at the begining as for AOSP 10:
Format the data partition {Wipe > Format data > type "yes"}
In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.
6) Can,'t we flash img and recovery though adb, or only in TWRP recovery {Install > Install Image > Select > Choose system image > Swipe➡} {Install > Install Image > Select > Choose recovery image > Swipe➡}
6) no open gapps for android 11!! should we stay vanilla, or do you think there will be a simple package to flash afterwards, when vanilla will be running ?

Djiban said:
2) do you think a factory reset in the stock recovery (if TWRP recovery is not installed) will not work as well? I think so.
In fact to flash fstab.hi6250b.zip, you havce to have TWRP recovery. This means that this rom cannot be install to a full stock EMUI, yiou have to install TWRP recovery first
3) ok
4) ok, sorry
i,ll give a try today I hope
5) do you also recommend those steps as for AOSP 10:
Format the data partition {Wipe > Format data > type "yes"}
In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.
6) no open gapps for android 11, should we stay vanilla, or do you think there will be a simple package to flash afterwards ?
Click to expand...
Click to collapse
2) yeah, except the recovery I think every other partition being stock is better.
5) yes
6) you can directly try the gapps arm64 a only version here and OpenGapps android 11 is under testing and is also available at sourceforge. But better try the gapps IMG itself.

Venkata Lochan Nune said:
@Djiban
I need your help to test out the same process I've done in post #1 for AOSP 11 but this time along with flashing fstab.hi6250.zip. @Hami_Do suggested this. But I'm not having a spare device to test it out. Please do it when you have some free time.
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group, there check /notes and find #a11-installation-guide

Hami_Do said:
Join https://t.me/hi6250group telegram group, there check /notes and find #a11-installation-guide
Click to expand...
Click to collapse
I did, not easy to find anything yet !

OK, Did try install to install phh AOSP 11 with the full process below ,from a clean EMUI 8 . Result : device is in bootloop.
What Should I change? From where to restart (do I have to go back to EMUI 8 , or I can restart the below process with change, from there ?)
Note that stock recovery factory reset (even low level factory reset, that occured after several bootloops) did not work at all, stoped after couple of second.
- Connect your usb debugging enabled Honor 6X (with EMUI 8 or custom rom installed over EMUI8) to a PC with adb & fastboot
- in the Adb directory of the PC, download:
https://forum.xda-developers.com/attachments/twrp-img.5326857/
https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/fstab.hi6250b.zip/download
https://forum.xda-developers.com/attachments/stock_recovery_ramdisk-img.5321325
system-roar-arm-aonly-vanilla.img extracted with 7zip from
https://github.com/phhusson/treble_experimentations/releases/download/v308/system-roar-arm-aonly-vanilla.img.xz
- in adb check if the device is connected with "adb devices"
- in adb , "adb reboot bootloader"
- in adb, check if the device is connected with "fastboot devices"
- in fastboot, "fastboot flash recovery_ramdisk TWRP.img"
- in fastboot, "fastboot reboot"
- after reboot completed, "adb reboot recovery"
- in adb, "adb push -p fstab.hi6250b.zip /sdcard/"
- in TWRP recovery, flash fstab.hi6250b.zip
- in TWRP recovery, Format the data partition {Wipe > Format data > type "yes"}
- in TWRP recovery, wipe > advanced wipe > select system, data, cache and DALVIK and format them.
- in TWRP recovery, factory reset
- in adb, "adb push -p system-roar-arm-aonly-vanilla.img /sdcard/"
- in TWRP Recovery Flash system-roar-arm-aonly-vanilla.img {Install > Install Image > Select > Choose system image > Swipe➡}
- in adb, "adb push -p fstab.hi6250b.zip /sdcard/"
- in TWRP recovery, flash fstab.hi6250.zip (just to be sure)
- in adb, "adb push -p STOCK_RECOVERY_RAMDISK.img /sdcard/"
- In TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe➡}
- Disconnect honor 6X from PC, and in TWRP reboot to stock recovery
- in Stock recovery, wipe cache and factory reset (even if error)
- in Stock recovery, reboot and wait.
Click to expand...
Click to collapse

maybe those steps were mistakes:
- in TWRP recovery, factory reset (even if it's early in the process)
- reinstall of fstab.hi6250.zip at the end of the process

Djiban said:
maybe those steps were mistakes:
- in TWRP recovery, factory reset (even if it's early in the process)
reinstall of fstab.hi6250.zip at the end of the process
Click to expand...
Click to collapse
What happened after you did this? Is it still bootlooping?

Venkata Lochan Nune said:
What happened after you did this? Is it still bootlooping?
Click to expand...
Click to collapse
I have to access bootloader mode and reinstall TWRP again, give it a try tonight

Ok tried ton install AOSP 11 without any fstab.hi6250b.zip flashing. Still bootloop! It seems my device is lacking an EMUI8 part, and not yours!
note that each time:
- when I'm final rebooting in recovery from TWRP, it says "no OS installed, sure you wish to reboot?"
- stock recovery factory reset stops at 7%
@Venkata Lochan Nune do you have this 2 errors too ?

Found my error, I was flashing the ARM and not the ARM64 system .img !!!!
First boot in AOSP 11 succeded.
I even tried the gapps img, but google setup wizard loops.
As I did flash fstab.hi6250.zip just after TWRP recovery in this last install, I' did checked if AOSP 11 survives the second boot:
gapps img did
vanilla img did
I think you can either change the status of this thread, or open a new one. Wa have an usable android 11 for Honor 6X. The exact process I did follw is quoted at the end of this post.
Still to do:
- test and bug search (let me know what should I try)
- find a nanogapps package to install
-find out how to proceed for system updates
thx for all @Venkata Lochan Nune
Process used to install:
- Connect your usb debugging enabled Honor 6X (with EMUI 8 or custom rom installed over EMUI8) to a PC with adb & fastboot
- in the Adb directory of the PC, download:
https://forum.xda-developers.com/attachments/twrp-img.5326857/
https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/fstab.hi6250b.zip/download
https://forum.xda-developers.com/attachments/stock_recovery_ramdisk-img.5321325
system-roar-arm64-aonly-vanilla.img extracted with 7zip from https://github.com/phhusson/treble_...d/v308/system-roar-arm64-aonly-vanilla.img.xz
- in adb , "adb reboot bootloader"
- in fastboot, "fastboot flash recovery_ramdisk TWRP.img"
- in fastboot, "fastboot reboot"
- after reboot completed, "adb reboot recovery"
- in adb, "adb push -p fstab.hi6250b.zip /sdcard/"
- in TWRP recovery, flash fstab.hi6250b.zip
- in TWRP recovery, Format the data partition {Wipe > Format data > type "yes"}
- in TWRP recovery, wipe > advanced wipe > select system, data, cache and DALVIK and format them.
- in adb, "adb push -p system-roar-arm64-aonly-vanilla.img /sdcard/"
- in TWRP Recovery Flash system-roar-arm64-aonly-vanilla.img {Install > Install Image > Select > Choose system image > Swipe➡}
- in adb, "adb push -p STOCK_RECOVERY_RAMDISK.img /sdcard/"
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe➡}
- Disconnect honor 6X from PC, and in TWRP reboot to recovery
- in Stock recovery, wipe cache and factory reset (even if error)
- in Stock recovery, reboot and wait.
Click to expand...
Click to collapse

[Fluid OS][Android 11] Guide to install Fluid OS on Huawei Honor 6X

POST - v3
(This number will increase every time the post is updated.)​What's new in v3?
Added procedure in a new spoiler to install the base EMUI 8 for hi6250 devices as using the EMUI 8 we get with our device is causing some errors and bugs. Thanks to @Kentoto2021 and @VarianWrynn for testing and reporting this problem.
Spoiler: Version Changelog
What's new in v2?
Updated the thread with newly found bugs in "What isn't working" section.
Made small changes to thread.
What's new in v1?
Took a lot of time to collect the infinity stones.
Took even longer to make Mr. Thanos snap this thread to existence.
What's new in v0?
LoL Who knows?
This ROM is none of my work. I just tested it and provided appropriate procedure and fixes to errors(Found nothing yet).
Thanks a ton to @Hami_Do for making this possible. Original Post : link.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks again to Huawei for making more than one device with hi6250 chipset.
Thanks a lot to @Djiban for helping me and testing different procedures, fixes and ROMs.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.​
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link.
TWRP from attachments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used pico OpenGapps).
stock recovery (available in attachments).
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10. Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What is OpenGapps? Check it out at OpenGapps.org!
What is ARM64? it is a 64 bit operating system/platform.
What isn't working :
Usb Notification (Options will be greyed out. To transfer files, go to Developer Options > Default USB configuration > set it to File Transfer).
Dual sim is buggy. Single sim works perfectly. Thanks to @Loopeez for reporting it.
What's Working :
Everything.
*Tell me if something isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***
Spoiler: Installing base EMUI 8 for hi6250 devices.
This was already described in a separate thread which describes the process to get back to EMUI 8 from custom ROMs. You can find it here.
Just follow the procedure in that thread. You need not even flash the frp unlock thing. After that, follow the process described in this thread.
It's recommended to be on original EMUI 8 before installing base EMUI 8 for hi6250. Follow the process linked in requirements to install EMUI 8 first then follow this spoiler.
Procedure :
Make sure your device is running stock EMUI 8.
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.
Reboot your device to TWRP.
Format the data partition {Wipe > Format data > type "yes"}
Flash fstab.hi6250b.zip from attachments
Check if your device is detected by adb using
Code:
adb devices
.
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).
(Optional, only if you want gapps) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.
(Optional, only if you want gapps) Unmount and Remount system partition as writable. Go to wipe > advanced wipe > Choose system > resize > Swipe➡.
Flash gapps.
Flash stock recovery. Push it with adb using
Code:
adb push -p stock_recovery_ramdisk.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.
Disconnect your device from PC and reboot to recovery(stock one).
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).
Reboot, Cross your fingers and wait.
>Booting is quite different in android 11 ROMs on our device. You'll see the "Your device has been unlocked" screen for more time than usual. Then, you'll see the boot animation (for very short time on subsequent boots) and the device will boot to ROM. So, be patient. (This isn't the case with ROMs upto android 10)
>Face Unlock is working perfectly
Spoiler: Additionals
Additionals:
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
Nothing yet...
Happy Flashing !
{
"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"
}

RESERVED​

Thx for keep looking for the best andorid 11 rom for Honor 6X. Installed it, no issue so far, testing it as a 2nd daily device. Let you know...
Below is my installation procedure using a microsdcard, quite the same as post #1 apart of that.
- on a micro SD card, download:
https://forum.xda-developers.com/attachments/twrp-img.5326857/
https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/fstab.hi6250b.zip/download
https://forum.xda-developers.com/attachments/stock_recovery_ramdisk-img.5321325
FluidOS-1.1-Rum-R-Hi6250-emui8.img extracted with 7zip from https://mega.nz/#!jWQWEJ7Z!cd2S5oy2g8IdUuw5PfQEkSadslojBpFgB6ltUNOpc-w
OPTIONAL: pico gapps from https://sourceforge.net/projects/opengapps/files/arm64/test/20210110/
- insert the micro SD card in your usb debugging enabled Honor 6X (with EMUI 8 or custom rom installed over EMUI8), and connect it to a PC with adb & fastboot
- in adb, "adb reboot bootloader"
- in fastboot, "fastboot flash recovery_ramdisk TWRP.img"
- in fastboot, "fastboot reboot"
- after reboot completed, "adb reboot recovery"
- disconnect the honor 6x from the PC
- in TWRP recovery, Format the data partition {Wipe > Format data > type "yes"}
- in TWRP recovery, flash fstab.hi6250b.zip
- in TWRP Recovery, flash FluidOS-1.1-Rum-R-Hi6250-emui8.img {Install > Install Image > Select > Choose system image > Swipe}
- OPTIONNAL IF GAPPS WANTED: in TWRP recovery, Mount system partition (Mount > check system and unckeck read only OR reboot in recovery).And
resize system (Go to wipe > advanced wipe > Choose system > repair > resize). Then install open_gapps-arm64-11.0-pico-XXXXXXX.zip.
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe}
- in TWRP recovery, reboot to recovery (even if TWRP says no OS installed)
- in Stock recovery, wipe cache and factory reset (error is normal)
- in Stock recovery, reboot and wait
Click to expand...
Click to collapse

Rom is very nice so far , no issue yet!!!!

Djiban said:
Rom is very nice so far , no issue yet!!!!
Click to expand...
Click to collapse
Same with me.

Hello, do you know how can I factory reset in the Huawei ERecovery step at the end ?
I try to do it so but it keep reboot my phone to TWRP recovery, it's like I can't wipe data/factory reset my phone from the stock recovery.
Maybe TWRP is bloking it ? Should I disable something in the TWRP settings ?
Between thanks for yours work !

Kentoto2021 said:
Hello, do you know how can I factory reset in the Huawei ERecovery step at the end ?
I try to do it so but it keep reboot my phone to TWRP recovery, it's like I can't wipe data/factory reset my phone from the stock recovery.
Maybe TWRP is bloking it ? Should I disable something in the TWRP settings ?
Between thanks for yours work !
Click to expand...
Click to collapse
Your mistake is that your using stock erecovery.
You have to use stock recovery. Meaning flashing the stock recovery provided in post 1 over the twrp recovery :
- in TWRP Recovery Flash STOCK_RECOVERY_RAMDISK.img {Install > Install Image > Select > Choose recovery image > Swipe}
- in TWRP recovery, reboot to recovery (even if TWRP says no OS installed)
- in Stock recovery, wipe cache and factory reset (error is normal)
- in Stock recovery, reboot and wait

Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Edit : no it's too painfull without google services haha

Kentoto2021 said:
Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Click to expand...
Click to collapse
Perform a factory reset after flashing gapps too.
Flashing gapps without factory reset crashed chromium based browsers on AOSP 10. This might not be the case with this rom but better do it.

Kentoto2021 said:
Yep thanks, I forget to choose Recovery when I flash the stock recovery ramdisk, so my twrp install it on the last choice that it's system image
To resolve my problem I reinstall my previous system (EMUI 8 for honor 6x) and this time I wipe the david cache, system, cache ... after format the data partition
And I didn't install any OpenGAPPS and it works fine !
A little empty, but I will try without Google services to see if it sweet to me, it saved a lot of battery so that's nice !
Again, I thank you all of you for your amazing work thank you very much my honor 6x can still live haha
Edit : no it's too painfull without google services haha
Click to expand...
Click to collapse
Android without Google services is more and more easy.
Aurora market is a good choice.
I have also some workaround for'GPS localisation and so....

Nevertheless, gapps working fine for me, no device lag cause of it ! All services active and working

Djiban said:
Nvertheless, gapps working fine for me, no device lag cause of it ! All services active and working
Click to expand...
Click to collapse
Same with me. And the power menu controls are just AWESOME.

Dang, I cannot go past installing Huawei USB COM driver to unlock my device (

jottect said:
Dang, I cannot go past installing Huawei USB COM driver to unlock my device (
Click to expand...
Click to collapse
? Didn't get you... Did you mean bootloader unlock? If yes, follow @lmaohelp 's guide mentioned in post 1. He described it very clearly.

Venkata Lochan Nune said:
? Didn't get you... Did you mean bootloader unlock? If yes, follow @lmaohelp 's guide mentioned in post 1. He described it very clearly.
Click to expand...
Click to collapse
Yes, it's clear, read the posts, watched YT video, but one of the steps is installing Huawei USB COM driver to replace the SER driver, and I already tried on 2 computers, Windows 10 (updated) fails to install that driver, and without it, PotatoNV won't 'see' the device.

Venkata Lochan Nune said:
Same with me. And the power menu controls are just AWESOME.
View attachment 5337621
Click to expand...
Click to collapse
Oooh how did you get that ?
I only have this :
Is it Gapps ? I use the nano one

Kentoto2021 said:
Is it Gapps ? I use the nano one
Click to expand...
Click to collapse
Nope, there's an app on play store called "power menu controls" download that. And the other, you could use Tasker(also an app from play store) to create your custom controls like the ones I did for screen rotation.

jottect said:
Yes, it's clear, read the posts, watched YT video, but one of the steps is installing Huawei USB COM driver to replace the SER driver, and I already tried on 2 computers, Windows 10 (updated) fails to install that driver, and without it, PotatoNV won't 'see' the device.
Click to expand...
Click to collapse
what's the procedure you followed to install drivers?
Unzip the attached file, and choose "DriverSetup.exe" and that's it. uninstall these drivers after installing the rom using "DriverUninstall.exe" for mtp to work. The process will ask for reboot in some language(i think Chinese) after uninstalling but it isn't needed.
*These are also the fastboot drivers(but the name in attachments is testpoint drivers).

Kentoto2021 said:
Edit : no it's too painfull without google services haha
Click to expand...
Click to collapse
Indeed! I once tried using AOSP 10 with floss services and without Google ones but yeah it didn't last even a day... lol I flashed gapps within 5 hrs.

Venkata Lochan Nune said:
what's the procedure you followed to install drivers?
Unzip the attached file, and choose "DriverSetup.exe" and that's it. uninstall these drivers after installing the rom using "DriverUninstall.exe" for mtp to work. The process will ask for reboot in some language(i think Chinese) after uninstalling but it isn't needed.
*These are also the fastboot drivers(but the name in attachments is testpoint drivers).
Click to expand...
Click to collapse
Thanks a million! It worked., I just unlocked the bootloader, I did not have these drivers.
Now onto next steps... may take a while, I'm old and slow
Well, did not go too far... when trying to flash twrp (as per this guide:
), I'm getting an error:
fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24466 KB)...
OKAY [ 0.642s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished.
Ideas?
P.S. I also tried
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (24466 KB)...
OKAY [ 0.642s]
writing 'recovery'...
FAILED (remote: image verification error)

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"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 <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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 Recovery
* 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.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G​
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
 
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎  
 
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S20 / S20+ / S20 Ultra Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy S20 / S20+ / S20 Ultra​Only for exynos variants - G980F / G981B / G985F / G986B / G988B (Europe - Global, Single/Dual-SIM)
Disclaimer
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 recovery 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.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy S20 (x1s / G980F / G981B)
Galaxy S20+ (y2s / G985F / G986B)
Galaxy S20 Ultra (z3s / G988B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - x1s / y2s / z3s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Nice, many thanks for the development!

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

corsicanu said:
Official TWRP 3.6.1-* For Galaxy S20 / S20+ / S20 Ultra​Only for exynos variants - G980F / G981B / G985F / G986B / G988B (Europe - Global, Single/Dual-SIM)
Disclaimer
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 recovery 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.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy S20 (x1s / G980F / G981B)
Galaxy S20+ (y2s / G985F / G986B)
Galaxy S20 Ultra (z3s / G988B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - x1s / y2s / z3s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Click to expand...
Click to collapse
Very good job, all working great.
Thanks bro

Zelo dobro delo, vse deluje odlično

Server down? Anybody else?

Great! Thank you so much!!
Edit: Everything's working so far (mtp too), S20+ (y2s) \m/

Seems to be down for G988B

inthedark22 said:
Server down? Anybody else?
View attachment 5607839
Click to expand...
Click to collapse
Few posts above i mentioned that pages are up but builds aren't ready yet.
I posted latest test builds on #2 post.

Possible to add support for SM-G981N?

Hello,
When flashing the multi disabler 3.2 there's a log message :
"Disabling restoration of stock recovery... Found /vendor/recovery-from-boot.p. Disabling... Failed."
Is it normal ?
EDIT : I rebooted and lost TWRP, when I went back into recovery it was the Android one.

naboum said:
Hello,
When flashing the multi disabler 3.2 there's a log message :
"Disabling restoration of stock recovery... Found /vendor/recovery-from-boot.p. Disabling... Failed."
Is it normal ?
EDIT : I rebooted and lost TWRP, when I went back into recovery it was the Android one.
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

I did this with my S10e and S10 without a hitch. They were SM-G970F and SM-G973F. Now I have an S20, SM-G9810. I flashed Hong Kong firmware (CRC TGY), Android 11, G9810ZHS3DUL3 (because I am trying to use microG in place of play store, which I was able to do on both the previous S10 models).
This is not working. After I flash the magisk patched AP (with CP and CSC and BL), reboot to download, then TWRP (x1s) in AP and vbmeta_disabled in CP successfully, but when I hold Vol + and Bixby, this is the error I receive:
RPMB fuse Set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x30F)
FRP LOCK : OFF
OEM LOCK : ON (U)
KG STATUS : CHECKING
WARRANTY VOID " 0x1 (0xE03)
QUALCOMM SECUREBOOT : ENABLE
RP SWREV : B3(1,1,1,3,1,1) K3 S3
SECURE DOWNLOAD : ENABLE
SPU(VALID):5
HDM STATUS : NONE
DID : 200412620E856811
I have USB debugging enabled. I have root access. But, I cannot use Odin to flash TWRP. I tried adb sideload also, even after granting ADB root permission in the magisk manager (but I don't know if that includes recovery ADB sideload). The recovery was the stock recovery as I cannot flash TWRP.

josephgrab said:
I did this with my S10e and S10 without a hitch. They were SM-G970F and SM-G973F. Now I have an S20, SM-G9810. I flashed Hong Kong firmware (CRC TGY), Android 11, G9810ZHS3DUL3 (because I am trying to use microG in place of play store, which I was able to do on both the previous S10 models).
This is not working. After I flash the magisk patched AP (with CP and CSC and BL), reboot to download, then TWRP (x1s) in AP and vbmeta_disabled in CP successfully, but when I hold Vol + and Bixby, this is the error I receive:
RPMB fuse Set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x30F)
FRP LOCK : OFF
OEM LOCK : ON (U)
KG STATUS : CHECKING
WARRANTY VOID " 0x1 (0xE03)
QUALCOMM SECUREBOOT : ENABLE
RP SWREV : B3(1,1,1,3,1,1) K3 S3
SECURE DOWNLOAD : ENABLE
SPU(VALID):5
HDM STATUS : NONE
DID : 200412620E856811
I have USB debugging enabled. I have root access. But, I cannot use Odin to flash TWRP. I tried adb sideload also, even after granting ADB root permission in the magisk manager (but I don't know if that includes recovery ADB sideload). The recovery was the stock recovery as I cannot flash TWRP.
Click to expand...
Click to collapse
SM-G9810 is snapdragon, doesn't show up in supported devices either, so why did you even try this?

Finally, thanks so much for officially porting TWRP to the s20 exy family, been waiting since release .

i have the problem that i cant boot into system anymore after flashing twrp. it always boots to recovery.
factory restet or wipe date after flashing twrp didnt help.
btw ill try to install it to Android 11. shouldnt that work too? cant find any other working guide for twrp on S20 for Android 11

J0KER! said:
i have the problem that i cant boot into system anymore after flashing twrp. it always boots to recovery.
factory restet or wipe date after flashing twrp didnt help.
btw ill try to install it to Android 11. shouldnt that work too? cant find any other working guide for twrp on S20 for Android 11
Click to expand...
Click to collapse
What if you try multidisabler this time?

corsicanu said:
What if you try multidisabler this time?
Click to expand...
Click to collapse
oh of course i installed that too. forgot to mention.. still no success