And is that a recovery or boot?
Edit: Ok well maybe you really dont know but it is a recovery.
Last edited:
And is that a recovery or boot?
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Official TWRP 3.2.1-0 Released
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
Code:* minui fixes (cryptomilk) * Better android-8.0 compatibility in ROM trees (Dees_Troy) * Fix missing library in android-8.0 (nkk71) * Fix inconsistent SDCard naming (DevUt) * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Download it from here - https://dl.twrp.me/osprey/twrp-3.2.1-0-osprey.img.html
You can use official TWRP app from Play Store, to flash recovery.
OK guys I'm using latest twrp but facing a strange bug. I'm changing twrp setting like viberate, screen brightness, timezone etc it keep the setting saved for few hours but then it reset to default setting and set everything like a fresh installed. I had flashed it via PC and it works fine for backup and restore ROMs. Any help what may be causing this issue?
?
Sent from my MotoG3 using Tapatalk
Try deleting the TWRP folder inside internal storage. Settings are saved there. Then reboot to recovery and apply your changes, check if they stick.OK guys I'm using latest twrp but facing a strange bug. I'm changing twrp setting like viberate, screen brightness, timezone etc it keep the setting saved for few hours but then it reset to default setting and set everything like a fresh installed. I had flashed it via PC and it works fine for backup and restore ROMs. Any help what may be causing this issue?
?
Sent from my MotoG3 using Tapatalk
Thanks, I have already tried that and it didn't workI've seen this not-saved thing before. I think the solution is to boot to twrp, make changes, reboot to twrp, check changes, reboot to twrp and do whatever.
Thanks, I will try thisTry deleting the TWRP folder inside internal storage. Settings are saved there. Then reboot to recovery and apply your changes, check if they stick.
Broadcasted from Zeta Reticuli
I've posted an updated build of my TWRP fork. It brings bug fixes related to the ADB backup feature, and also executes automated recovery scripts (such as wipe and update commands) without first waiting for the user to enter a decryption password. As usual, the download is on the downloads tab.
No offense, but a quick search of this thread yields the answer since it has been asked many times...Lately my phone takes about 2 to 3 minutes to boot to TWRP. What could be the problem.
I'm on the latest build. I tried the older builds, but is the same.
fastboot boot twrp.img
fastboot flash recovery twrp.img