Related
Team Win Recovery Project 3.1.0
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
{
"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"
}
#include <std_disclaimer.h>
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
Download: dream2lte (Exynos variants - G955F/FD/X/N)
https://twrp.me/devices/samsunggalaxys8plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - General Discussion
Join to get quick support (when you find my guide confusing or meet any unexpected problem).
You can also discuss about ROMs(this group is "neutral" so you can discuss about or review any ROM. Note: Devs: Do NOT aggressively advertise your work.), get latest updates from developers or report possible bugs.
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
XDA:DevDB Information
TWRP for Galaxy S8+, Tool/Utility for the Samsung Galaxy S8+
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2017-04-23
Last Updated 2017-05-04
Changelog:
Apr. 27:
Problems Solved:
1. MTP
2. ADB
3. External SD Mount
Features Added:
F2FS - Note: This change ONLY makes it possible to operate F2FS in TWRP. You still need a F2FS-compatible KERNEL to boot into system with F2FS.
Note: As MTP and ADB are available now, flashable zips will no longer be included. Please download them by yourself and transfer them from your computer to phone if you need them.
Useful Links:
Disable dm-verity and make encryption optional: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk: https://forum.xda-developers.com/apps/magisk
Apr. 24:
Exynos variants united to one "dream2lte".
Apr. 23:
Initial Release
Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Thx Jesse now time to test it on my g955f and root it
here we go ! nice job Jesse!
ok tested on G955F and works
Nice work.
Sent from my SM-G955U using Tapatalk
for the one that roots the device with magisk. when it have random reboots delete the mcregistry files with 000000013 at end and it dont reboots anymore
Ok maybe a stupid question but if I just want the recovery so I can make full nandroid backups (so I can return my pink screen device then just restore the nandroid on a new device without having to set up everything again!!), can I flash this without worrying about it tripping knox?
ewokuk said:
Ok maybe a stupid question but if I just want the recovery so I can make full nandroid backups (so I can return my pink screen device then just restore the nandroid on a new device without having to set up everything again!!), can I flash this without worrying about it tripping knox?
Click to expand...
Click to collapse
flashing custom recovry = tripped knox
nice to see some development so quickly. gonna flash it first thing tomorrow when i get my hands on s8+
thanks for your work jesse ??
Sent from my SM-G935F using Tapatalk
Can someone make a Version for the S8 (non +)?
Do this work on my SM-G950F?
Knox will work with magisk hide ?
Working fine - now preparing for restore with Titanium.
Thank you
OMG that was fast. Thanks
pickles76 said:
Do this work on my SM-G950F?
Click to expand...
Click to collapse
Yes, see my post above
Sweetness! Kudos
Could someone share a link to Samsung USB drivers, please. I mean for windows 10.
Thank you for the Recovery! Hats down.
Korean download ? International ?post #1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about 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.
*/
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open-source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
This is for OFFICIAL and BETA builds of TWRP for the Asus Zenfone 5z (Z01RD, zs620kl)
Device Config:
https://github.com/TeamWin/android_device_asus_Z01RD
Stable Downloads:
ASUS ZenFone 5z 2018
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Test Downloads:
Download File List - twrp-for-z01r - OSDN
Download File List - twrp-for-z01r #osdn
osdn.net
Installation:
Backup everything important off of your device
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of the file is you downloaded):
Code:
fastboot flash boot twrp-3.5.2_10-1-Z01RD.img
NOTE, If you're coming from stock ROM to custom ROM? You MUST format data (wiping data won't work) to remove stock ROM encryption. Wipe > "Format Data" Button > Type "yes" > Keyboard checkbox
(Optional instructions from this point on) Wipe cache and system and then Install the ROM of your choice
Install TWRP installer zip
Reboot to recovery
Install GApps
Reboot to system
Upgrade / Reinstall TWRP instructions
Download desired TWRP installer zip version
Reboot to recovery
Select Install
Tap on install and select the TWRP installer zip you downloaded from step one
Reboot to recovery and confirm that the updated version of TWRP is installed
Nandroid backup/restore
Have an available microSD Card or USB OTG drive
Backup boot, dtbo, system image, vendor image and data (optionally any other partitions you want a backup of) to your external storage device of choice
Once you wish to restore? Reboot to TWRP and format data (Wipe > "format data" button > type yes > keyboard checkbox)
Reboot to TWRP
Restore boot, dtbo, system image and vendor image
Reboot to system
Once it boots to the system without issues? Do not set any lockscreen security and reboot to TWRP
Restore data
Reboot to system
After it finishes boot? Your data and ROM will be restored but sometimes the UI might be incorrect, so reboot to the system again
For the TEST builds of TWRP? Please let me know if this works. If so? I will submit it to Gerrit for official updates.
Credits:
bigbiff for helping me get set up on gerrit.twrp.me for official status and updating official TWRP
JackEage for working on TWRP for this device
All the users who tested my builds of TWRP
Anyone who worked on the open-source kernel of this device
So the next build of official TWRP for Z01RD will include vendor wiping since it seems that the modified prebuilt vendor image flashing can sometimes break the vendor partition for future flashing.
Z01RD: Enable vendor wipe · TeamWin/[email protected]
It seems that users flashing a modified prebuilt vendor runs the risk of corrupting their vendor partition, so against my better judgement as normally there is zero reason we should ever need to do...
github.com
ThE_MarD said:
Installation:
Make sure your bootloader is unlocked
Download the recovery image (and optionally the TWRP installer zip) from above
Reboot into bootloader
Run this command (Change the .img to whatever the name of the file is you downloaded):
Code:
fastboot flash boot twrp-3.5.2_10-1-Z01RD.img
(Optional instructions from this point on) Install ROM of choice
Install TWRP installer zip
Reboot to recovery
Install GApps
Reboot to system
Click to expand...
Click to collapse
I did steps 1-4 in an unlocked bootloader zenfone 5z. After flashing TWRP, my phone is stuck in either TWRP or fastboot; and TWRP can't mount any storage so adb loading firmware isn't possible.
Is there a way to recover from this?
Phone can only receive fasboot commands and TWRP non storage commands
Heyyo @fastrespawn , you will need to format data in TWRP as stock ROM uses Full Disk Encryption and on custom ROMs like LineageOS we use the newer File-Based Encryption.
Wipe > "Format Data" Button > Type "yes" > Keyboard checkbox
Then wipe Cache and system and reboot to recovery and you're ready to flash a custom ROM.
I've expanded the instructions to mention this
ThE_MarD said:
Heyyo @fastrespawn , you will need to format data in TWRP as stock ROM uses Full Disk Encryption and on custom ROMs like LineageOS we use the newer File-Based Encryption.
Wipe > "Format Data" Button > Type "yes" > Keyboard checkbox
Then wipe Cache and system and reboot to recovery and you're ready to flash a custom ROM.
I've expanded the instructions to mention this
Click to expand...
Click to collapse
Thank you!
After flashing twrp-installer-3.5.2_10-1-Z01RD.zip, I cannot touch my screen in twrp. What should I do?
Heyyo @JuanTamqd21 , there is a bug in the touchscreen firmware updater in the kernel, so on LineageOS tbh I just disabled it as I've heard zero touchscreen complaints from any Z01R user that came to LOS from ZenUI Q .123 build as that is the last device firmware for Z01R. You can try rebooting to TWRP again or wait a few minutes then tap the power button a few times and sometimes that will get the touchscreen working. Otherwise? Ask the maintainer of that ROM to also do the same thing I did.
https://review.lineageos.org/c/LineageOS/android_kernel_asus_sdm845/+/312874
ThE_MarD said:
Heyyo @JuanTamqd21 , there is a bug in the touchscreen firmware updater in the kernel, so on LineageOS tbh I just disabled it as I've heard zero touchscreen complaints from any Z01R user that came to LOS from ZenUI Q .123 build as that is the last device firmware for Z01R. You can try rebooting to TWRP again or wait a few minutes then tap the power button a few times and sometimes that will get the touchscreen working. Otherwise? Ask the maintainer of that ROM to also do the same thing I did.
https://review.lineageos.org/c/LineageOS/android_kernel_asus_sdm845/+/312874
Click to expand...
Click to collapse
thanks for the guide. I will try it now
Heyyo, a new test build is up! twrp-3.6.0_11.0-Z01RD-test17-UNOFFICIAL contains the upgrade to TWRP 11 branch and also added in system/vendor wiping as I keep getting nagged about this useless feature lol oh well...
Release twrp-10 twrp-3.6.0_11.0-Z01RD-test17-UNOFFICIAL - twrp-for-z01r - OSDN
Release twrp-10 twrp-3.6.0_11.0-Z01RD-test17-UNOFFICIAL - twrp-for-z01r #osdn
osdn.net
twrp-3.6.0_11.0-Z01RD-test18-UNOFFICIAL is up! Contains fixes for the Boot Control HAL so that flashing ROM images will work correctly and properly switch to inactive partition upon reboot plus the decryption and other updates from test17
Release twrp-for-z01r twrp-3.6.0_11.0-Z01RD-test18-UNOFFICIAL - twrp-for-z01r - OSDN
Release twrp-for-z01r twrp-3.6.0_11.0-Z01RD-test18-UNOFFICIAL - twrp-for-z01r #osdn
osdn.net
Hii
Heyyo, a new test build is up! twrp-3.7.0_12-0_UNOFFICIAL-20230222-01-Z01RD contains a bootctrl hal fix
Release twrp-for-z01r twrp-3.7.0_12-0_UNOFFICIAL-20230222-01-Z01RD - twrp-for-z01r - OSDN
Release twrp-for-z01r twrp-3.7.0_12-0_UNOFFICIAL-20230222-01-Z01RD - twrp-for-z01r #osdn
osdn.net
Official TWRP for the Asus Zenfone 5z has been updated with the bootctrl HAL fix!
{
"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"
}
TWRP FOR SAMSUNG GALAXY F62/M62 (EXYNOS 9825) (*ANDROID 11, M62 UNTESTED)
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Team Win Recovery Project 3.x, or Twrp3 for short, is a custom recovery built with ease of use and customisation in mind. It's a full 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.
TWRP built for the Samsung Galaxy F62. It is a stable build, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. SAMSUNG ODIN is used to flash this recovery.
NOT TESTED ON ANDROID 12, IT MAY GIVE BLACK SCREEN ERROR AFTER FLASH SO FLASH AT YOUR OWN RISK!!!
Downloads:TWRP AND MAGISK7zipODIN FOR F62/M62
NOTE: ONLY FOR F62- PREPATCHED MAGISK IMAGE WILL WORK. M62 USERS WILL HAVE TO FIRST PATCH STOCK BOOT IMAGE WITH MAGISK ROOT IT AND THEN PROCEED WITH TWRP INSTALLATION PROCESS
TO FLASH PRE PATCHED IMAGE MAKE SURE YOU ARE FIRST IN THE STOCK FIRMWARE BUILD OF THE RESPECTIVE PATCHED IMAGE
BUGS:MTP DOSEN'T WORKSTABLITY:Fully Stable without errors (Tested on SAMSUNG GALAXY F62)
BY DEFAULT SWIPE TO ALLOW MODIFICATIONS IS DISABLED. TO MODIFY SYSTEM
BOOT TWRP>ADVANCED>TERMINAL> TYPE mount -o rw,remount /system_root
Gather Things-1.ODIN
2.STCOK FRIMWARE
3.EXTRACT THE SUPER.IMG.LZ4 FROM FIRMWARE (AP) AND ARCHIVE IT TO .TAR USING 7ZIP
4. DETERMINE YOUR ANDROID VERSION. (ANDROID 11 OR ANDROID 12)
Installation (Odin Windows)
If you already have the bootloader unlocked you can skip to step 6.
* Please be aware all your data will be erased including internal storage and phone will reboot!!
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);
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;
Download TWRP AND MAGISK from above.
Flash the TWRP recovery in AP Section of Odin and Disabled VBmeta in USERDATA section of Odin
Uncheck auto reboot and start flash
Force reboot to TWRP recovery. Press vol- and power button to restart and immediately press vol+ and power button to boot the TWRP.
In TWRP recovery press Wipe and then Format Data and Type yes to wipe.(DON'T REBOOT DEVICE YET)
MAKE SURE TO COPY PASTE THE ZIP FILE ONTO YOUR SDCARD FOR FLASHING IN TWRP. Press home button and now press install and tap storage and select the SDCARD and navigate to the Multi Disabler.zip.
Flash the Multi Disabler zip from your SD CARD.
Force reboot the device to download. Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Download latest Stock FIRMWARE and extract the firmware files.
Rename AP file from .md5 to .tar and extract the super.img.lz4 file from the AP file. (super.img.lz4 is the system OS)
Now Archive the Super.img.lz4 to .TAR format using the 7zip Software.
Place just Archived super.tar in AP Section of Odin (Flash the file you just archived to .tar format.)
Uncheck auto reboot and start flash
Now again boot into download mode by pressing the vol up + vol down + usb cable plugged to a pc to start the phone in download mode
Flash your respective android version MAGISKboot file in AP of Odin. (FLASH FROM PROVIDED ANDROID VERSION FOLDER.)
*If your android version is 11 then flash the MAGISKbootA11.
*If your android version is 12 then flash the MAGISKbootA12.
NOTE: ONLY FOR F62- PREPATCHED MAGISK IMAGE WILL WORK. M62 USERS WILL HAVE TO FIRST PATCH STOCK BOOT IMAGE WITH MAGISK ROOT IT AND THEN PROCEED WITH TWRP INSTALLATION PROCESS
TO FLASH PRE PATCHED IMAGE MAKE SURE YOU ARE FIRST IN THE STOCK FIRMWARE BUILD OF THE RESPECTIVE PATCHED IMAGE
After flashing force restart the device by Pressing volume down and power button to restart the device
The device should Auto boot to TWRP after boot looping 2 times. It will show you ANDROID RESCUE PARTY TRIGGER in TWRP LOGS. (Press below right cornet button to show up the logs)
Now again flash the Multi Disabler zip from your SDCARD.
REBOOT THE DEVICE AFTER FLASHING THE ZIP.
*If you fail to boot os, then you haven't followed a step or missed a step.
Flash the total Firmware bact to device using Odin and start the steps again.
******You can always revert to stock by flashing full frimwere with odin.
*FIRST BOOT WILL TAKE AROUND 10 MINS, SO DON'T INTERRUPT THE PROCESS UNTIL YOU GET STARTING ANDROID...THAT'S IT YOU WILL HAVE A TWRP RECOVERY.
Credits : Hibiscus, Sushrut1101, Shuvam
OFFICIAL TELEGRAM
Mod edit : Link removed (TG allowed only for development threads)
Samsung Galaxy F62/M62 | OFFICIAL
Official Discussion group for ➤
Samsung Galaxy F62/M62
Official Channels & Groups ➤
• Updates : @SamsungGalaxyF62Updates
• Off-Topic : Mod edit : Link removed (TG allowed only for development threads)
Great work!
If it doesn't work on M62 I can convert it.
Thanks for making this possible
@rc chanu please check your inbox, you have an important PM
{
"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