Develop Bugs

[RECOVERY] TWRP 3.3.1-0 (lilac) [UPDATE: 2019-09-16]

TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"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"
}
FEATURES
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!​
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16

Nice work!

What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?

Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51

4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!

aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.

modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?

4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...

works perferct! thank you :good:

I got an XZ1. Any chance to get TWRP for it (for testing)?

Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img

TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it

modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...

it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally

a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.

modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.

Question just to be clear: do we have to update twrp for evry new securitypatch?

To decrypt the /data partion on a stock ROM, yes you do.

Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham

UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10e/S10/S10+

Team Win Recovery Project 3.3.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"
}
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.
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.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: S10(Exynos variants - G970/973/975/F/N)
Download
Sources:
TWRP Tree and kernel source
Changelog:
15.12.2019
- Updated TWRP for Android 10.0
- From now on no more Magisk Prepatched images (if you need it patch it byself or flash my kernel where patched recovery is not needed)
07.10.2019
-Updated TWRP Kernel to Full ASIG Base
-Dex On PC will now work
23.09.2019
-Updated TWRP for boot on ASIG Bootloader and for not Break Camera on ASIG
-Dex On PC will not work for the moment but i will fix that soon
-Use ASIG TWRP Builds only when you are on a ASIG rom
22.09.2019
-Reverted MTP Changes from last build since for some mtp dont worked in system
21.09.2019
- Fixed the bug that mtp dont worked anymore on TWRP when usb cable got disconnected and reconnected
- Modded Kernel for have MTP in TWRP, Samsung Roms and GSI roms (for GSI Roms flash GSI_MTP_ENABLER.zip)
- Reverted FFS MTP changes since new way is more stable
- Fixed format data issue (was my fault)
14.09.2019
- Rebased Kernel to ASH6 base
- Added Busybox to twrp because enought devs asked me that since toybox is too limited
- Fixed all Bugs from initial release
- Fixed MTP using FFS_MTP in recovery (Thx to @bigbiff for add FFS MTP support on TWRP 3.3.0. FFS_MTP dont corrupts large files like the mtp used by samsung in the roms)
14.04.2019
- Initial Release
Bugs:
-No one
Telegram Group
https://t.me/twrp_n10
Note that after flashing this twrp other build not made by me will have lockscreen unlock issues
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][ASIG] TWRP for Galaxy S10e/S10/S10+, Kernel for the Samsung Galaxy S10
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 4.0
Stable Release Date: 2019-09-23
Created 2019-04-07
Last Updated 2019-12-15

Installation Guide
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp
flash the disabler that is on TWRP download link
flash my kernel avaiable here
press reboot to system in twrp.

Thank you!

Thank you!Thank you!

If I'm already rooted with Magisk do I still need to perform factory reset and so after installing the tar file?

jimbo77 said:
If I'm already rooted with Magisk do I still need to perform factory reset and so after installing the tar file?
Click to expand...
Click to collapse
yes because you have data encryption enabled and twrp dont have support for it

geiti94 said:
yes because you have data encryption enabled and twrp dont have support for it
Click to expand...
Click to collapse
Alright will give it a go. I'm just gonna backup my stuff

jimbo77 said:
Alright will give it a go. I'm just gonna backup my stuff
Click to expand...
Click to collapse
Anyone know if you could just decript it then flash?

Is it working?

reboot system...bootlop logo.

Does this include the ATT US galaxy s10???
---------- Post added at 07:57 AM ---------- Previous post was at 07:46 AM ----------
3dLyric said:
Does this include the SM-G973U
Click to expand...
Click to collapse

3dLyric said:
Does this include the ATT US galaxy s10???
---------- Post added at 07:57 AM ---------- Previous post was at 07:46 AM ----------
3dLyric said:
Does this include the SM-G973U
Click to expand...
Click to collapse
Only exynos will work for now, us snapdragon have locker bootloader, maybe never will have twrp.
Click to expand...
Click to collapse

help cannot bootphone into twrp or downlodmode tried three button combination no sucssees only phone blinks in coution messege

saxena1 said:
help cannot bootphone into twrp or downlodmode tried three button combination no sucssees only phone blinks in coution messege
Click to expand...
Click to collapse
Attach your phone to a computer and retry, it's a known issue

delete

bon0123456789 said:
reboot system...bootlop logo.
Click to expand...
Click to collapse
Have you tried doing reboot recovery from TWRP?

In the OP, it says ASC firmware base. Does that mean it only works on devices with ASC firmware base? If so how do I check that?

geiti94 said:
yes because you have data encryption enabled and twrp dont have support for it
Click to expand...
Click to collapse
I disabled encryption when installed Magisk.
Still need factory reset?

Ndaoud360 said:
In the OP, it says ASC firmware base. Does that mean it only works on devices with ASC firmware base? If so how do I check that?
Click to expand...
Click to collapse
Hi
I think he's talking about the last
First was ASBA and last is ASCA ^^

Step 9. hold vol up+ bixby+power until you are twrp, doesnt work for me. I have tried holding the buttons for more than 1 minute, holding vol up + bixby plugging usb, holding vol up and bixby only, it just stays on download mode. I can only press vol down + power to reboot, and I cant boot to system or recovery after that, I have to flash stock with odin and start over.
Any ideas?

[Recovery][v3.0.0][Curtana] Unofficial PBRP Recovery

{
"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.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp

Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path

kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp

Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!

@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?

You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.

Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?

mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it

end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks

Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well

Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?

Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.

end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!

Thank you
Sent from my Redmi Note 9 Pro using Tapatalk

is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!

keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk

how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted

trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...

Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222

Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0

[ROM] LineageOS 19.1 UNOFFICIAL - 1.3 [vendor & FBE] [2022-04-20]

LineageOS 19.1 for Sony Xperia XZ Premium
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
Real vendor partition
FBE instead of FDE encryption
DOWNLOAD
You can download the latest releases and TWRP here:
https://androidfilehost.com/?w=files&flid=333825
Check the ChangeLog below for firmware requirements!
INSTALLATION
This build uses a real vendor partition in place for the (now) useless oem partition. You will therefore need the modified TWRP with vendor/FBE support linked above.
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, No1Alien, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12.1 / 12L
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2022-04-20

SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.

REQUIRED FIRMWARE: 47.2.A.10.107 (47.2.A.11.239 should also work as there isn't any real changes)
CHANGELOG
2022-04-20 | 1.3| 47.2.A.10.107
Initial release

Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？

ssdsw said:
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
Click to expand...
Click to collapse
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.

derf elot said:
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
Click to expand...
Click to collapse
is there any clues/guide on how to edit the fstab?
so we can use f2fs on data & cache

is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?

m00ns0rr0w said:
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
Click to expand...
Click to collapse
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.

derf elot said:
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
Click to expand...
Click to collapse
hi,
thx for your answer. i was just curious, as the arrowos build is based on your work and has signature spoofing enabled. But if, as you write, that's a lot of work then ... no problem. the arrowos version is stable
And, without signature spoofing, the part with "howto best migrate from rom A to rom B" is obsolete Self-building doesn't seem to be an option, as the hardware requirements seem a bit ... ambitious

Thanks for the great ROM.
I did a few tests today and I couldn't find anything broken.
The only issue I have found so far is when I take a picture or video with Open Camera and try to open it for preview inside the app. It does not work.

Thanks for your working on the ROM.
I found that LOS installed on my G8142 seems to have screen always on when charging, both on 18.1 and 19.1 (which is this one). How to turn it off?

Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily

stipi69 said:
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
Click to expand...
Click to collapse
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.

derf elot said:
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
Click to expand...
Click to collapse
I agree, but i have faulty vol+ key so i was having a hard part sadlly.
Can i ask you something i see this problem 1+ years on all Lineage roms and i am not a developer:
SETTINGS / DISPLAY / LIVE DISPLAY / COLOR PROFILE / VIVID
If i choose this profile i get like 8 bit colors after a while of use, but realy like this profile... i adjusted it manualy now its good looking and stable but wondering if it is XZ P specific or all lineage

short message: my SIM card isn't working with this ROM.
long message: today i installed this ROM. I first flashed stock ROM, booted into it once, and then flashed this ROM. But, as with the ArrowOS ROM, my SIM card isn't working.
More Details: after fresh install of this ROM and during boot i enter the SIM PIN (so that works), but after boot it says: "service not available" (Dienst nicht verfügbar). I'm unable to get it working.
Provider: congstar (telekom daughter). The SIM worked with stock ROM, and it works in an older Samsung S5. Just for curiosity i flashed stock ROM again and
Yeah, i know, no warranty, but... someone had such a problem before?
thx

geee... getting crazy here... after the next (test) flash of this ROM the SIM suddenly works, as well as phone calls, SMS, ...
what's the difference to the first flash? after latest stock ROM flash i left the SIM inside, and the stock ROM (or the telekom software) did some settings, rebooted, and then i started the last flash. Is there something magic that is happening here?
if i had more hair all of it would be bright gray...

OK, after almost a week... no SIM card problems anymore. ROM is running stable.
Just some apps that somehow rely on Google Play Services (or microg maybe) don't run: apps that warn regarding severe weather conditions or catastrophes, like 'DWD Warnwetter', 'NINA KatWarn' etc.. Push notifications...

ROM is stable, and i finally managed the signature spoofing + microg stuff. Thx to @Yokurt815 and his little list in the XZ1C thread - going step by step, writing it all down, finally succeeded.
Am i right that the magisk/lygisk stuff has to be done again after flashing an possibly upcoming ROM update?

Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.

shoey63 said:
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
View attachment 5643169
Click to expand...
Click to collapse
Edited: NVM, seems like it won't work neither.
You need to set Ok Google/Hey Google at first boot; otherwise, it won't work.