{
"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 UNOFFICIAL builds of TWRP for the Motorola G30 (caprip)
Device Config:
GitHub - TeamWin/android_device_motorola_caprip
Contribute to TeamWin/android_device_motorola_caprip development by creating an account on GitHub.
github.com
Official Downloads:
https://twrp.me/motorola/motorolamotog30.html
Test Downloads:
https://osdn.net/projects/twrp-for-caprip/releases/
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 boot twrp.img
(Optional instructions from this point on) Install TWRP installer zip
Reboot to recovery
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:
mistersmee for his TWRP tree for the Motorola Moto G9 Power (cebu) that this caprip tree is based upon
Samw662 for encouraging me to work on this and help out caprip owners since I don't own one plus testing these builds
Heyyo, initial public release is twrp-3.6.2_12-0_UNOFFICIAL-20220929-03-caprip which is based on TWRP 12.1 branch. Please test decryption on either A12 or A13 ROMs as I'm unsure if it is setup correctly or not.
Please report any bugs in this thread
Hey, I cannot see my internal storage on this version of twrp. I am on android12 srtock rom
Heyyo @anuragnahata , can you please test this?
https://build.twrp.me/twrp-3.7.0_12-0-caprip.img
Code:
fastboot boot twrp-3.7.0_12-0-caprip.img
If you have any problems with this build too, then please submit logs either here or in PM. I've had other caprip owners say everything on that TWRP build works fine for them
Touchscreen doesn't work. Maybe because my software channel is reteu?
Heyyo, TWRP 3.7.0_12 official is meow up on the TWRP website! Thanks to @Sammm77 for encouraging me to work on this for a device I don't even own and for helping test it out.
@Leogami9009 can you please provide logcat? Tbh I'm not even sure what are all the touchscreen drivers that caprip even uses but I did try to reference the kernel source code but maybe I missed one? Also, are you on the official build or a test build?
ThE_MarD said:
Heyyo, TWRP 3.7.0_12 official is meow up on the TWRP website! Thanks to @Sammm77 for encouraging me to work on this for a device I don't even own and for helping test it out.
@Leogami9009 can you please provide logcat? Tbh I'm not even sure what are all the touchscreen drivers that caprip even uses but I did try to reference the kernel source code but maybe I missed one? Also, are you on the official build or a test build?
Click to expand...
Click to collapse
For some people ek touch does not work, but for the vast majority it works perfectly. You have to wait 15 seconds when starting TWRP but after that it works fine. Excellent work friend.
Leogami9009 said:
Touchscreen doesn't work. Maybe because my software channel is reteu?
Click to expand...
Click to collapse
No, it's not because of your channel, surely the developer skipped a display driver. Maybe with time we will solve it, if you want to contribute send logcat and dmesg to the developer.
@Sammm77 if touchscreen doesn't work right away? Odds are it's just the touchscreen driver still initializing and maybe checking firmware and such. Focaltech for example is really known for having touchscreen issues as well on TWRP because of a long init period. Some touchscreens have a way to manually reset the kernel driver I think but I'm unsure if caprip has a method to do so.
My Asus Zenfone 5z (Z01R) has focaltech touchscreen and has issues with TWRP where sometimes it's intermittent that touchscreen works but it always works in the ROM since the ROM boot time is a lot longer than TWRP
Ok, i let the phone to load the driver and it works, thank you all!
Is it normal for this recovery to not be able to resize system/ not being able to enter on internal storage?
ThE_MarD said:
@Sammm77 if touchscreen doesn't work right away? Odds are it's just the touchscreen driver still initializing and maybe checking firmware and such. Focaltech for example is really known for having touchscreen issues as well on TWRP because of a long init period. Some touchscreens have a way to manually reset the kernel driver I think but I'm unsure if caprip has a method to do so.
My Asus Zenfone 5z (Z01R) has focaltech touchscreen and has issues with TWRP where sometimes it's intermittent that touchscreen works but it always works in the ROM since the ROM boot time is a lot longer than TWRP
Click to expand...
Click to collapse
No, it doesn't load right away, that would be great but it doesn't. You have to wait a few seconds. Do you think that can be solved?
Leogami9009 said:
Is it normal for this recovery to not be able to resize system/ not being able to enter on internal storage?
Click to expand...
Click to collapse
internal storage must be decrypted. Maybe later I'll make a tutorial on how to do that.
Heyyo, well it seems there's some communication breakdown as I was under the impression that decryption worked but I guess it doesn't lol oof.
Ok, can someone who is decrypted please try to decrypt and when it fails send me the recovery.log and logcat?
(No replies? Maybe decryption does actually work and there's some more miscommunication???)
Sorry for the long waiting, but i forgot to get the logcat and recovery.txt. I tried today to get it, but i wasn't able to. it says that it was saved in data/media/ so i tried to get it with adb pull but it says "failed to stat remote object 'data/media/logcat.txt': Permission denied". But i think i should mention that i've installed twrp by flashing the .zip with termux (my phone was rooted with magisk and it had the magic flasher module). I installed it this way because the booted .img touchscreen didn't worked even if i let it some minutes for the driver to load. And when i've flashed the .zip with termux my device wasn't rooted anymore. So i can't use adb root. But when i flash the patched boot.img back, the recovery just disappears.
Sorry for bad english
@Leogami9009 hmm, maybe it's just because of the prebuilt kernel? Not too sure though tbh but I think there's kernel source code somewhere so I might see if that would help? From what I saw from Motorola's source code release there was only like, 2 drivers they used for touch
ThE_MarD said:
@Leogami9009 hmm, maybe it's just because of the prebuilt kernel? Not too sure though tbh but I think there's kernel source code somewhere so I might see if that would help? From what I saw from Motorola's source code release there was only like, 2 drivers they used for touch
Click to expand...
Click to collapse
That's why twrp doesn't work on ilitek screens, on this device.
@Leogami9009 I think I just realized you're trying to get some logcat.txt on the device, but you should be using a PC or something to get logcat like this:
Via Windows PowerShell:
Code:
adb logcat | Tee-Object logcat.log
Via Linux Terminal:
Code:
adb logcat | tee logcat.log
And whatever folder you are in when you run it will have that logcat.log
Also, which build of TWRP are you on?
Plus twrp-installer.zip is meant to be installed whilst in recovery and not while booted into the system. Installing TWRP does remove root so if you want to maintain that you must reinstall it after rebooting to recovery.
Here is the logcat, i let it for 5 minutes:
I have twrp 3.7.0, i realized yestarday that if i root with twrp i can have both root and the recovery, and i tried to flash the zip with the twrp already installed ( nothing different)
Something intresting is that if i format data with twrp and reboot in recovery, it detects the internal storage (when i try to select the internal storage it says it has 15000mb or something like that), but after i set up the phone, it says 0mb. Maybe is something about the partition format? Idk, i can put a sd card to see if it gets detected or not.
Another thins is that when twrp starts it says "Unable to mount storage" and "Unable to mount /data/media/TWRP/.twrps" two times and when i try to manually select the Internal Storage and data partition and format those it says "Unable to mount 'data' (Invalid argument)" "Unable to wipe /data."
ahoy, the release version does not work on my phone, also EU, build S0RCS32.41-10-9-2
I mean, I fastboot boot twrp-3.whatever.img and it boots to that, but touchscreen doesn't work, and adb doesn't work, only thing I can do is turn screen on-off, lol, even after waiting several minutes
also the kernel sources are iirc like, on github, under various tags and branches
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"
}
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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
- Selinux is enforcing
- FBE build, don't use twrp for these builds
- Custom kernels are NOT supported
- Read the instructions carefully
Downloads
- Here
Flashing instructions
- Here (Suggestions for improving the guide are welcome)
Sources:
- LineageOS
- Kernel Tree
Happy modding!
Reserved
Good news
Great!
Okay but does it run Crysis?
Stonks
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
a1291762 said:
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
Click to expand...
Click to collapse
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
for now you can use some old build i made https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220319-UNOFFICIAL-daisy.zip
i should upload a new one as soon as possible (maybe tomorrow/today)
Its_Vixano said:
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
Click to expand...
Click to collapse
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
My recovery process:
* Boot into TWRP
* Flash Lineage 18.1
* Boot into (Lineage 18.1) recovery
* Install Lineage 19.1
* Boot into (Lineage 19.1) recovery
* Flash Gapps and Magisk
* Boot into system
a1291762 said:
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
Click to expand...
Click to collapse
Avoid using the 'fastboot boot' command, somehow it doesn't works
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Its_Vixano said:
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Click to expand...
Click to collapse
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
a1291762 said:
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
Click to expand...
Click to collapse
It should work, but sometimes it takes a couple of tries with reboots in between. I did not find a pattern yet, but in general flashing boot and doing the power vol+ combo should be fine. Maybe it's a timing thing, not sure. Try to switch which button you press first maybe, or try to press them at the exact same time. A bit weird, yeah
UPDATE: pressing the + button just a bit earlier seems to be doing the trick for me!
just done a test build for fixing the privapp permission issues (random bootloops caused by some normal reboots), seems fine here but i don't really trust my self
https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220329-UNOFFICIAL-daisy.zip
report if something will be wrong with it
edit: Apparently it's fine so
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Its_Vixano said:
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Click to expand...
Click to collapse
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Yep, that's the right way to update the rom
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
nabav said:
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
Click to expand...
Click to collapse
- Just follow the instructions, everything is written here
- Should be stable enough for daily driving it, sadly i don't use daisy anymore as a 'primary' device
- I also use fdroid and adaway and they don't require root
a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Hi a1291762,
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used? If it is an upgrade procedure rather than an update procedure (are those to be expected at all?) can you give a more detailed explanation? I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?). Does your procedure work with fastboot or adb? Whatsoever, though it is not my daily driver I am very happy with my Mi A2 Lite with TWRP and Magisk but I also like playing... (with 75 years).
Thanks for all of your efforts!
grufty47
grufty47 said:
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used?
Click to expand...
Click to collapse
The OP guide seems to be written for people coming from something other than Lineage. The first part of it sets up the Lineage recovery and formats user data.
Since I was coming from Lineage and already had the recovery, I figured I could skip those steps. The OP guide says you can skip formatting data if you're coming from Lineage and I figured the recovery can't have changed too much.
I don't know how much testing was done for a Lineage 18 -> 19 upgrade. It worked for me but I barely had anything installed when I did it. Make backups in case of data loss and all that.
Something I don't understand in the OP guide is the suggestion to use the copy_partitions script. It only seems useful if your phone is somehow in an odd situation where miscellaneous A and B partitions don't match? It can't hurt to run it I guess.
grufty47 said:
can you give a more detailed explanation?
Click to expand...
Click to collapse
My 18->19 upgrade process matches the 19 "OTA" process. Refer to the OP guide for screenshots and details.
1. Boot to recovery
2. Sideload the lineage zip
3. Reboot to recovery (changes the active slot)
4. Sideload gapps
5. Sideload Magisk
The lineage zip is like a "full OTA" for the stock ROM. Flashing it overwrites system, boot and vendor, hence the need to flash gapps and magisk again. But the recovery only supports flashing to the current slot, hence the reboot in the middle.
grufty47 said:
I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?).
Click to expand...
Click to collapse
FBE has to do with encryption. I found this that might help explain it.
https://www.reddit.com/r/LineageOS/comments/hd534a
Booting TWRP 3.5.2_9.2 (fastboot boot twrp.img) shows only garbage names under /sdcard plus a bunch of other places (but not all of /data). So I guess TWRP doesn't support FBE encryption? I'm not sure why that matters for flashing system partitions, but if any of lineage, gapps or magisk expects to write to places covered by FBE then clearly that's not going to work properly under TWRP.
Since you have installed TWRP over the Lineage recovery, you'll have to get a Lineage recovery back on your phone before you can upgrade. Using the provided recovery should work I guess? If not, you could use TWRP to flash the most recent Lineage 18 zip, which will also replace TWRP with Lineage recovery. Part of the reason I attempted the 18->19 upgrade in the first place is because I couldn't get the provided recovery to boot on my phone.
I hope that helps.
Lincoln
{
"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.
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
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