[RECOVERY][STOCK]TWRP 3.3.1-0 UNOFFICIAL

[Schritti]

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.

THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS

#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 recovery
 * before using 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.
 *
 */

Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June/July patch)
- Touch not working when installed
- Please report any other bugs

Install guide:
Installing is currently not recommended because touch is not working on the installed version!
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode from adb
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it

Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button

If it keeps booting into TWRP and not System try

adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

Download

Changelogs:

3.3.1-0 03.08.2019
- Initial Release



Source code:
https://github.com/Schritti/device-sony-mermaid
https://github.com/Schritti/device-sony-ganges

If you like my work, press thanks
I would appreciate your Donation

Thanks to:
@MartinX3 for helping me developing the TWRP
@Oshmoun for providing device trees for Ganges and Mermaid
@naoki2010 for Testing

XDA:DevDB Information
TWRP, ROM for the Sony Xperia X10 Plus

Contributors
Schritti, MartinX3, Oshmoun, Marijn
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware

Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-08-03

Created 2019-08-03
Last Updated 2019-08-05

 

[Schritti]

Reserved

 

[Schritti]

Reserved

 

[MartinX3]

Woohooo!
First!

 

[sickkside13]

My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.

 

[Schritti]

My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.

All variants are supported

 

[clothtalklp]

I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?

 

[Schritti]

I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?

It's normal, that the screen is black in fastboot mode. If the LED is Blue then it's alright.
When you're in fastboot mode (Blue LED) check the windows device manager, you might install the driver again for fastboot. If it shows a device called "Android" you have to right click it and install the correct driver.

 

[Haxk20]

I just got the phone unlocked so i will boot into TWRP and install it and debug the touch. I have the feeling that it might be just missing file.

 

[Haxk20]

I just tested the installed version of TWRP and touch works just fine. The TWRP on itself is little slow. Decryption is broken and we see just bunch of junk folders in internal storage as expected.
But decryption shoudlnt be an issue after i bake TWRP into my AOSP images.
Rebooting into OS is totally broken and even cleaning misc doesnt help. Boots to TWRP all the time. Again most likely just an issue that it was not installed in boot.img right away but had to be added.

 

[mad-murdock]

So about unlocking - my device/version isn't supported to unlock. Any hints?

 

[Haxk20]

So about unlocking - my device/version isn't supported to unlock. Any hints?

You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.

 

[mad-murdock]

You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.

bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.

do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.

 

[Haxk20]

bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.

do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.

Sadly I do not think so. We would love another dev helping on SonyOpenSourceDevices or even custom ROMs but sadly if the phone is not unlockable there is nothing you can do sadly. I heard stories of people having carrier phones sim locked and after unlocking that they were able to unlock BT so you could possibly try that if the phone is locked to 1 carrier. If not then there i s really nothing you can do. I'm sorry.

 

[argotera]

Hi,

first off a big thank you!

I would like to root my xperia 10 plus I4213. I tried to do my homework before posting here, but since I am not knowledgeable on the subject, can someone confirm that these are the right steps:

1. Enable in phone third party apps, unlock developer settings, enable adb.
2. Boot in fastboot mode. That can be done in terminal, not by using buttons as it used to.
3. unlock bootloader . My understanding if that now, that can be achieved either via terminal or via windows newsflasher program.
4. Flash recovery from this thread
4. Boot into system and install magisk manager .
5. Install via recovery Magisk zip.
6, Boot into system and use magisk manager to enable root and set settings.

Should I install latest magisk 20.1 or an earlier version?

Thank you.

 

[reintal]

Problem with TWRP

Why is the device memory data encrypted even though the device doesn 't have a password?

 

[Haxk20]

Why is the device memory data encrypted even though the device doesn 't have a password?

That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.

 

[reintal]

That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.

It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.

 

[Haxk20]

It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.

We are mainly focus on making AOSP 10 stable now and TWRP is not on top of the list to fix now. And TWRP doesn't support Android 10 yet so we can't even begin.