After a while I figured out what the problem was, with a freshly flashed phone. Here I'll be answering my own question.
Does the twrp decrypt command output something else when decryption succeeds?
Yes, it outputs something like:
Attempting to decrypt data partition via command line.
Data successfully decrypted
Updating partition details...
That's expected. Devices with A/B partition scheme don't have a recovery partition. You can only boot in recovery mode with fastboot boot twrp.img. But to permanently flash recovery to device which can be booted into by proper key combination, you need to unpack both of your boot.imgs (A/B) from device and replace the ramdisk with the one extracted from twrp....
Solution by @beeshyams that worked in my case:
On Odin in the options tab; Uncheck the Auto Reboot option.
When Odin finishes the flashing procedure; use the suitable key combination to boot into TWRP Recovery Mode.
From the TWRP menu; boot into system.
Tip : In some cases, if a problem occurs try to flash an older version of TWRP
Note many ...
Searching the web gave me a clue: While before Android 7 one could easily flash a custom recovery without fearing side-effects, starting with Android 7 the system enforces DM Verity. That is, at a very early stage in the boot process, the system checks whether any partition was "tampered" with – which in my case meant the /recovery partition. As far as I ...
Yes you can boot in TWRP if bootloader is unlocked:
fastboot boot /path/to/twrp.img
Then you can simply dd whole eMMC or individual partitions. You need some extra memory to backup whole eMMC or /data partition. Smaller partitions (including the biggest one: system) can be backed up to internal memory i.e. data partition.
For Qualcomm SoC:
(for MTK ...
False. Many newer devices utilizing the A/B partition layout don't have a dedicated recovery partition. See landing page for Google Pixel for a full explanation.
True. Certain devices have exploits that allow recovery on locked bootloaders - this kind of recovery is often referred to as "Safestrap". Do note "exploits" - most devices don't have such ...
TWRP automatically does not mount system partition. It has to be mounted manually via its UI (under Mount option) or via command line. The fact that ls /system showed you nothing gives us the evidence that the partition indeed is not mounted. It can further be confirmed using mount command.
If you must insist on mounting system partition using command line, ...
There's an app that's just been released (tested on Moto X Play) that bridges the gap between Nandroid and full backup and backs up photos, videos, game data etc, which wasn't possible earlier
Tipatch (Play Store) and quoting from developers XDA thread
Tipatch patches TWRP to backup contents of internal storage (emulated SD card) as part of Data, thus ...
On recent Android devices, when you have Factory Reset Protection, which is enabled automatically when you setup a Google account, custom binaries (the files that are not signed by the OEM) are blocked (custom recoveries, boot, etc) for security reasons as one can bypass that lock and gain access to your data.
So disabling OEM lock in the Developer ...
The locked bootloader doesn’t let unsigned images to be flashed. So, the Image not signed... error indicates that there is a possibility of the bootloader not being unlocked.
Make sure the bootloader is unlocked.
Make sure you are using right version of TWRP for your device.
Try fastboot boot /path/to/twrp.img instead of flashing. If it boots, flash the ...
All Pixel's are bootloader locked by default, Google retail models can be unlocked easily while Verizon models cannot.
In the comments, you said "The question is how to PROVE it is not a Verizon variant. This phone is model G011C."
The model G011C is the Google Retail version, the Verizon version has a model of GA00152-US. Also, determining whether it's a ...
No! LineageOS does not Zip Signature Verify, instead the LineageOS download site provides SHA256 codes which the user or the downloading app can use to verify their downloads (using a tool like sha256sum). You can also use sha1sums just provide the ?sha1 to the webserver as below,
Rooting has become pretty straight forward since Magisk came out. This is one approach to root your device. All you need is a custom recovery and then just flash the Magisk systemless root .zip.
First step would be installing the custom recovery TWRP.
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from ...
according to your logs TWRP is currently in simulation mode.
Updating partition details... ...done Full SELinux support is present. Simulating actions... Updating partition details... ...done
1) go to Settings
2) toggle simulation mode off.
Try to flash the .zip again. You should be good to go
No, you can't use fastboot boot to boot into a custom recovery if the bootloader is locked (as Jerry Chin noted in a comment).
Android Security Internals says in Chapter 13: System Updates and Root Access (in section Recovery, subsection Custom Recoveries):
A custom recovery is a recovery OS build created by a third party (not
It's a issue with TWRP and the ROM you are using. TWRP is able to decrypt till Android 8.0 but if you're using a ROM above it you'll get this error and after flashing your data partition to ext4 it will let you use that space till ROM boot up and encrypt again. There isn't a solution yet. TWRP releases updated version 3.2.3_1 for few devices only which has ...
Eventually, I found a workaround (which is not a fix but it allowed me to continue the installation).
Since my device was detected in discovery, I did not used sideload. I just pushed the image to the sdcard with:
adb push xxxxx.zip /sdcard/
and then I installed the image from the sdcard directly in TWRP.
Found out the way to fix it:
Download stock firmware (*.tar.md5)
Flash it with Odin (it removes TWRP and replaces it with a standard recovery)
Start Android - still "Unsuccessful encryption" error
Boot into recovery mode (now it's standard recovery instead of TWRP)
Run factory reset
Start Android - now it finally starts - problem solved
Flash again TWRP ...
If a custom ROM has SEL set to enforcing, it means the dev is confident that features are working under strict SEL, and you can safely change it to permissive knowing that things will continue to work under a more lax SEL environment.
On the other hand, however, if he chooses to release with SEL permissive (especially if he lists it in the "bugs" section), ...
Well, sorry for bothering. The solution was simple: Don't use the wipe function of TWRP but the Format Data button in the wipe menu.
I was able to factory reset and install a different custom rom.
BTW: Don't use TWRP for Android >= 9 (Pie). As of Version 3.3.0 TWRP lacks the vendor partition feature. Pitchblack seems to be the standard now.
If you have the habit of removing apps on a regular basis, then you can clear it regularly. Once a year or once every 6 months should be fine. If you have root, then you can use Titanium backup as stated on this answer to remove dex files not link to apps.
Full credit to alecxs for this answer. Posting incase anybody else has the same problem in the future.
Download stock image(Mine was oneplus.com/uk/support/softwareupgrade/details?code=9)
Use extract_android_ota_payload-master to split the payload.bin inside the zip
(Method for step 2 https://pastebin.com/RfEHuvu7 , I did this on linux because my linux ...
Titanium Backup is a backup utility for Android that backs up your system and user applications along with their data on external storage of your choice. It is a leading Android application that uses root access to pull all your important applications and data from the system partition and stores them for future restoration. Whether your phone is corrupted ...
You can flash the custom Rom and Magisk without rebooting. However, I would reboot after flashing the custom Rom and Magisk. That way you can ensure your system and root are setup. Xposed is a bit hacking and it is best to flash on its own.
As far as Xposed you very important to reboot after flashing xposed. Also depending on Rom size it could take around ...
If the first solution does not open your encryption door to show your internal storage within TWRP. There is another option that should correct your internal storage issue. Format the Data, however it will cause the loss of your UserData. If the data is important to you, make a backup the /data partition. There are two simple approaches: one is through ...
Sounds like your internal storage is encrypted.
In order to fix this
boot into the Android OS.
Set a screen lock PIN or password.
Make sure you save it as requiring password on startup.
Then bootup into TWRP and it should ask you for your password to decrypt.
Put in the correct password
Your files should show up again.