[Discussion] Official TWRP for Beryllium [3.3.0.0] [05092019]
- Thread starter madsponge26
- Start date
When flashing new TWRP over a consisting TWRP does it erase internal Data/Storage??
It should what? Lol erase? I don't want that my internal Storage get deleted!
Edit: Did you flash it mate?
Last edited:
He said it shouldn't, not should
. Anyway, no, it will not erase.---------- Post added at 06:56 PM ---------- Previous post was at 06:56 PM ----------
Great, thanks !
He said it shouldn't, not should
---------- Post added at 06:56 PM ---------- Previous post was at 06:56 PM ----------
Great, thanks !
Oh ok thanks.
Edit: Everything went fine flashing new TWRP but still got the same 10 to 15 second not responding issue as in other Builds ? Any tips?
Last edited:
Touch delay is there at least for me
Tested battery drop but I couldn't recognized any so far...
@der_Kief. Earlier builds don't have touch delay? And when yes witch ones? Thanks
I meant it should not, anyways nope bro I didn't, im using Orange Fox since forever.
Sent from my POCO F1 using Tapatalk
No touch delay for me. I don't bother about the battery drop bug (if any), I only go to twrp to backup and restore, or to install updates to MIUI global beta rom. These are all long processes, so I charge after that anyway.
The bug I hate the most is I still cannot backup system and vendor, so that I can automate the backup using the OpenRecoveryScript, as well as have a smaller size of backup. Restoring with the new version 3.3 results in "extracttarfork() process ended with error 255".
So even with new version, we must still backup system-image and vendor-image as usual, and all is well during restore.
Last edited:
previous official doesn't have touch delay ... at least for meTouch delay is there at least for me
Tested battery drop but I couldn't recognized any so far...
@der_Kief. Earlier builds don't have touch delay? And when yes witch ones? Thanks
Noob question here.
But just wanted to ask that in the new
3.3.0-0 TWRP recovery
Do we still have to install a
Force encryption Disabler
Or
DM-Verity Disabler?
Or can I directly flash a xiaomi.eu rom after flashing the twrp recovery?
But just wanted to ask that in the new
3.3.0-0 TWRP recovery
Do we still have to install a
Force encryption Disabler
Or
DM-Verity Disabler?
Or can I directly flash a xiaomi.eu rom after flashing the twrp recovery?
I don't know about EU Rom, but I don't need any of those disablers.
Now, I got touch issue only when changing backup name. Very minor issue, just wait like 5 seconds, it's so trivial that there is no reason for me to go back to older version. However, YMMV.
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
90Official TWRP for Beryllium
WHAT IS 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, and root your device.
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Maintainer: @Dees_Troy
Initial Release
Changelog:
What's new in 3.3.0-0:
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
Download12lol this makes no sense. you cant make thread for others work
Maintainer: Dees_Troy
https://twrp.me/xiaomi/xiaomipocophonef1.html12TWRP 3.3.0-0 Changelog
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
Soon on our device..8I made a 3.3.1-0 twrp with the same touch firmware fixes as optimus drunk kernel:
https://gtrcraft.stackstorage.com/s/hs0ytnW4c4j6zHX
You problably need to flash miui kernel 9.6.18/20 from ipdev's drive for good working touch firmware8
To all wondering the same.
About encryption, this is a good start. Link
Easiest way to tell if and what version of encryption is used, is to use the getprop command in a terminal app or adb shell.
getprop ro.crypto.state
encrypted = Device is encryption
unencrypted = Device is not encrypted
getprop ro.crypto.type
file = FBE (File Base Encryption)
block = FDE (Full Disk Encryption)
Nothing returned = Not encrypted
Example using adb and three different devices.
Cheers.
