{
"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:
/*
*Disclaimer
*
* 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 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.
*/
Introduction
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox version: R11.1
For device: a32
Maintainer: Ahnet ( @Captain_cookie_200 )
OrangeFox source:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Device tree:
GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6.
Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6. - GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Sa...
github.com
Kernel Source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features:
Code:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included assorted customizations
Inbuilt patches, like Magisk and password reset patch
Several addons
Password protection
Fully open-source
Frequently updated
Status
Stable-ish
Tested on:
SM-A325F (by me)
SM-A325M (by @filipedonato)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings is fixed but for fixing settings such as theming resetting on reboot is by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
Installation
Code:
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:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. 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).
5. Your device will boot into download mode with a warning. Accept it.
6. 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.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename OrangeFox recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. 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:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: OrangeFox TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. 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 OrangeFox up and running now.
Post-Installation:
MUST: Trigger Multi-disabler.
1. In OrangeFox, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
1. In OrangeFox, go to Backup
2. 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, PBRP and the likes)
1. Download the recovery image.
2. Copy it to phone, then reboot to OrangeFox (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. 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.
Credits:
To the OrangeFox and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.
reserved
reserved
I have tried to talk to various developers about the settings not saving issue. They have no idea. I have myself tried playing around with the tree but nope. So unless someone has a fix for this i have no idea
New Build!
Whats new?
Fixed the settings such as theming resetting on reboot by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
If you see the recovery trying to decrypt storage dont worry about it. its just because of this. It does nothing.
It's stable? I mean, i can install gsi's and zips?
ApiYoshi said:
It's stable? I mean, i can install gsi's and zips?
Click to expand...
Click to collapse
yes i use orangefox. flashing gsi works fine. same goes with zips
Captain_cookie_200 said:
yes i use orangefox. flashing gsi works fine. same goes with zips
Click to expand...
Click to collapse
Ok, i flashed it and is awesome!! Thanks for great work brother!
ApiYoshi said:
Ok, i flashed it and is awesome!! Thanks for great work brother!
Click to expand...
Click to collapse
You should make a telegram group
ApiYoshi said:
You should make a telegram group
Click to expand...
Click to collapse
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Works in A32 A325M Brazil variant.
really nice you are keeping the a32 alive!
applesucksLmao said:
really nice you are keeping the a32 alive!
Click to expand...
Click to collapse
i did nothing tbh. all the credit goes to the people who put effort in making twrp work i just copied and built it. all the credit goes to them
Captain_cookie_200 said:
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Click to expand...
Click to collapse
Ooh, i undertand
One question, you will update the recovery when an update came out?
ApiYoshi said:
One question, you will update the recovery when an update came out?
Click to expand...
Click to collapse
yes i will try
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Seth Ofc said:
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Click to expand...
Click to collapse
sorry i didnt include it. but i think i specified. rename OrangeFox recovery img file to recovery.img
then use 7zip or winrar or any other archiver and then add to archive. There select tar and compress. I'll include tar files in next builds by default
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Seth Ofc said:
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Click to expand...
Click to collapse
use a generic system image.
if you want heres a list: here
Related
{
"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 S10/e/+/5GOnly for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (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:
S10e - beyond0lte - G970F/G970N
S10 - beyond1lte - G973F/G973N
S10+ - beyond2lte - G975F/G975N
S10 5G - beyondx- G970F/G977N
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 down + bixby key + 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 down + bixby key + 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 + bixby + 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 down + bixby key + 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 down + bixby key + 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 + bixby + 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 - beyond0lte / beyond1lte / beyond2lte / beyondx
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.
further reading moved to #2
Thanks for your work, good job
Amazing work as always Corsi, thank you so much!
Thanks Sir I'm fan of your hadesRom and I'll wait your new work//from Thailand
Well done as always
Great work as aways @corsicanu! Keep it up and don't worry about the others, OFFICIAL is yours, haters gonna hate...
Cheers!
Can I just flash this to recovery in ians twrp that I currently have?
Eidluci said:
Can I just flash this to recovery in ians twrp that I currently have?
Click to expand...
Click to collapse
What it says on the box...
If you already have TWRP installed, download .img file according to instructions from step 9 from above, and install from your current TWRP with Install image - browse to image location and select - Recovery
is this better than the ianmcd 3.4.0.3 TWRP?
r3xx3r said:
is this better than the ianmcd 3.4.0.3 TWRP?
Click to expand...
Click to collapse
My thoughts exactly!
For that matter, is it better than Modpunk's 3.4.0-0?
There are various custom ROM Modders stating use this (name) TWRP - all stating different TWRPs.
Presently we have 3 different Mods versions of TWRPs for the S10- family.
I, for one, have difficulty in seeing the difference between the TWRPs???
One is compatibility, two is ian's dropping the support.
Hi! I have problem with latest samsung firmware and twrp. I can get root and i can install twrp from 0. But recovery can't access data folder (sam folders with strange name) and multi disabler put the phone in a "stack at samsung logo" state! Why?
rubino25 said:
Hi! I have problem with latest samsung firmware and twrp. I can get root and i can install twrp from 0. But recovery can't access data folder (sam folders with strange name) and multi disabler put the phone in a "stack at samsung logo" state! Why?
Click to expand...
Click to collapse
You have to format /data to decrypt your device. Be aware that you'll loose all your data. Read FAQ, it includes all the info you need.
Cheers!
AndrzejDwo said:
You have to format /data to decrypt your device. Be aware that you'll loose all your data. Read FAQ, it includes all the info you need.
Cheers!
Click to expand...
Click to collapse
Thanks!
Norup58 said:
My thoughts exactly!
For that matter, is it better than Modpunk's 3.4.0-0?
There are various custom ROM Modders stating use this (name) TWRP - all stating different TWRPs.
Presently we have 3 different Mods versions of TWRPs for the S10- family.
I, for one, have difficulty in seeing the difference between the TWRPs???
Click to expand...
Click to collapse
If you're not using any modpunk rom (such as his LineageOS) - you'll need to use his twrp - no way around that. - it's really not recommended if you want to run any of the ROMs besides that as it'll likely not work.
Ianmcd twrp is best used on any rom/fw below DTI8 (so anything from DTH7 and below) - This is losing support soon and no longer will be updated.
(tldr: unless you're planning to use my crdroid 7, Ivan's lineage 18 or latest 17.1 - I recommend you keep to this twrp until other roms are updated)
This twrp here (corsicanu) is now the recommended twrp from now on as long as you're on DTI8 or above and flashing DTI8 based roms.
Official builds are up, updated the links and the instructions, read carefully everything before you brick your phone.
Congrats @corsicanu. As always, quality work. Keep it up mate. ??
{
"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.
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S21 FE 5G G9900 and G990B.
Download & Guide:
1. Unlock your bootloader.
2. Download S21 FE 5G: r9q.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
- Haptic feedback is currently not working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for testing and fix touch
Sources:
Kernel tree
Device tree
Changelog:
01.05.2022 - Initial Release.
Tested on BVB3 and CVC6 roms, both are working perfect.
On CVC6, wiping data worked and multidisabler seems to be working too. My phone is rebooting and after all data recover I can tell if it done well completely.
Edit : backup is working, install zip is working, to me there is no bug. Just one weird thing, after the update I directly installed TWRP, it worked fine. Then decrypted data and reboot. When finished, I wanted to reboot recovery via Vol Up and power, it always boot up to system, I née needed to reflash TWRP to access it again.
Except this little thing, it works great.
Many many thanks !!
Great cant wait to test whenever I got some time to clear it all and start over :/
Any1 who tested yet?
How do I unlock my bootloader?
Mr NI said:
How do I unlock my bootloader?
Click to expand...
Click to collapse
If you bought a US Version, i.e. Carrier brands, you cannot do so, even if you have an unlocked. All US Snapdragon device after like S6 they've kicked us out. If you have a Exnos.
1. Open Settings scroll to about device
2. Tap on Software Information tap build number 5 times to show hidden developer settings.
3. Scroll to you see OEM Unlock.
4. Refer to guides online after step 3
Dr.Lost said:
If you bought a US Version, i.e. Carrier brands, you cannot do so, even if you have an unlocked. All US Snapdragon device after like S6 they've kicked us out. If you have a Exnos.
1. Open Settings scroll to about device
2. Tap on Software Information tap build number 5 times to show hidden developer settings.
3. Scroll to you see OEM Unlock.
4. Refer to guides online after step 3
Click to expand...
Click to collapse
well isnt that ass
Doghan13 said:
Tested on BVB3 and CVC6 roms, both are working perfect.
On CVC6, wiping data worked and multidisabler seems to be working too. My phone is rebooting and after all data recover I can tell if it done well completely.
Edit : backup is working, install zip is working, to me there is no bug. Just one weird thing, after the update I directly installed TWRP, it worked fine. Then decrypted data and reboot. When finished, I wanted to reboot recovery via Vol Up and power, it always boot up to system, I née needed to reflash TWRP to access it again.
Except this little thing, it works great.
Many many thanks !!
Click to expand...
Click to collapse
I am considering buying the smartphone. But the root access ist important for me.
Need you to enter twrp again to have root access after a restart and a connection to pc to enter twrp? I ask because my Galaxy A50 loose after every restart the root access and I need to enter the twrp with a connection to pc to fix it.
icalgoos said:
I am considering buying the smartphone. But the root access ist important for me.
Need you to enter twrp again to have root access after a restart and a connection to pc to enter twrp? I ask because my Galaxy A50 loose after every restart the root access and I need to enter the twrp with a connection to pc to fix it.
Click to expand...
Click to collapse
When you make all right, unlock bootloader, twrp, vb_disabler and then magisk. Then you have a rooted phone with advantages and disadvantages. No loosing after reboot. But no OTA too
Does nandroid backups work with this version and android 12?
how can we update the phone say to OneUI 5.0 in the future and keep root.
stuntora said:
how can we update the phone say to OneUI 5.0 in the future and keep root.
Click to expand...
Click to collapse
Patch the fw with Magisk, use Magisk install instructions and possibly replace recovery.img with TWRP so that you keep it and flash any multi disabler again that you may have already flashed.
Is it mandatory to format data when we already have Magisk installed ?
If you are full stock, then disabling vbmeta will trigger a wipe
afaneh92 said:
If you are full stock, then disabling vbmeta will trigger a wipe
Click to expand...
Click to collapse
Just a thought, I have stock ROM october patch and I have Magisk installed properly with Zygisk activated.
I obviously already done a full wipe for this.
If one day I would like to install TWRP, a full wipe will be mandatory ?
I'm asking since I understand that full stock means no Magik installed, which is not my case.
Benjamin2557 said:
Just a thought, I have stock ROM october patch and I have Magisk installed properly with Zygisk activated.
I obviously already done a full wipe for this.
If one day I would like to install TWRP, a full wipe will be mandatory ?
I'm asking since I understand that full stock means no Magik installed, which is not my case.
Click to expand...
Click to collapse
Yes its mandatory
does smali patcher work on rooted galaxy s21 fe?
Hello Mohammad,
After rooting I keep getting "ERR_INTEGRITY" errors in logcat, so some apps (especially Samsung ones) don't work properly. Is it normal since you wrote "Encryption not fully working", or am I doing something wrong?
Thank you!
MoveToZero said:
Hello Mohammad,
After rooting I keep getting "ERR_INTEGRITY" errors in logcat, so some apps (especially Samsung ones) don't work properly. Is it normal since you wrote "Encryption not fully working", or am I doing something wrong?
Thank you!
Click to expand...
Click to collapse
Usually because bootloader unlocked, use safetynet fix module.
Team Win Recovery Project
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 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.
*/
{
"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"
}
Disclaimer:
I am not responsible about any damage of any kind that this custom binary may cause.
Please pay attention to this post & related ones before proceeding and follow the guide correctly. 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 the community's Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs.
What's TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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.
Read more about TWRP here: https://twrp.me/about/
How do I flash and set it up correctly?
Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.
Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.
Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.
Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:
Spoiler: Unlock the bootloader
Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).
Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.
Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.
Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.
Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).
Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.
Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.
Once TWRP has booted you need to format again your data partition in order to be able to boot in system again. To do so touch Wipe>Format Data and follow the instructions in screen.
Bugs:
Decryption will only work if no password/PIN/pattern is set in Android (One UI).
Download:
Galaxy A52s 5G (a52sxq):
twrp.me
Bootloader/Modem collection:
GitHub
Sources:
Kernel source code: https://github.com/BlackMesa123/android_kernel_samsung_sm7325/tree/sep-14.1/twrp-12.1
Device tree: https://github.com/TeamWin/android_device_samsung_a52sxq
Changelog:
Check Post #2.
A52s 5G Community Telegram Groups:
General
Development
Credits:
Samsung for the kernel source code
TeamWin for their awesome recovery
@Captain_Throwback for his help and troubleshooting
@ShaDisNX255 & @ronardnx for testing out the recovery
Changelog:
Please note that this only includes device-specific changes. For global TWRP changes, go to twrp.me.
20230104 (3.7.0_12-3)
- Fix /vendor backup restoring
20221224 (3.7.0_12-2)
- Updated kernel to DVK5
- Support Android 13 decrypt with no password
- Fix /efs, /sec_efs backup
20221208 (3.7.0_12-1)
- Fix fastbootd
- Disable stock recovery patching in /vendor
20221012 (3.7.0_12-0)
- First release
It's been a while since I released something here in XDA. I'm happy to join the modding train again with this custom recovery, hoping to see more cool stuff come out for this device soon
Amazing work, always happy to test. Great step towards more development.
Nice job plus Nice instructions. Thanks a lot
Most peru dev
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Brilliant!! Thankz for this. Now bring on custom stuff lol.
Essentrix said:
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Click to expand...
Click to collapse
Am a bit also confused with all this files.. i suppose recovery image is the only thing needed for a allready rooted phone right?
Finally!!
Essentrix said:
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Click to expand...
Click to collapse
BlueChris said:
Am a bit also confused with all this files.. i suppose recovery image is the only thing needed for a allready rooted phone right?
Click to expand...
Click to collapse
Yes, the guide is for those that are starting with an unrooted device. If you already had the old TWRP or have installed a patched vbmeta you can just flash the new recovery.img without any extra steps
New minor build released to mitigate the /data and /efs backup errors. If you're still having issues, try to delete the /sdcard/TWRP folder and reboot again to recovery.
New version works perfect. Thanks!!
BlackMesa123 said:
Yes, the guide is for those that are starting with an unrooted device. If you already had the old TWRP or have installed a patched vbmeta you can just flash the new recovery.img without any extra steps
Click to expand...
Click to collapse
Ok i was rooted and i passed only the recovery. Now i rebooted in twrp and the phone asks for a password of myne... i tried to put my pin and then it tries to decrypt FBE it says for user 0 but stays there for ever...
BlueChris said:
Ok i was rooted and i passed only the recovery. Now i rebooted in twrp and the phone asks for a password of myne... i tried to put my pin and then it tries to decrypt FBE it says for user 0 but stays there for ever...
Click to expand...
Click to collapse
Seems like decrypt currently works when no lockscreen password/PIN is set. I'm going to look at this
BlackMesa123 said:
Seems like decrypt currently works when no lockscreen password/PIN is set. I'm going to look at this
Click to expand...
Click to collapse
I changed to pattern and the same is huppening. If i try to change to nothing it will remove my fingerprints etc.. its not biggy but this could be a solution for me?
Yeap i changed to none and is working now.... i will do a full backup now and then i will put the security on again.
Thx anyway.. a full phone backup was what i was needing.
BlueChris said:
I changed to pattern and the same is huppening. If i try to change to nothing it will remove my fingerprints etc.. its not biggy but this could be a solution for me?
Click to expand...
Click to collapse
Unfortunately with the current build you'll have to choose between disabling encryption in your /data partition or remove any kind of lockscreen protection. I'm already working on fixing this issue, found out it's due to gatekeeper not working correctly
BlackMesa123 said:
Unfortunately with the current you'll have to choose betweeb disabling encryption in your /data partition or remove any kind of lockscreen protection. I'm already working on fixing this issue, found out it's due to gatekeeper not working correctly
Click to expand...
Click to collapse
No worries m8, take your time and again thank you for this.
BlueChris said:
No worries m8, take your time and again thank you for this.
Click to expand...
Click to collapse
I have some bad news: unfortunately decrypt with password/PIN set in lockscreen is not supported in the TWRP itself, so posting a new build with fixed gatekeeper would be useless anyway. As soon as the android-12.1 TWRP branch fixes this issue I'll be posting a new build for the recovery, hoping this issue will be addressed asap
{
"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:
/*
*Disclaimer
*
* 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 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based On TWRP version: 3.7.0
PitchBlack version: 4.0
For device: a32
Maintainer: Ahnet (@Captain_cookie_200 )
PitchBlack source:
PitchBlack Recovery Project
Open-Source Android Recovery Project. PitchBlack Recovery Project has 216 repositories available. Follow their code on GitHub.
github.com
Device tree: https://github.com/ahnet-69/pbrp_device_samsung_a32
Kernel source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features
Code:
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Status
stable-ish
Tested on:
SM-A325F (by me)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings
Installation Instructions
Code:
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:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. 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).
5. Your device will boot into download mode with a warning. Accept it.
6. 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.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename PBRP recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. 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:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: PBRP TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. 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 PBRP up and running now.
Post-Installation:
MUST: Trigger Multi-disabler.
1. In PBRP, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
1. In PBRP, go to Backup
2. 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)
1. Download the recovery image.
2. Copy it to phone, then reboot to PBRP (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. 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.
Credits:
To the PBRP and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.
@LehKeda and his team for lzma compression tool from here.
reserved
reserved
For people wondering why this recovery takes a long time to boot.. its because our phone only has 32mb for recovery partition. So its impossible. The original builds were around 35MB. I had to resort to lzma compression which is slower. but hey atleast it boots